View Single Post
  #10 (permalink)  
Old 01-02-2009, 08:30 PM
Glossman's Avatar
Regular 'Geeker
Location: 34° 50' 47" North, 119° 8' 55" West
Join Date: Feb 2007
Posts: 484
Reputation: 800
Glossman knows their stuffGlossman knows their stuffGlossman knows their stuffGlossman knows their stuffGlossman knows their stuffGlossman knows their stuffGlossman knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: HOW TO: Recover a Diamond that won't get past the boot screen! (Instructions)

Originally Posted by tobeychris View Post
Lol, I apologize. I wasn't trying to insult you, or your ROMs. I was saying that the main reason it happens is a mistake in building a ROM. This usually is because some of the modules were change (Usually if you use a different SYS). The way to avoid this most of the time is to use g'reloc. I can't speak for any other kitchen, but the C4RBON kitchen runs it every time, just in case.

Thank you. And sorry if I reacted a bit strongly, but I've been putting a lot of time into this lately, and I take it personally when my ROM causes a headache for someone. I get a little touchy when I *perceive* that someone is rubbing it in.

I just want to help the user recover as soon as possible, you know?

So, no hard feelings, okay?

On to business! The kitchen I used for the build did incorporate G'reloc, and it ran when I built my Production ROMs. What I'm wondering is how this manifests itself after multiple reflashes, but not after 1 or 2. Almost everyone (including myself) who has experienced this issue has never seen it after a single reflash from the same ROM type. This makes it really hard to troubleshoot.

How to recover your Diamond from a hang at the boot screen!

Audiovox Thera-Samsung i700-Verizon PPC 6600-Sprint 6700-Sprint Mogul-Sprint Touch-HTC Touch Diamond-HTC Hero-HTC SuperSonic (EVO)
Reply With Quote
This post has been thanked 1 times.