I tried .890 via both rsdlite and 1 click, resulting in nada. I am beginning to wonder if flashing too many images has somehow corrupted the partitioning scheme or the storage itself.
From what I gathered at http://elinux.org/Android_Booting, this problem appears to occurr during the first stage bootloader as it is unable to boot into recovery despite rsdlite confirming a successful flash, never mind the normal boot sequence itself, and the boot loader has somehow been damaged although how that is possible I'm not sure as it is locked and transitively frustrating many d3 peeps (unless this could actually be the possibility of an exploit, which would kick ass! Prolly not the case, but doesn't hurt to be optimistic ).
I just with I could see what the error message on the moto screen is (super duper tiny tiny). Is it possible to A) somehow view that error message via USB and B) completely wipe the entirevfile system clean? I'm actually installing sdk right now but quite frankly I have no clue what I'm doing
Edit: A) adb is a friend. Now to learn how to use it
From what I gathered at http://elinux.org/Android_Booting, this problem appears to occurr during the first stage bootloader as it is unable to boot into recovery despite rsdlite confirming a successful flash, never mind the normal boot sequence itself, and the boot loader has somehow been damaged although how that is possible I'm not sure as it is locked and transitively frustrating many d3 peeps (unless this could actually be the possibility of an exploit, which would kick ass! Prolly not the case, but doesn't hurt to be optimistic ).
I just with I could see what the error message on the moto screen is (super duper tiny tiny). Is it possible to A) somehow view that error message via USB and B) completely wipe the entirevfile system clean? I'm actually installing sdk right now but quite frankly I have no clue what I'm doing
Edit: A) adb is a friend. Now to learn how to use it
Last edited: