• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] Still Stuicking @ Boot Animation - LogCat.

Heh, I guess I'm tired.
But you see when it does not work, I have to do a battery pull each time and start over because when I try the next boot animation number it says its read only or something to the like.

So each time I got stuck at the Google logo or black screen I did a battery pull, then booted to recovery, mounted system, entered the commands but replacing the boot animation line with one of a different version aka -1 -2 or -3.

So, for the sake of clarification, when I get stuck at a Google Logo or the blank screen after, do what?

Again, thanks for your patience.
 
Sorry I can't fire-in at the moment--am away from my computer and watching by phone over a sketchy internet connection :(.

I'll check back when I can...

Cheers and good luck!
 
gapi said:
Heh, I guess I'm tired.
But you see when it does not work, I have to do a battery pull each time and start over because when I try the next boot animation number it says its read only or something to the like.

So each time I got stuck at the Google logo or black screen I did a battery pull, then booted to recovery, mounted system, entered the commands but replacing the boot animation line with one of a different version aka -1 -2 or -3.

So, for the sake of clarification, when I get stuck at a Google Logo or the blank screen after, do what?

Again, thanks for your patience.
Click to expand...

No problem man, we've thrown a LOT at you over the last many days. You're a trooper for keeping on.

Now Scary may revise my plan but here's what I'm thinking...what we are looking for is a bunch of scrolling text after the Google screen instead of the plain black screen. So if you don't get it after you original effort (which is doing the whole enchilda with the batch file and/or manually typing out all those commands), then I don't see a need to redo all that stuff again. It's already been committed to the phone. So if there's no scrolling text after the Google screen after that initial effort, then pull the battery and do only this:

adb push bootanimation-1 /system/bin/bootanimation (from platform-tools)
adb shell chmod 755 /system/bin/bootanimation

If you again don't see the scrolling text after the Google screen, pull the battery and then try the next one:

adb push bootanimation-2 /system/bin/bootanimation (from platform-tools)
adb shell chmod 755 /system/bin/bootanimation

And finally, if you still don't see the scrolling text, pull the battery and try the last option:

adb push bootanimation-3 /system/bin/bootanimation (from platform-tools)
adb shell chmod 755 /system/bin/bootanimation
 
Right. So after you've gone through those options I just posted Gapi and you're all done, then do one final restart and boot into recovery and run these commands:

adb shell ls -a -l /cache/bootani*.out
adb pull /cache/bootani-1.out
adb pull /cache/bootani-2.out
adb pull /cache/bootani-3.out

That should pull the "bootani" files from the phone INTO your platform-tools folder on the PC so you can access them and post them here. Does that have it about right SA?
 
Good Lord I love AndroidForums. I have no idea what I just read in this thread (way over my head) but wow. Talk about taking the time out to help a guy. Kudos to you all! I'm sure with this kind of support, your issue will be solved, gapi!
 
jova33 said:
Well jelly bean is out for all carriers now. Why not revert to stock and get the ota update?
Click to expand...

Well, gapi might still be left with the same issue of not being able to restore a custom JB ROM (I do suspect that he'll be able to proceed after doing so). It will be interesting to see how this does pan-out for him.
 
A guy just posted in the xda thread dealing with this same issue. He said the ota is causing the same boot loop. :eek:

If true, this is going to be in the news soon. I can't believe a few test phones didn't have this problem to tip them off.
 
Hi Guys,

Finished the 3 day grind this evening. I am thinking of going totally stock and waiting for the OTA and if it fails going to attempt a warranty replacement try.

I just wanted to make sure I was not abandoning you.
 
gapi said:
Hi Guys,

Finished the 3 day grind this evening. I am thinking of going totally stock and waiting for the OTA and if it fails going to attempt a warranty replacement try.
Click to expand...

That's exactly what I would do, its the smart money. Let us know if the ota solves it for you.
 
iowabowtech said:
That's exactly what I would do, its the smart money. Let us know if the ota solves it for you.
Click to expand...

+1! :)

(finally have a few minutes at a laptop here (I'm on vacation with my Dad in Oregon ;) :)))

Did we ever capture a kernel message boot animation output?

I was really mostly curious which method worked or worked best...

Cheers and thanks for hanging in there with us, gapi :).
 
scary alien said:
+1! :)

(finally have a few minutes at a laptop here (I'm on vacation with my Dad in Oregon ;) :)))

Did we ever capture a kernel message boot animation output?

I was really mostly curious which method worked or worked best...

Cheers and thanks for hanging in there with us, gapi :).
Click to expand...

No capture. Either a Google logo or a blank screen was all.
 
gapi said:
No capture. Either a Google logo or a blank screen was all.
Click to expand...

Ah, thanks...I was hoping that you'd see something or that the other bootanimation files would be able to produce something to the /cache/bootani-?.out files.

When I return home from vacation (don't really have my "tools" available with me here) I'll play some more with all of this. At the very least, we should be able to make some nice flashable .zip files for CWM that will allow use to put this in our toolkit for future debugging efforts.

Hopefully you won't have any trouble installing the JB OTA :) [pulling for you!].

Cheers!
 
Well, guess who's going to the Verizon store in the AM? Me!

I did the Wugs Tool Kit to revert to stock. Once done it OTA'd the MM76K pronto.
After a while I remembered to go into Apps and clear Cache and disable the Google services frame work and reboot to force an OTA. It worked.

20 minutes of the JB X boot animation later and it looks like there is no known cure.

I'm gonna put it on the charger and let it animate till I leave for the store.

Also I just remembered that I used to run Boot Manager. When the JB nightly ROMs surfaced I tried to load one in a Slot behind my AOKP ROM. It did not go well. That may be the smoking gun in my case.
 
Called Verizon, told them about the post OTA animation looping. The V-tech activated a 3-way call with a Samsung rep that heard the story. The S-rep immediately with no questions went into telling me to ship the phone in for repairs and of the estimated 9-day turn around time line. The V-tech interrupted her and let her know that will not be necessary that Verizon will take it from there.

I'll have the replacement tomorrow. My good-ole OG Droid is back in action till then. I have had offers to buy my OG that I turned down. It's in like new condition.

:smokingsomb:
 
Well bro, we gave it all we had but I'm really glad there's finally a silver lining for you. That had to be maddening. It'll be nice to finally say goodbye to all these problems and get back to normal flashing that actually works.
 
iowabowtech said:
Well bro, we gave it all we had but I'm really glad there's finally a silver lining for you. That had to be maddening. It'll be nice to finally say goodbye to all these problems and get back to normal flashing that actually works.
Click to expand...


Yeh, Thanks, I'll be holding my breath to see what comes on the device and the like eh?
 
Hmm, that's interesting about Boot Manager...I know Steven used that before and had a brief bootloop issue that we worked through...

I'll have to research that...
 
You must log in or register to reply here.
Back
Top Bottom