Hello,
I've read a few posts ( only a couple as of now ) mentioning the user was having a similar symptom as I am... the box only showing two penguins on power up. There is a difference on this one... I hadn't gotten to the point of flashing anything yet, I was only getting prepared for it when this happened. I'll go through the steps I took in a bit.
This is my first time I've worked with one of these although I've worked with the original Droid and the Bionic since both came out. I've flashed more roms on those that I can remember. Still, there is enough differences in methods and even some terminology... that I'd say I'm a newbie with these. Despite that, I've been a computer tech since 1987 so the procedures really don't phase me... I just need to get familiar with them some.
The unit is a MK808B Dual Core Rockchip RK3066 Cortex-A9 that I purchased on Amazon from Geekbuying. The unit has been working fine since the end of November up until tonight when I attempted to connect it to my PC to the OTG port.
The PC never recognized the unit despite my enabling PC mode for the USB as well as ensuring that USB debugging was disabled. When connected, at this point, it would power up and then a few moments ( perhaps 15-30 seconds ) later... it would power off or at least the blue LED would go out. I tried several USB ports on the PC and even tried a couple on my Netbook with the same results. This happened if I left the SD card in ( I understand I should remove it, at this point it was just something to try ) or if the HDMI is plugged in or not. I also have a 2.4Ghz receiver which I tried both plugged in and not plugged in. The second to the last scenerio I tried was to leave the USB power cord attached even though my PC is capable of putting out plenty of power. During this... the unit would power up and complete the boot normally.
Since none of the steps I took up to this point would let my PC "see" the unit... I removed the SD card again as well as the 2.4Ghz receiver and powered down the unit removing the USB power cord... disconnected the USB cable going to the OTG port... pressed on the inner button to get it into flash mode manually and plugged back into the OTG port. Again, after waiting for about a minute or so... the PC didn't recognize the unit.
I pulled the OTG cable out... and when I tried to boot it normally is when I first saw the two penguins on the screen. I'm guessing that the new USB type A to type A cable... is defective.
So I guess what I think I need to do is try to unbrick or fix the nand as described in sticky post but I'm not certain, it is just a guess.
I also assume that it appears that the boot files or kernel files got corrupted ( since I didn't make it to flashing ).
So I need to know if my assumptions are correct... I need to try to unbrick/fix the nand... or something else before I try that.
I'd also like to know if the two penguins mean that there is a corruption or something else.
Thanks ahead of time for any info or help.
PS... it will be a little bit before I can get a replacement USB cable... we've got an ice storm that just moved into the area. Still... if I can read up on the processes I need to do... it will be helpful when I can start.
I've read a few posts ( only a couple as of now ) mentioning the user was having a similar symptom as I am... the box only showing two penguins on power up. There is a difference on this one... I hadn't gotten to the point of flashing anything yet, I was only getting prepared for it when this happened. I'll go through the steps I took in a bit.
This is my first time I've worked with one of these although I've worked with the original Droid and the Bionic since both came out. I've flashed more roms on those that I can remember. Still, there is enough differences in methods and even some terminology... that I'd say I'm a newbie with these. Despite that, I've been a computer tech since 1987 so the procedures really don't phase me... I just need to get familiar with them some.
The unit is a MK808B Dual Core Rockchip RK3066 Cortex-A9 that I purchased on Amazon from Geekbuying. The unit has been working fine since the end of November up until tonight when I attempted to connect it to my PC to the OTG port.
The PC never recognized the unit despite my enabling PC mode for the USB as well as ensuring that USB debugging was disabled. When connected, at this point, it would power up and then a few moments ( perhaps 15-30 seconds ) later... it would power off or at least the blue LED would go out. I tried several USB ports on the PC and even tried a couple on my Netbook with the same results. This happened if I left the SD card in ( I understand I should remove it, at this point it was just something to try ) or if the HDMI is plugged in or not. I also have a 2.4Ghz receiver which I tried both plugged in and not plugged in. The second to the last scenerio I tried was to leave the USB power cord attached even though my PC is capable of putting out plenty of power. During this... the unit would power up and complete the boot normally.
Since none of the steps I took up to this point would let my PC "see" the unit... I removed the SD card again as well as the 2.4Ghz receiver and powered down the unit removing the USB power cord... disconnected the USB cable going to the OTG port... pressed on the inner button to get it into flash mode manually and plugged back into the OTG port. Again, after waiting for about a minute or so... the PC didn't recognize the unit.
I pulled the OTG cable out... and when I tried to boot it normally is when I first saw the two penguins on the screen. I'm guessing that the new USB type A to type A cable... is defective.
So I guess what I think I need to do is try to unbrick or fix the nand as described in sticky post but I'm not certain, it is just a guess.
I also assume that it appears that the boot files or kernel files got corrupted ( since I didn't make it to flashing ).
So I need to know if my assumptions are correct... I need to try to unbrick/fix the nand... or something else before I try that.
I'd also like to know if the two penguins mean that there is a corruption or something else.
Thanks ahead of time for any info or help.
PS... it will be a little bit before I can get a replacement USB cable... we've got an ice storm that just moved into the area. Still... if I can read up on the processes I need to do... it will be helpful when I can start.
Comment