yashsingh1/xdaforums huggingface dataset:
[Fascinate General] jbrnd:
I got this from /tmp/recovery.log:

CWMR Touch v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /recovery mtd recovery (null) 0
2 /boot mtd boot (null) 0
3 /radio mtd radio (null) 0
4 /system yaffs2 system (null) 0
5 /cache yaffs2 cache (null) 0
6 /datadata yaffs2 datadata (null) 0
7 /sdcard vfat /dev/block/mmcblk0p1 (null) 0
8 /data ext4 /dev/block/mmcblk0p2 (null) 0
9 /emmc vfat /dev/block/mmcblk1p1 (null) 0

Could the problem be that /data is ext4?
[Fascinate General] jpmccarthy:
I think the big issue if your steps are correct is that you flashed 10.2 version of Darky - which is GB and not ICS - and then tried to go to slim from there which will not work (you need an updated recovery like the glitch recovery used on the front page).

If you can get back into recovery I would try restoring a backup (assuming you made one) or re-flashing Darkys to get your phone operational. Then go the steps on the front page for flashing an ICS ROM and doing that step by step.

I *think* (again, based on your original post) that that is the issue of your bootloops. Also, what semaphore did you flash? Flashing that first won't for you either as Slim will install its own kernel (I replace it with Semaphore after I install Slim as part of multi-step process I do when I upgrade the ROM on my phone).

Hope that helps a bit - let me know.
[Fascinate General] jbrnd:
Thank you for the suggestions. Stupidly enough, I did not make a backup when trying to go from Darky to ICS. I tried flashing the Glitch kernel and then flashing CM9 on top of that, but got the same type of boot loop as before.

I suspect going back to the same version of Darky (10.2) that I had before would work, but the problem is that I can't find a version that's flashable through recovery.

I might have to wait for the jig to arrive and hopefully that'll get me back in business.
[Fascinate General] jpmccarthy:
I'm much better at telling people to make backups than I am at doing them. :)

You're not soft bricked so I will think about this some more.
[Fascinate General] jpmccarthy:
Just checking but did clear cache and wipe data.
[Fascinate General] jbrnd:
Yep, I went through all the clear cache/data etc options, but none of them made a difference.
[Fascinate General] jpmccarthy:
Maybe flash glitch, boot into recovery, clear cache and factory reset, flash the slim rom followed but the common and reboot.
[Fascinate General] jbrnd:
I've tried that too. Still the same problem, I'm afraid.
[Fascinate General] jpmccarthy:
Sorry very odd.
[Fascinate General] jpmccarthy:
It may be the lag fixes, you'll need to repartition when you get into odin.

Try pulling your battery, plug into usb on your pc, hold down volume down plus power, put battery back in. That might work.
[Fascinate General] jbrnd:
I'm afraid that still just loops through the battery charging animation. Would you mind posting your partition list (like what I posted earlier) ?

If I have that, I could reformat the partitions through adb while in recovery.

Many thanks for your help!
[Fascinate General] jbrnd:
Thank you, but unfortunately that doesn't show the file system types (ext4 etc). Would you mind posting that too?
[Fascinate General] jpmccarthy:
Yeah, I don't have a tmp recovery file so just gave to find something that works.
[Fascinate General] jbrnd:
If you have adb on your computer, "adb shell mount" should give you the file system types.
[Fascinate General] jpmccarthy:
Yeah, I've never had use ADB. So don't have that unfortunately. Might look into it this weekend if I have the time.
[Fascinate General] Ipse_Tase:
WTH...I am in the same boat. PLEASE HELP US!

I did the rooting, unlock, got spooked by the fugly Telus wallpapers and layout and immediately tried the method here. Phone WAS working fine on GB 2..3.3 stock, registered with Bell.

I did the Odin kernel flash, with

Glitch

got the recovery going and flashed SlimICS 4.2. I picked T959_4.2.zip from the slimrom site.

I wiped out EVERYTHING to be safe.

Started the phone, went straight into recovery.

Thinking this is a kernel issue, from the new recovery (I assume the ROM with it's kernel has a diff recovery, some red font one...can't remember which CWM version) I flashed semaphore 1.2.5s.

Again, phone booted into recovery (a blue one with this kernel).

I even tried to flash I9000_4.2.zip from slimroms, thinking I got the wrong ROM - same thing.

I'm at a loss as to what to do next, short of flashing Froyo from Oding and restarting all over.

Just hoping I'm missing something obvious...my life got more miserable since I cannot always see the SD card, which limits me to the files I have on the internal flash (kernels and ROMs).

Thanks in advance. :eek:
[Fascinate General] moosehead11:
Did you flash the Common file too?
[Fascinate General] jpmccarthy:
OK - so you were right on the wrong ROM - use the I9000 and the T959 which is for Vibrant - that does not work.

And also, as Mosse asks did you flash the common file as well - per the ROM instructions you need to flash BOTH or it will not work.

So if you can get into recovery I would:

1. recharge to 100% if not already.

2. wipe data.

3. Wipe cache.

4. Wipe dalvik cache

5. Wipe batt stats

6. You mention using speedmod, but read the full instructions - to flash ICS you will need a specific version of CWM - I've only ever used the glitch one personally (there is a link on the front page in the ICS ROM instructions).

7. Flash the I9000 4.2 for SLIM

8. Flash the slim_common for 4.2

9. reboot from your phone.

That *should* work I would think - I have flashed pretty much straight from ICS for the longest time at this point with no need to start fresh as I have not been changing ROMs but that should get you started. Once you have that working you can:

1. Look at swapping in semaphore 1.2.5s

2. Look at modding your build.prop and gps.conf per my front page instructions.

3. Look at swapping in a different ICS modem.

Hope that helps.
[Fascinate General] Ipse_Tase:
Yeah, I did :(

I started with the SlimICS_4.2 plus the slimcommon.

Lemme see if I can still see the SD from recovery and give it another try...or try Darky.

Thanks guys for quick replies.

---------- Post added at 01:21 PM ---------- Previous post was at 01:19 PM ----------

Lack of sleep can do that to people :)

Now, I actually flashed glitch first as per your guide....but i'm thinking my effup was using the T969 slim...I didn't see anywhere which one I should pick.

Hope it's not too far gone :)

/EDIT I can't see the SD from recovery, tried to unmount and mount sdcard (but that is the internal one) :((((((((((
[Fascinate General] karmatose:
I have nothing but good things to say about darky 11 as of now. On my first full battery charge cycle and it's holding up comparable to the JW1 base rom I was running but I'm using it a LOT more. Ram usage sits under 200mb idle and holy hell is it fast.

I can't believe how bloated TW and GB in general were in comparison.
[Fascinate General] jpmccarthy:
Did you use the glitch kernel that I have linked on the front page - I've had that problem with other glitch kernels - only the one I have posted works correctly.
[Fascinate General] jpmccarthy:
That's awesome - seems silly but if there was a % battery mod I'd give it a try. :)
[Fascinate General] Ipse_Tase:
That's the only one I have, thanks.

---------- Post added at 02:30 PM ---------- Previous post was at 02:13 PM ----------

Is there a way to copy from SD to internal in recovery? What is the option to mount external USB?

Can't get recovery to see the sd, hence I can't flash the I9000_4.2 slim ROM.

/EDIT NVM, didn't realize that actually "sdcard"n the glitch recovery is internal and "internal" is microsd.

After flashing the I9000_slim rom + slimcommon I'm still stuck at recovery.

---------- Post added at 02:53 PM ---------- Previous post was at 02:30 PM ----------

Wondering if this has anything to do with the recovery? Should I start over with CWN_all? or the cwm4_fixed_for_cm7-ODIN one?

I had a similar problem with my XOOM and it was related to the recovery I used...what worked for many people didn't work on my tablet. The moment I flashed another recovery (see my sig) I was up and running.

Damn, this is the 3rd Android device I go through all the hoops to get ICS and by far the most problematic. Just when I was happy that unlike others my refub didn't have hairs inside or pics from the previous owner :)
[Fascinate General] karmatose:
I compensate for this with SiMi Clock! I've been using it since day one, so not having a percentage battery isn't a huge deal to me.
[Fascinate General] Ipse_Tase:
Just for the sake of it I tried flashing CM9 nightly and Darky 11 (as per Darky procedure) but I'm still going back to recovery the minute the kernel starts loading.

One thing you guys mentioned (and Darky's thread too) is the "bootloop" following the ROM flash - which needs to be interrupted.

In my case, after flashing a ROM it just goes back to recovery...and the message is always success.
[Fascinate General] karmatose:
fwiw, I didn't have any bootloops at all installing DarkyROM v11 on my phone. Not even when I installed CM9. It just went smooth. I posted the steps I did a page or so back.
[Fascinate General] Ipse_Tase:
I bit the bullet and went back to Froyo :(

Back to square -1 (I had GB) but at least it booted.

It's gonna be a loooooooooooooooooooong weekend. :mad:
[Fascinate General] karmatose:
Really? I had mine going in about 2 hours. Longest part was installing Kies on my netbook. I could have used my desktop which had it installed, but that would have required me to get out of bed. Titanium Backup took care of the rest.
[Fascinate General] jbrnd:
Would you mind telling me exactly which Froyo files you used, and from which recovery image you flashed them? Thanks a lot!
[Fascinate General] jpmccarthy:
If folks are stuck maybe we need to do a hangout or gtalk or something.
[Fascinate General] Ipse_Tase:
http://dl.dropbox.com/u/2069701/T959TLJL3.zip which is posted on Page 1 by our helpful OP. :)

---------- Post added at 06:14 PM ---------- Previous post was at 06:10 PM ----------

Mothaf.... now Kies (2.3 which is the only one available from Samsung) says "Your device is not supported by Kies 2.0. Make sure your device is supported and try again".

WTF??????? This is crass, what on Earth can I do to "make sure my device is supported"? I did try to "troubleshoot" which triggered an agonizingly slow driver re-install, but that did not help.

The "unsupported" effing device does say on the other hand "Connected to Kies".

Sheesh...now I'm risking my a$$ trying to locate a copy of Kies 1.5. [Maybe my issue stems from this laptop running Win XP Pro?]

/EDIT From the geniuses at Samsung, specific for SGH-T959D

http://pages.samsung.com/ca/androidupgrade/English/:

Software Enhancement:

•	Android 2.3.3 (Gingerbread) upgrade

Equipment Requirement:

•	Samsung Kies, version 2.0.2.11071_128 or later

•	Data Link Cable, APCBU10BBE.

•	PC with standard USB port and the following system requirements.

System Requirement:

Item	Requirements

Operating system (OS)	Windows XP (32/64 bit), Windows Vista (32/64 bit) or Windows 7 (32/64 bit)

*Windows XP 64 bit or Vista 64 bit requires the installation of .NET.
[Fascinate General] jpmccarthy:
If you can get to download node, go back to stock using odin AND repartition.. I have had that error before when I have not repartitioned.
[Fascinate General] Ipse_Tase:
Thanks for being so prompt...I did repartition (knowing that I am going from GB/ICS back to Froyo - I saw your note).

I checked even the database for Kies and it frikkin' HAS the SGH-T959D included as "based GT-I9000M). So that should not be an issue.

And this IS Froyo stock from your link...

Is there an equivalent Telus GB floating around? For my current phone (an Optimus One) I could find dozens of GB versions...

---------- Post added at 07:19 PM ---------- Previous post was at 06:57 PM ----------

@jpmmcarthy: I hate to pester you, but reading around here, I found this thread that gives an option to move from Froyo to any ROM (I believe you might have used he initial ODIN-> Froyo part?)

http://xdaforums.com/showthread.php?t=923712&highlight=telus+2+3+3

Or I might have to get another computer where Kies actually works. Frikkin' PITA.
[Fascinate General] jbrnd:
Ahh, thank you. And all you did was install that file from recovery?
[Fascinate General] jpmccarthy:
Hi - no pester what-so-ever :) So there is not odin flashable for stock GB as far as I know, which is why we have the steps to FROYO, GB, root - and then from there. So you are selecting repartition in Odin when you flash and you have my files.

I do use that thread for going back to stock - BUT have never used it for an ICS ROM (it was written before ICS). I have only gotten to ICS using the steps on the front page actually.

Sucks you guys are having issues - but that is what I typically have done in the past. I have had some of the headaches and frustrations you guys are going through - usually cause I have not repartitioned in Odin, or used the wrong glitch.

I haven't flashed from scratch in a while as I've continued updating Slim so I may be a bit rusty in my memory.
[Fascinate General] Ipse_Tase:
One has to wonder if Samsung has any clue about software...I rebooted my machine, still the same error about the device not supported and how I should maybe buy one that IS supported.

Fine down the toilet goes Kies 2.3.2 and up comes 1,5...installs in 15 min and becomes unresponsive immediately...had to kill it. Then when it launches again, greets me with a whack of database errors. And then "this device is not supported by Kies". WOW.

I manage a support team for a company that writes their own code and I thought I have seen all.

Probably I haven't bought a Samsung product yet (my TV is Panasonic, BR Player an LG, older phone LG, etc) to really appreciate other vendors. Shame.

The hardware might be OK, but it does not run on grass fumes.

Don't wanna break the post record in one day, but if anyone has a suggestion how to get to GB from Odin, I'm all ears.
[Fascinate General] finneginsfast:
I never flash to GB, just out of curiosity why is it that you need GB? If you're trying to get an ICS rom just go from froyo to ICS...
[Fascinate General] Dayfid:
The bootloaders.
[Fascinate General] finneginsfast:
Can you tell me what the GB boot loaders are doing for you then cause every ICS rom I flash works fine?

Just wondering...
[Fascinate General] Dayfid:
I have no clue actually. Haha. A lot of people say "Flash GB before ICS for the bootloader" but I've never seen an actual reason why. Sorry.
[Fascinate General] Ipse_Tase:
That's exactly it: I followed recommendations, I have no allegiance to GB :)

If you have a working procedure to get from this stock Froyo to ICS, by all means, I will pour gold over you :)

Seriously, I just don't want the aggravation I had to deal with so far...ICS is the ultimate goal, no matter how.

/EDIT Last note before I crash: got home, fired up my Win7 desktop, installed POS Kies 2.3.2, device is now recognized, but does not show firmware nor can I upgrade. I can browse it and do other stuff.

Dead avenue.
[Fascinate General] finneginsfast:
So you currently have a super clean flash of froyo then, no root or non-stock kernels? That's the only time I've had issues trying to upgrade via kies...

Anyhow, I still use a method that Jp sent me quite some time ago that I use as a guideline. I'll try to clean it up with relavent links and post up for you to try.
[Fascinate General] Ipse_Tase:
Thanks a bunch.

I fear that restoring Froyo did NOT retore the bootloader (there was no file for it)...so could I be in this piockle because I stuill have some ICS bootloader?

But if that is the case, I should be able to flash ICS more or less following this guide:

http://xdaforums.com/showthread.php?t=923712&highlight=telus+2+3+3

Or that is for CM7 ROMs only? I don't feel comfy that the voodoo kernel is still called "froyo" something.

---------- Post added at 11:45 PM ---------- Previous post was at 11:36 PM ----------

Yeah, follow the "back to Froyo stock" instructions on the first page of this thread. Odin is the key.
[Fascinate General] jbrnd:
Now I'm confused. You say Odin is the key, but you flashed from recovery? Don't you have to put the phone into download mode to use Odin?

My problem is that I can't get into download mode - maybe you still could?
[Fascinate General] Ipse_Tase:
To recover from MY problem (booting into recovery, not kernel, regardless which kernel and/or recovery I was using) I flashed Froyo stock using Odin as per page 1.

At least I got a working phone...now back to tinkering.
[Fascinate General] xenonrider:
Hey guys, just got this phone and I'd like to upgrade it to ICS. I was reading the instructions on page 1 and it mentioned to use ODIN to flash the glitch and speed kernals. I downloaded the free ODIN mobile from here, but it says that the device is not compatible. Is there a certain flash kernel I need to download for this phone and if so where is it?

Also, is there a reason we can't we CWM on this phone? Thanks.
[Fascinate General] Ipse_Tase:
I lied when I said I'll go crash...thanks to the steps from finneginsfast (THANKS! again) I was able to go from my stock Froyo to Darky11 (ICS).

Most of the steps are similar to

http://xdaforums.com/showthread.php?t=923712&highlight=adb

but I haven't earned my reputation here to make recommendations.

All I can say is that it IS possible to go from stock to ICS via a kernel that has root and CWM (in this case voodoo).

Nothing else worked for me...incl the dreaded Kies (can't wait to wipe that $..t out).

I was able to unlock in ICS with the market app...easy-peasy.

Now my last question is: do I need to flash a Telus modem (step 8 in the above guide).

I am with Bell, NOT Telus - but they share the same UMTS network.

Cheers to all who offered advice and help.
[Fascinate General] moosehead11:
I would suggest using regular Odin not the mobile version
[Fascinate General] jpmccarthy:
So the last time I skipped GB, what would happen on boot is the T959D logo would come up, then quickly flash and come again - I would never see the kernel logo, and then my ROM would boot. By going to GB first before loading ICS, I now see the kernel splash page.

What does this do? I have no idea, but personally I knew something was amiss so wanted to figure that out and resolve it - going to GB first did that. :)

Most of the times I have screwed up my phone was to take it from 99% working to try to get 100% - one of the reasons I'm not actively switching from SLIM as its 100% IMHO - and by the way, seems to scream on semaphore 1.2.6s released yesterday.
[Fascinate General] jpmccarthy:
Agreed, have never used mobile odin.

I could load up some files onto box or something I use regularly that are too big for the thread - they are on my windows laptop which I don't regularly use though (pretty much exclusively linux at home)
[Fascinate General] jpmccarthy:
If you're modem works - you are good - as I said before that thread is a bit dated.

If you want to try different modems, check out the recommendations in the first few posts to ensure you get an ICS and 850 mhz compatible modem.
[Fascinate General] jpmccarthy:
CWM will work on this phone - the steps provided in the first post are just to get you to stable starting point and essentially go to

1. Froyo.

2. GB

3. Root and back up EFS

4. new CWM via glitch

5. ICS :)

What is the current state of your new phone? If its 2.3.3 you can go to the rooting method straight off.
[Fascinate General] jpmccarthy:
LOL - can you send me that too Finn - did I miss something in my front page posts? I cannot remember what I sent you :)

Really wish I could see what was going on on these phones, but the group here will help when we can - finn, matt, iwebsource, and especially buck have ALL help me tremendously in the past - and we all learn and re-learn based on questions.

I'm just glad we have a group of growing users on the phone - I'm still not up for getting a new device yet :)
[Fascinate General] jpmccarthy:
How did you get to download mode, that is jbmd's issue - button combos and battery pulls don't seem to be working for him.
[Fascinate General] Ipse_Tase:
Yup, I get it, but all I'm saying is that getting to download mode was not the issue for me, heck, I was always at lest getting in recovery. Not dead.

So he needs to sort out the first (worse case with a JIG cable). Sorry, can't help beyond what I've done to my phone, I wish I knew more.

For those who use Darky11 (which I like) and for jpmccarthy as semaphore user, will I benefit from flashing semaphore 1.2.6s to my phone?

Last on the modem part - my signal is 2 bars weaker then on my Optimus One, in the same location - so I'm a bit concerned.

I wouldn't mess with the phone at this point unless it would buy me something, so no, it's not for love of tinkering :)
[Fascinate General] xenonrider:
The phone is currently rooted with 2.3.3 on it. EFS has been backed up.

1. When I flash ClockworkMod Recovery (using the latest version of ROM manager v5.0.0.8)

2. I'm then asked to confirm the phone model (Nexus S, Nexus 4G, Epic 4G and GalaxyS i9000).

3. I select the GalaxyS i9000 option and it proceeds to successfully install CWM.

4. I then try to reboot into reovery and then get the following error:

E:failed to seek in /cache/update.zip (Invalid argument)

E:signature verification failed

I then select apply update from sdcard and select the location of the update.zip (on the root of the sdcard) and it tries to install it and then errors out with the following error message:

E:failed to verify whole-file signature

E:signature verification failed

And this is where I'm stuck as CWM refuses to install.
[Fascinate General] jpmccarthy:
No worries - was just looking at what you did to get into download mode so that might be able to help out jpmd - just you have done it VERY recently. All in all, glad you are up and running on Darky's which does look great! I'll likely try the next version of their S1 ROM once they add in a few more things - Joel was looking to get a very stable base as Darky's does have a reputation of being VERY stable with great battery life - although this is a bit of a departure as they had typically before only modded Samsung ROMs, but to get ICS on the Galaxy S you need to start from a port of the nexus AOSP.
[Fascinate General] jpmccarthy:
Ahhh - OK - you are trying to put on CWM from ROM Manager - I have never had any luck with that, nor do you really need it.

If you want to move to ICS you are pretty much well on your way - go the 2nd post on this thread for installing an ICS ROM where we load up the glitch kernel (as you are already rooted with a backed up EFS) and get that gltich coupled with whatever ROM you want to try - note that folks here trying Darky's 11 are using a combination of this posted and TotallyDubbed's instructions on the Darky's forum - so if that's the route you want to take - there are some steps posted a few posts back.

(If someone wants to send me their DarkyROM11 steps - I'll gladly add that to the OPS)

Hope that helps - time to whipper snip :)
[Fascinate General] jpmccarthy:
Not sure of the benefits other than having the latest - I don't see any cons to doing this - Darky would have used had it been out at the time I'm guessing. Semaphore is a FANTASTIC kernel.

Different modems have different strengths - the bars can be deceptive - the big test is just to ensure you are getting reception,etc. If you want to look at modems there is no harm in downloading and trying some - check out Perka's app and Buck had gotten Perka to create a directory of 850 compatible modems (which is what you want). I used the TLJ one, but KG3 is supposed to be good, and I swore by KC1 for the longest time.

Different modems work better in different geographies which complicates things (there's a map somewhere on XDA that shows what modems work better where LOL) but trail and error is the best thing - testing bars, reception (particularly rural) and GPS (noting you can make some GPS.conf changes to help out as well).