- Sep 12, 2011
- 1,384
- 237
Background
There are some users with "hard bricked" Kyros: tablet will remain on only while holding the power button, during this period the touch buttons will remain light. Buttons will go off as soon as one releases the power button. If the power button is also pressed for a long time (~10 seconds), it will also go off.
There is a similar "hard brick" with tablets very similar to Kyros, known as HeroTab/DroPad. They found out that it's possible to revive the tablet using a "SD boot", when the internal NAND content is bypassed or not needed.
Tutorial with solution is here:
[GUIDE] Revive your dead tablet - SlateDroid.com
Long thread with hardware details (although not devoted to revive a tablet) here:
[DEV] Custom kernel for Dropad/Herotab - SlateDroid.com
Facts:
1. Some Kyros tablets exhibit "hard brick".
2. "Hard brick" is related to NAND problems.
3. Similar tablets (almost same hardware) with similar symptoms were successfully revived, using a bootable microSD card that re-flashed NAND.
4. It is possible to put smdkv210 (CPU board used in MIDxx24) to boot from either NAND or SD.
5. Not all Kyros have the same internals (ex. MID1024 tablets may have MID1025 boards or MID1024N boards, same goes for 7024 and possibly 8024).
Questions:
1. Is there a simple way to determine if a Kyros is "hard bricked", i.e. fully working besides a faulty NAND?
2. It is possible to have console (simple TTL terminal) access to smdkv210 boards, it's also possible with Kyros? How?
3. Is there a way to change a Kyros from NAND boot to SD boot? How?
4. Is there a working bootable image (u-boot-sd.bin) for Kyros? Universal or one file is needed for each model?
5. Finally, is it possible to revive a "hard bricked" Kyros? How?
..."Soft Recovery" mode doesn't seem to work in all "brick" cases. When the Coby screen doesn't turn on at all "and" Droid Explorer or Disk Management don't detect the Coby "and" the soft lights shut off after 7 seconds......you're Coby is in a "HARD" brick.
There are some users with "hard bricked" Kyros: tablet will remain on only while holding the power button, during this period the touch buttons will remain light. Buttons will go off as soon as one releases the power button. If the power button is also pressed for a long time (~10 seconds), it will also go off.
There is a similar "hard brick" with tablets very similar to Kyros, known as HeroTab/DroPad. They found out that it's possible to revive the tablet using a "SD boot", when the internal NAND content is bypassed or not needed.
Tutorial with solution is here:
[GUIDE] Revive your dead tablet - SlateDroid.com
Long thread with hardware details (although not devoted to revive a tablet) here:
[DEV] Custom kernel for Dropad/Herotab - SlateDroid.com
Facts:
1. Some Kyros tablets exhibit "hard brick".
2. "Hard brick" is related to NAND problems.
3. Similar tablets (almost same hardware) with similar symptoms were successfully revived, using a bootable microSD card that re-flashed NAND.
4. It is possible to put smdkv210 (CPU board used in MIDxx24) to boot from either NAND or SD.
5. Not all Kyros have the same internals (ex. MID1024 tablets may have MID1025 boards or MID1024N boards, same goes for 7024 and possibly 8024).
Questions:
1. Is there a simple way to determine if a Kyros is "hard bricked", i.e. fully working besides a faulty NAND?
2. It is possible to have console (simple TTL terminal) access to smdkv210 boards, it's also possible with Kyros? How?
3. Is there a way to change a Kyros from NAND boot to SD boot? How?
4. Is there a working bootable image (u-boot-sd.bin) for Kyros? Universal or one file is needed for each model?
5. Finally, is it possible to revive a "hard bricked" Kyros? How?
Last edited: