Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

G1 with 5.0.8 boot loop + fix


This topic has been archived. This means that you cannot reply to this topic.
5 replies to this topic

#1 Andrew Low

Andrew Low
  • Members
  • 126 posts

Posted 24 June 2010 - 01:28 AM

Something "bad" happened to my 5.0.8-final install on my G1.  I was running with swap enabled, but I'm fairly confident this has nothing to do with this issue.

The web browser stopped working (would force close when launched).  A reboot resulted in my phone getting stuck on the G1 boot screen.

Hooking up ddms to get some log information, I could see there was a problem

06-23 20:44:09.637: DEBUG/dalvikvm(211): GC freed 500 objects / 34592 bytes in 52ms
06-23 20:44:09.697: ERROR/Zygote(211): Class not found for preloading: org.bouncycastle.asn1.x509.RSAPublicKeyStructure
06-23 20:44:09.697: ERROR/Zygote(211): Class not found for preloading: org.bouncycastle.asn1.x509.TBSCertificateStructure
06-23 20:44:09.697: ERROR/Zygote(211): Class not found for preloading: org.bouncycastle.asn1.x509.Time
06-23 20:44:09.707: ERROR/Zygote(211): Class not found for preloading: org.bouncycastle.asn1.x509.X509CertificateStructure
06-23 20:44:09.707: ERROR/Zygote(211): Class not found for preloading: org.bouncycastle.asn1.x509.X509DefaultEntryConverter
06-23 20:44:09.707: ERROR/Zygote(211): Class not found for preloading: org.bouncycastle.asn1.x509.X509Extensions
06-23 20:44:09.717: ERROR/Zygote(211): Class not found for preloading: org.bouncycastle.asn1.x509.X509Name
06-23 20:44:09.767: DEBUG/dalvikvm(211): GC freed 884 objects / 64736 bytes in 53ms
06-23 20:44:09.777: WARN/dalvikvm(211): Exception Ljava/lang/NoClassDefFoundError; thrown during Lorg/bouncycastle/jce/provider/CertPathValidatorUtilities;.<clinit>
06-23 20:44:09.787: ERROR/Zygote(211): Error preloading org.bouncycastle.jce.provider.CertPathValidatorUtilities.
06-23 20:44:09.787: ERROR/Zygote(211): java.lang.ExceptionInInitializerError
06-23 20:44:09.787: ERROR/Zygote(211):	 at java.lang.Class.classForName(Native Method)
06-23 20:44:09.787: ERROR/Zygote(211):	 at java.lang.Class.forName(Class.java:237)
06-23 20:44:09.787: ERROR/Zygote(211):	 at java.lang.Class.forName(Class.java:183)
06-23 20:44:09.787: ERROR/Zygote(211):	 at com.android.internal.os.ZygoteInit.preloadClasses(ZygoteInit.java:295)
06-23 20:44:09.787: ERROR/Zygote(211):	 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:582)
06-23 20:44:09.787: ERROR/Zygote(211):	 at dalvik.system.NativeStart.main(Native Method)
06-23 20:44:09.787: ERROR/Zygote(211): Caused by: java.lang.NoClassDefFoundError
06-23 20:44:09.787: ERROR/Zygote(211):	 ... 1 more
06-23 20:44:09.787: DEBUG/AndroidRuntime(211): Shutting down VM
06-23 20:44:09.787: WARN/dalvikvm(211): threadid=3: thread exiting with uncaught exception (group=0x4001e178)
06-23 20:44:09.787: DEBUG/dalvikvm(211): DestroyJavaVM waiting for non-daemon threads to exit
06-23 20:44:09.787: DEBUG/dalvikvm(211): DestroyJavaVM shutting VM down
06-23 20:44:09.787: DEBUG/dalvikvm(211): VM cleaning up

This was repeated several times in the log.  Somehow some part of my system has become corrupted.  In hindsight, I suspect my dalvik cache was messed up.

Attempts to fix this by reflashing CM 5.0.8 + the Google apps from recovery did not resolve the problem.

The actual fix
I then booted into recovery (I use CM 1.4 + JF) and used the wipe+factory reset.  Then flashing the CM 5.0.8 + google apps as per: http://wiki.cyanogen...x.php/DangerSPL (step 7)

Quote

Flash CM 5.0.x THEN gapps-ds-ERE36B (& Ebi1 port if required); then reboot (Boot may take longer than normal) DO NOT reboot between flashing ROMs!

This did result in a working phone - albeit one that needed to be reconfigured.  Thankfully I'm using Apps2SD for all of my apps, so nothing lost there.  Really wish I had backed up my ADWLauncher settings :(

Roo

#2 Transmition

Transmition
  • Members
  • 41 posts

Posted 24 June 2010 - 02:20 AM

I believe the issue of reconfiguring everything after a wipe can be avoided if you go into your settings beforehand, and have google back them up during sync. Then use apps2sd, and back up your ADW settings within the ADW settings menu.

Then do a factory reset, resync with google, enable apps2sd, let everything do its magic and reboot.

I haven't done this myself to confirm this however. It is merely speculation.

#3 Andrew Low

Andrew Low
  • Members
  • 126 posts

Posted 25 June 2010 - 12:51 AM

View PostTransmition, on 24 June 2010 - 02:20 AM, said:

go into your settings beforehand, and have google back them up during sync.

Where is this setting?  I've looked around in the settings menu and I don't see anything.

My calendar / gmail / contacts / etc were all backed up to google (of course) - but stuff like wifi settings, and my preferences (stuff like locale) were not sync'd.

This wouldn't have helped my particular "total fail" issue, as I couldn't even boot.  I did a nandroid backup, so I know I could extract the data if I really cared.

#4 Andrew Low

Andrew Low
  • Members
  • 126 posts

Posted 07 July 2010 - 04:26 AM

Ok it happened again.  However, you can recover from this type of boot loop without a full wipe.

Short version.  Use adb.

adb shell stop
adb shell

find and delete contents of:
cache/dalvik-cache
sd-ext/dalvik-cache
data/dalvik-cach

reboot.

I've written this up in more detail on my blog: http://www.lowtek.ca...-android-fails/

#5 Orange Crush

Orange Crush
  • Members
  • 10 posts

Posted 09 July 2010 - 04:16 PM

This happened to me as well, it never occurred to me to try just wiping the caches out and I wound up doing a full wipe.  Oh well.  Good to know when there's a boot loop I should attempt clearing the cache first.  Might've saved me some time this morning!

#6 herculesksp

herculesksp
  • Members
  • 8 posts

Posted 31 July 2010 - 03:30 PM

View PostAndrew Low, on 07 July 2010 - 04:26 AM, said:

Ok it happened again.  However, you can recover from this type of boot loop without a full wipe.

Short version.  Use adb.

I've written this up in more detail on my blog: http://www.lowtek.ca...-android-fails/

Awesome stuff Andrew, my phone got stuck in a boot loop all of a sudden and I was just short of biting at my nails. Found this post and did what you said and my phone is currently through to the Cyanogen X-animation, so I guess I am out of the boot loop. Thanks a Mil. :)