View Single Post
Old 09-20-2012, 03:06 PM   #180
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: 6299991
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
ouch... that doesn't sound good.

hmm.. I think k3flasher is an option but it's a "radical procedure" if you don't have a 3.3 backup (which I presume you do not)

The only option I can think of however.

I just did this recently (did I write it up? possibly)
in essence:

get a de-bricking image (3.0.x is available I think)

apply via k3flasher - (which in itself has a learning curve, thread is easily found)

then update incrementally to 3.3 (mine actually just jumped to 3.3 for some reason when I applied the Amazon update, I'm sure I documented that somewhere)

Then... well since your 3.4 OTA update already delivered... that should be it.

This procedure IF DONE CORRECTLY won't lose your books etc.

Sorry mate. best I can think of. HTH
twobob is offline   Reply With Quote