Installation of Sourcery 2.2

[Chizzele]

The Right way to install this Rom is to download all three to the sd and flash all before boot. I will fix the OP to further emphasize it.

 

[buellboy9]

Am I reading this thread correctly? This mod is no longer being developed?

 

[Chizzele]

Am I reading this thread correctly? This mod is no longer being developed?

That has been the case for the last couple of month. This Rom is not being developed but is Supported.

 

[transfigure]

Just installed. Quite simple. So far, it looks quite good. The options available are quite nice - I was able to install a Slayher kernel with ease. I'm coming from CyanogenMod because I was having lots of hanging and lagging problems. Fingers crossed that Sourcery runs more smoothly.

 

[zerosouls]

Are you by chance installing a kernel as well? If so I've seen that error with a kernel that's not compatible with a rom.

Either way I would move the rom zips over to the sd card via the mounted usb. Safest way to get clean zip files to the phone.

Sent from my Droid using Tapatalk

are you installing a kernel that was for a gingerbread rom maybe. ???

No, I installed deprimeds kernel which was working on CM6.

 

[buellboy9]

Setting up now... keeping fingers crossed...

 

[Chizzele]

Keep us posted... I would recommend not to install any kernel until the Rom is up and running, after words if you are not happy with the Kernel choices inside the Rom, nandroid and then flash new ones.

 

[buellboy9]

Sh*t... I'm DEAD. Don't know WHAT happened. Everything was going well till I rebooted the phone. Had everything installed, then used ROM Manager to reset the system file permissions (having trouble with moving an application to the SD card).

When it came back from the boot, I just got into a "Boot Logo Loop." No problem, I figured, I'd just reboot into recovery and start over... So I pulled the battery, reinserted it, held down the "X" key and powered the phone back on...

Except now all I'm getting is the Motorola logo over and over!! Tried pulling the battery again and with the "X" key held, it went into the Sourcery Boot Loop!!

HELP!! I've never run into this before that I can't even get into Clockwork Mod!! I've got a brick right now.

 

[zerosouls]

Hold down the power button and x together.

Sent from my Droid using Tapatalk

 

[buellboy9]

Hold down the power button and x together.

Sent from my Droid using Tapatalk

I should've been clearer... that's what I was doing. Looks like I'll have to wait till I get home and I can use RSD Lite to reset the phone back to stock.

 

[eagle1967]

what he said

never had the rom ever delete recovery. i can only guareentee you that there is a 99,9% chance you are not bricked (.1 % to avoid being sued so you can take 80% of my zero dollars i have)
let us know.

 

[eagle1967]

ok

Hold down the power button and x together.

Sent from my Droid using Tapatalk

I should've been clearer... that's what I was doing. Looks like I'll have to wait till I get home and I can use RSD Lite to reset the phone back to stock.

glad you know how to do that that will fix it. not sure what you did but this is definatley the first time anyone has ever lost recovery. and since the only thing that would mess with recovery inside the rom is rommanager im guess it did something. wierd. keep us updated.
remember if you like the rom its me and gflam if you have problems its all chizzles fault.

 

[buellboy9]

Yeah, I'm thinking ROM Manager did something hinky... It told me that there was an update to CWM, and without looking closely I said to go ahead and "flash the new ClockWorkMod Recovery." Only after I did that did I notice it flashed an OLDER version of CWM (I had the new Version 3, and it flashed the older version 2). That might be what did it.

 

[zerosouls]

Yeah, I'm thinking ROM Manager did something hinky... It told me that there was an update to CWM, and without looking closely I said to go ahead and "flash the new ClockWorkMod Recovery." Only after I did that did I notice it flashed an OLDER version of CWM (I had the new Version 3, and it flashed the older version 2). That might be what did it.

You mentioned you had a problem moving an APP to SD... I noticed Sapphire and Sourcery have a problem moving APPS to SD the first time with a "Failed to move App" but if you try again right after that it works...

But yea... I think running fix permissions during a fresh ROM boot might have mucked something up, it's sort of a fragile state to be performing high level system commands.

 

[Chizzele]

Yeah, I'm thinking ROM Manager did something hinky... It told me that there was an update to CWM, and without looking closely I said to go ahead and "flash the new ClockWorkMod Recovery." Only after I did that did I notice it flashed an OLDER version of CWM (I had the new Version 3, and it flashed the older version 2). That might be what did it.

You mentioned you had a problem moving an APP to SD... I noticed Sapphire and Sourcery have a problem moving APPS to SD the first time with a "Failed to move App" but if you try again right after that it works...

But yea... I think running fix permissions during a fresh ROM boot might have mucked something up, it's sort of a fragile state to be performing high level system commands.

Sourcery has a fix permission script built in.. Should help i believe in that event although i never had to use it. I never flashed using Rom Manager either so i'm not sure how to work it properly. I'm pretty sure my CWM version is outdated but it works so i don't mess with it.

Per Eagle, if it doesn't work you can blame me... Eagle please send the user 80% of my pay .. actually make it 100% dancedroid

Also Apps2SD always work for me as well. I think Rom manager might had a hand in your boot loop.