My problem still exists - black screen, no blinking LED, no flashing at all. I have not the proper firmware.
Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
I unbrick m8s HOW TO included - now i need firmware ROM M8S model: KCA-003
Collapse
X
-
Originally posted by feh View PostOk i suddenly had it running again.
But acutally i dont know what happend.
I connected the pins a few times and tried the method with the "AUTOROM" folder.
then i deleted it from the SD Card and copied the first rom again rom_cyx_m8s_ap6330_8g2g_150728 and tried the standard - method and it flashed.
but after this flash it went black again and im not really any step further .....
Edit:
I can now open the recovery menu again (everytime i need to connect the 2 Pins on NAND flash), but canot flash anything because it says /cache would not exists...
I thinks it's finally defect.
https://mega.nz/#!1Fw1Ta5a!0kpwpqjiY...Q-B09FRcGrsAHYLast edited by hipisxbit; 21 November 2015, 06:37.
Comment
-
tdcompuservices what if you connect the 2 NAND Flash Pins?
hipisxbit i will try, but i cant wipe cache because of the error (see picture below)
You may only view thumbnails in this gallery. This gallery has 1 photos.1 Photo
Comment
-
You can find it in the older Posts of this Thread:
http://freaktab.com/forum/tv-player-...614#post537614
and
http://freaktab.com/forum/tv-player-...572#post530572
hipisxbit I cannot flash a *.img file it doesnt show if i select "apply update from EXT" i only see *.zip files
Comment
-
Originally posted by feh View Posttdcompuservices what if you connect the 2 NAND Flash Pins?
hipisxbit i will try, but i cant wipe cache because of the error (see picture below)
Try flashing methods from sd card firmware format img .
Comment
-
Originally posted by feh View PostWhat exactly is that u-boot.bin anyway?
Do i always need it?
My advice : find last rom which bricked your device, extract bootloader.img , rename it to uboot.bin, ( or copy u-boot.bin if exist ) create boot sd card with amlogic bootcardmaker.
Then write to sdcard autorom1, which I share in this topic. Try to burn from sd card, with shorted nand pins, if not work , create another sd card with other u-boot.bin, and try again.
If You see screnn "updating" unshort the pins in nand.
Recently I had Brick and LED fading like with you , when u-boot.bin is wrong device not boot .
How do I find a moment that I'll try to do some set of files in - u-boot.bin
If you start flashing and device will not start after finish , there will always be an option entrance to recovery, and flashing other update zip file.
About factory_update_param.aml and recovery.img?-
I'm sorry , but if you do not know , you dont do any update .. This files works with only zip. firmwares. factory_update_param.aml - parameters for update.
recovery.img - recovery - program to update like as CWM or TWRP .
If you have Brick like this, update zip files not working . You have to perform flashing from sdcard with img update.Last edited by hipisxbit; 23 November 2015, 19:34.
Comment
-
Originally posted by orlie View PostI think that it is better than my case. Cache not exists, but I think it can be created or some problem is in the script. It can be resolved ... somehow.
My problem still exists - black screen, no blinking LED, no flashing at all. I have not the proper firmware.Last edited by hipisxbit; 23 November 2015, 19:26.
Comment
-
Originally posted by tdcompuservices View PostI had M8S from on top nof cover box, but when open look inside it marked M8 V8_1 20150418...
By the ways my problem is I have no power at all, after insert the toothpick into AV (No firmware flash yet, just insert toothpick
the take out now
1. No LED
2. NO POWER
Any idea, please..!
Read me answers in this topic for other users.
Comment
-
@hipsixbit, thanks for your help.
I didn't know anything about .img firmwares. (i always used factory_update_param.aml and recovery.img + firmware.zip files so far)
i will try with last bootloader.img as u-boot.bin and your autorom
Ok, i tried exactly as you said, used the bootloader.img as u-boot.bin from my last working firmware and your autorom from a earlier post.
But i had NO Update screen and no reaction at all.
So i tried it a few times (it's quite hard to get the right pins connected everytime) and suddenly the device booted completely normal.
But as i want to make my own firmware without so much bloatware - how can i prevent this to happen again? I mean this device is useless for me if i cannot flash it as often as i want without having this kind of "bricked" state again?
How can I make sure this wont happen again?
Last edited by feh; 24 November 2015, 09:38.
Comment
What's Going On
Collapse
There are currently 2493 users online. 1 members and 2492 guests.
Most users ever online was 63,956 at 18:56 on 20 March 2025.
Comment