Soft Brick. I'm sad....

Forums › Android › Soft Brick. I'm sad....

Linuxluver

5828 posts

Uber Geek

Trusted

Subscriber

#75469 18-Jan-2011 22:24

I had JP6 Froyo running fine on my SG-S, but decided to have a go at using ODIN to flash Android v2.2.1 (JPY).

I copied my (apparently empty) /efs to my external sdcard.

I removed root access. I had already removed the OLCP lag fix. No issues or errors.

I set ODIN (v1.3) it to re-partition and used the 512.PIT file.
I set PDA to JPY_JPY_JPY.tar

I did not flash a modem or CSC separately.

The download of the firmware went fine and the phone boots into the recovery menu, but there appear to be some errors below.

It says:

update media, please wait (in yellow)
E: can't mount /dev/block/st110 (in red)
E: copy_DBdata_media: Can't mount DBDATA (in red)

your storage not prepared yet. please use UI menu for format and reboot actions. (in yellow)
copy default media content failed. (in red)

I wiped the cache partition. When I tried to wipe for a data / factory reset the phone appeared to hang. I gave it ten minutes.

I reflashed the ROM and started over. Got to the recovery meny. Same errors as above.

I tried booting the phone from there, but after the SG-S logo the screen remains dark and I get one vibrate followed by 3 quick vibrates....over and over.

Soft brick.

Not sure where to go from here. I can get the phone into download mode by pulling the battery and starting over. My firmware file un-RAR'd without error, so shouldn't be corrupt.

Anyone have any advice to offer?

_____________________________________________________________________

I've been on Geekzone over 16 years..... Time flies....

johnr

19282 posts

Uber Geek
Inactive user

#428633 18-Jan-2011 22:29

Would a band aid help?

John

Linuxluver

5828 posts

Uber Geek

Trusted

Subscriber

#428636 18-Jan-2011 22:35

johnr: Would a band aid help?

John

Heh. :-)

Thanks.

I rarely have any trouble with this stuff, so looks like my luck ran out tonight. For now, anyway.

_____________________________________________________________________

I've been on Geekzone over 16 years..... Time flies....

Linuxluver

5828 posts

Uber Geek

Trusted

Subscriber

#428646 18-Jan-2011 23:05

I've tried flashing back to JP6 - the same level I was running before...and it has the same result.

Feels like a boot loop.....after the SG-S logo.

One vibration followed by 3 quick vibrations. Over and over.

Update: Have now tried JS3 (2.2.1) as well. Same result...

Wonder what I'm missing? It's a soft brick....just have to find the right combo.

_____________________________________________________________________

I've been on Geekzone over 16 years..... Time flies....

numfarr

329 posts

Ultimate Geek

#428655 19-Jan-2011 00:01

It was probably the pre-existing lagfix, even though you "removed" it your dbdata partition is still in a state that the standard kernel can't work with, and Odin is a bit stupid about recreating the partitions even when you tick re-partition. I see you already got an answer on xda, try that.

Linuxluver

5828 posts

Uber Geek

Trusted

Subscriber

#428663 19-Jan-2011 01:19

numfarr: It was probably the pre-existing lagfix, even though you "removed" it your dbdata partition is still in a state that the standard kernel can't work with, and Odin is a bit stupid about recreating the partitions even when you tick re-partition. I see you already got an answer on xda, try that.

Thanks. The answer on XDA helped a lot.

Flashing JP2 (which has all 3 files) and re-partitioning with 512.PIT at the same time appears to have got my phone to the point where it will boot OK.

...and JP2 is a Froyo....so that's not bad.

Update: I then flashed JPY over the top without a re-partition but that didn't work....so back to JP2.

_____________________________________________________________________

I've been on Geekzone over 16 years..... Time flies....

Linuxluver

5828 posts

Uber Geek

Trusted

Subscriber

#429954 22-Jan-2011 18:08

I've discovered that JP2 is pretty unstable and you'd only want to use it if you had few options. I'll be spending tomorrow morning trying to work out how to get my SG-S to Android v2.2.1 (JPY or JS3).

It looks like there is a path to there from here....but I have to nail down the details and then have a go.

_____________________________________________________________________

I've been on Geekzone over 16 years..... Time flies....

tonyhughes

Hawkes Bay
8476 posts

Uber Geek

Retired Mod

Trusted

Lifetime subscriber

#429976 22-Jan-2011 19:40

Im using Hardcore Speedmod JPY linked from page 249 of the SGS mega-thread here on GZ. Its FANTASTIC.

Fast. Stable. Battery life is just streets ahead of XT's stock 2.1.

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

androidmnz

178 posts

Master Geek

#430106 23-Jan-2011 08:34

Yeah agreed Speedmod kicks ass. I'm running Darkys 8.2 ROM with JPY and speedmod. Super smooth!

Hope you get it sorted Steve.

Linuxluver

5828 posts

Uber Geek

Trusted

Subscriber

#430194 23-Jan-2011 15:13

androidmnz: Yeah agreed Speedmod kicks ass. I'm running Darkys 8.2 ROM with JPY and speedmod. Super smooth!

Hope you get it sorted Steve.

Hi Pete

Took me 5 hours today.....but managed to get from the some seriously buggy JP2 (which was my only escape from the black-screen boot-loop) through several more crapped out install to being able to actually run JPY.

I followed these instructions, but stopped before rooting and lag-fixing. The separated / modded JPU build linked to there allowed me to get around the boot-loop crashing problem and boot up on JPU...then a simple flash got my to JPY....and Android v2.2.1.

I want to see what default / stock JPY is like before I mess with it. Call it a reality check.

I think the problem was that though I had removed the OCLF lag fix and done a factory reset, I had not not actually formatted the internal sdcard. Almost every flash I tried failed because it said the internal sdcard was not properly prepared...and the suggesttion on XDA is that this is a leftover from the lag fix, even though I had removed it and done a factory reset before flashing a new ROM.

_____________________________________________________________________

I've been on Geekzone over 16 years..... Time flies....

Damager

2125 posts

Uber Geek

#430230 23-Jan-2011 16:55

Clearing the Dalvik cache can also overcome bootloops.

- Telstra HTC Touch Pro2 - Energy ROM WM6.5.5 20 Oct/Cyanogen Mod Froyo 2.2 - R.I.P
- AT&T Galaxy S Captivate 16GB on XT (now with brother)
- Samsung Galaxy S2 on XT- Runs ICS 4.0.3 Resurrection Remix 9.2
- Business Hours - Work In The Electricity Industry, After Hours - DJ/Turntablist - Will Scratch Vinyl For Free'
- What's next??? S3?

Linuxluver

5828 posts

Uber Geek

Trusted

Subscriber

#430324 23-Jan-2011 20:59

Damager: Clearing the Dalvik cache can also overcome bootloops.

Thanks. That may have been a factor, as I wasn't wiping the cache after each flash and subsequent failed boot attempt.

I definitely tried all of these things much of the time if not every time...and could see via ADB/ logcat that there was a mix of permissions problems and lots of stuff not found.....resulting in a system crash....and then a cleanup....and then let's try it again. Etc....

_____________________________________________________________________

I've been on Geekzone over 16 years..... Time flies....

Damager

2125 posts

Uber Geek

#430407 24-Jan-2011 01:17

Even though I have a Captivate, which differs slightly from the Galaxy S and have very different ROM upgrade paths, any issues encountered usually have some common factor.

My last ROm flash resulted in a bootloop.. Couldn't for the life of me work it out. I'd never touched the Dalvik cache in previous ROM upgrades, so wiped it after several attempts at installing the ROM and presto, I was away.

androidmnz

178 posts

Master Geek

#431278 26-Jan-2011 08:46

Linuxluver:
androidmnz: Yeah agreed Speedmod kicks ass. I'm running Darkys 8.2 ROM with JPY and speedmod. Super smooth!

Hope you get it sorted Steve.

Hi Pete

Took me 5 hours today.....but managed to get from the some seriously buggy JP2 (which was my only escape from the black-screen boot-loop) through several more crapped out install to being able to actually run JPY.

I followed these instructions, but stopped before rooting and lag-fixing. The separated / modded JPU build linked to there allowed me to get around the boot-loop crashing problem and boot up on JPU...then a simple flash got my to JPY....and Android v2.2.1.

I want to see what default / stock JPY is like before I mess with it. Call it a reality check.

I think the problem was that though I had removed the OCLF lag fix and done a factory reset, I had not not actually formatted the internal sdcard. Almost every flash I tried failed because it said the internal sdcard was not properly prepared...and the suggesttion on XDA is that this is a leftover from the lag fix, even though I had removed it and done a factory reset before flashing a new ROM.

Good to hear you sorted it Steve. When you get sick of the stock JPY, I'd suggest Darky's ROM. He's just put out 9.0 and it's very customisable with the option for Speedmod or the new Voodoo kernel. You won't even need lagfix enabled. It's like bloody lightning.