.32 Brick Solution That May Work And Have Worked With Some PPL

**spica234** · 06-02-2011, 06:43 AM

WARNING: KERNELS BASED ON .32 CAN BRICK YOUR SPICA, ALTHOUGH 3 CASES HAS TAKEN PLACE BY HP AND 1 BY OTHER .32 KERNEL(NOT INCLUDING NAME OF KERNEL), I STRONGLY RECOMMEND TO USE TIME-TESTED .29.6 KERNEL FOR STABILITY AND SAFETY.

DISCLAIMER: I DO NOT ENCOURAGE TO USE ANY .32 KERNEL HEREBY, IMPORTANCE OF THIS THREAD IS ONLY FOR PROVIDING TEMPORARY SOLUTION TO ALREADY SEMI-BRICKED SPICA(WITH DOWNLOADMODE WORKING) BY AN ACCIDENTAL INSTALLATION OF .32 KERNEL. THIS THREAD HAS NO OTHER INTENTION AND SHOULD NOT BE CONSIDERED IN WRONG WAY.

*STEPS TO PREVENT BRICK DURING INSTALLATION OF .32 KERNEL:

-Before installation, enusre your file system is in ext2, If not or in RFS then convert them to ext2
- Before installing .32 kernel make sure to WIPE DALVIK-CACHE before and after installation of .32 kernel.Sometimes in most-of-the cases, WIPING DALVIK-CACHE BEFORE AND AFTER installtion don't create such problem.

*WHAT TO DO IF BRICKED ALTHOUGH BY PREVENTION OR BY AN IMPROPER INSTLATTION(WITH Active DownloadMode):

-When after installation of .32 or any kernel you find boot-loop once with boot logo with no processbar, follow below mentioned steps immedietely:

(1.) DO NOT ATTEMPT TO START MOBILE ONE MORE TIME. DO NOT MAKE FULL ODIN FLASH, Cause these flash's final results is converted file system to RFS.
(2.) ENTER IN DOWNLOAD MODE THEN OPEN ODIN, ATTACH USB CABLE
(3.) NOW USE ANY .29 PDA KENREL TO FLASH WITH ODIN. EG. XMister_CM_CRI_PDA or Lukiq_PDA. SELECT ANY OF THESE KERNEL IN ODIN AS PDA.IF YOU DON'T HAVE ONE DOWNLOAD ONE FROM ATTACHMENTS NOW.
(4.) SELECT PROPER OPS FILE. AND THAT'S spica_jc3.ops
(5.) THEN FLASH WITH IT AND WAIT UNTILL THE PHONE STARTS AND BYPASS BOOT LOGO
(6.) DETACH CABLE AND USE TIME-TESTED .29 KERNEL EVER SINCE THEN.

NOTE:I think instead of full odin flash, only kernel as PDA will be good as it doesn't convert to final RFS as full flash, I faced such problem before long time on mKernel at that time I dint know untill I read here post "3RD brick after .32 Kernel installation" that it was partial symptoms of brick caused by .32 kernel, all I did was flash Xmister_cm_bfs_PDA via odin as it was only thing I had that time in my PC and it worked. Other 2-3 users faced such problem with other .32 kernel (Needless to mention kernel name , it wasn't HP) and they also did odin flash that way and their spica is working till now.

**banjo0917** · 06-02-2011, 06:50 AM

Why use BFS Kernel? BFS needs ext2. What if their file system is RFS, this will cause more problem, resulting to bootloop and inability to enter recovery mode.
I suggest you attached CFS Kernel TAR file.

**spica234** · 06-02-2011, 07:06 AM

Thank you banjo for pointing out about BFS

**Spoetnic** · 06-02-2011, 10:07 AM

(2.) OPEN ODIN, ATTACH USB CABLE AND ENTER IN DOWNLOAD MODE

When attached before you try to boot into downloadmode, it will boot into system, right?
I always boot into downloadmode (or recovery for that matter) before I attach it to the computer.

So im suggesting:
(2.) OPEN ODIN, ENTER IN DOWNLOAD MODE AND ATTACH USB CABLE

**ragstoriches** · 06-02-2011, 10:48 AM

sounds like a good solution,Needs to b stickied so that no one else gets his Spica bricked.

---------- Post added at 01:18 PM ---------- Previous post was at 01:12 PM ----------

Originally Posted by Spoetnic

When attached before you try to boot into downloadmode, it will boot into system, right?
I always boot into downloadmode (or recovery for that matter) before I attach it to the computer.

So im suggesting:
(2.) OPEN ODIN, ENTER IN DOWNLOAD MODE AND ATTACH USB CABLE

it also can b done Spica234's way....
OPEN ODIN...ATTACH USB CABLE...ENTER IN DOWNLOAD MODE...NOW ATTACH THE USB CABLE TO CPU

(jusz kiddin,u r ryt)

**cygnus** · 06-02-2011, 01:22 PM

Hmm, It sounds good if someone's phone has become stuck in a bootloop, but this doesn't help for those of us who's phone got damaged to the point of no download mode I'm afraid- In my case I'd already got a .29 kernel installed too- whatever broke the phone did so when running .32 then slowly corrupted flash.

There's another option here- that the three flashed phones have simply worn out the flash chip- too many writes.

**tom3q** · 06-02-2011, 01:43 PM

Originally Posted by cygnus

There's another option here- that the three flashed phones have simply worn out the flash chip- too many writes.

I would exclude my phone from this hypothesis, as it was the personal one with at most several flashes done to it at all, rather than the one used by me for development (and even on it I use kexec for testing my kernel, without flashing).

**cygnus** · 06-02-2011, 02:36 PM

Originally Posted by tom3q

I would exclude my phone from this hypothesis, as it was the personal one with at most several flashes done to it at all, rather than the one used by me for development (and even on it I use kexec for testing my kernel, without flashing).

Hmm- You're right there- In fact I'm going to retract it, because even in an extreme case It'd be hard to wear out the flash chip- I guess I could only have flashed mine maybe 50 or so times- nowhere near the 100,000 write cycles (generally) applied to flash memory. Besides if we wore out the flash would it cause the phone to brick, or just become unable to load a kernel or specific file sitting on the burnt block? The symptoms don't fit my diagnosis. :-)

Ah well, I'm a little lost now. I've bought an (official!) teensyUSB and am creating a little portal robot for the fun of it since I can't play with my phone. heh.

**spica234** · 06-02-2011, 03:02 PM

Tom3q,
May be I'm wrong, But I think brick isn't directly caused by .32 kernel itself(ONLY RECOVERY affected along with boot-loop), But by a full re-flash via odin indirectly. Might after bootloop, ODIN recognize it(spica) differently and write stuff at wrong addresses. Cause after full-flash download mode also disappeares along with blank screen:/

**nebkat** · 06-02-2011, 03:40 PM

Originally Posted by spica234

Tom3q,
May be I'm wrong, But I think brick isn't directly caused by .32 kernel itself(ONLY RECOVERY affected along with boot-loop), But by a full re-flash via odin indirectly. Might after bootloop, ODIN recognize it(spica) differently and write stuff at wrong addresses. Cause after full-flash download mode also disappeares along with blank screen:/

The spica_jc3.ops file has all the partition locations. It couldn't possibly write to the wrong ones...