View Single Post
Old 02-15-2013, 10:30 AM   #9
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299993
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
politely might I suggest 1st you remove the wpa supplicant log.
ALL THOSE LOGS

It reveals entirely too much data about your home/roaming network And is not helpful to this cause.

Looking in all netlog now.
Hmm I would just take them ALL down. not helpful, too personal.

Wrong logs.

Will have a head scratch BUT: Like I said before:

I think... IIRC I ran an md5sum against everything ON my machine versus the md5sum checklist-list embedded in the update (baf posted it somewhere on here)

I found 3 or 4 files that I had amended. However. I still got a U006 even after all that. (possible custom modules, I forget what the exact issue was)

And this really is the last time I will type this: simply cleaning the main partition with a fresh set of data (using imx_gui and fastboot I think) sorted it out for me.

I lost no personal documents in the process.

Hope that helps.

Last edited by twobob; 02-15-2013 at 12:13 PM. Reason: removed network details from post since logs are now down
twobob is offline   Reply With Quote