The firmware I dumped for you 20170829.121614.V0321, well the img you made seems to not flash back. Getting stuck at 10%, fails at uboot and sometimes logo. Here's my error "uboot/partition logo/verify partition/error result". Odd that I was able to dump the rom but not flash it back...
Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
[ROM] Mecool M8S PRO+ TVStock Nexus ROM (Android TV 7.1)
Collapse
This is a sticky topic.
X
X
-
Magendanz,
The firmware I dumped for you 20170829.121614.V0321, well the img you made seems to not flash back. Getting stuck at 10%, fails at uboot and sometimes logo. Here's my error "uboot/partition logo/verify partition/error result". Odd that I was able to dump the rom but not flash it back...
-
#571.1Guest commented29 September 2017, 19:45Editing a commentWell, I had to use the uboot binaries (UBOOT.USB, DDR.USB, aml_sdc_burn.UBOOT) from the previous OEM firmware release to create the .img file, and if the hardware on these August devices is using new eMMC chips it may no longer be compatible with the old .img file. I was only able to test it on my units, which predate the problems.
What I need is an OEM .img file for the 20170919.150557.V0619 release. That will include any updates made to the uboot binaries.
Of course, the other possibility is that the uboot binaries are fine and it's the prolonged write to the eMMC that's failing. Given that you're high risk to be in the affected batch, that's seems more likely.Last edited by Guest; 29 September 2017, 20:05.
-
-
Originally posted by Magendanz View PostI don't really see much of a point in doing that, given that I've already made the ATV for 20170919.150557.V0619 and it fixes a lot of longstanding issues. It might be the last OEM firmware that can have TWRP recovery installed, but I wonder how many actually use that.
Last edited by jack1142; 29 September 2017, 20:01.
Comment
-
Originally posted by ready View PostI am trying to upgrade the 20170829.121614.V0321 to ATV build for 20170919.150557.V0619, but without success. What is wrong? Please see attached screen.
Comment
-
Originally posted by kml View Post
Change the image filename to something shorter, like update.img and try again. Hard to explain, but worked in my case with X robot.
on my second the same box in recovery state i was observed that
Last edited by essir; 29 September 2017, 22:14.
Comment
-
Originally posted by superceleron View PostPPl with problems plz give the board revision... that is printed on the board itself!
https://imgur.com/a/O6X8T better resolution
Comment
-
No one, as far as I can remember, has Flashed a box that came with 08.29 FW and got a working box. No one has got a working box back by reverting to 08.29
All the boxes, as far as I can tell have eMMC Rev 5.1
Do they all have D/X Ram ?
It would be good to have as much info to correlate as possible, so if all who can could post as asked over in OEM Thread that would be great.
Pete
Note:
KLMAG2WEPD = 5.0
KLMAG1JENB = 5.1
Cut and Paste to OEM thread
If as many as can, could post their
FreaktabHandle - Box ##
STATE = Good | BAD
FW DATE = YYYY.MM.DD
SUPPLIER = Fullname
eMMC Marking = SAMSUNG | SEC
eMMC Rev = 5.0 | 5.1
3 Digit NUMBER = ###
RAM = D/G | 10DIGIT
Comment
-
Originally posted by superceleron View Post
Do you see any diferences on the board, placement of the chips etc etc?
I can't manage to get a good enough alignment of photos of the 2 boards to do a difference layer compare in Photoshop
Nothing else stands out to the naked eye ...
Comment
-
Originally posted by essir View Post
Please find the attached files. Where I can find this information?IThis information is under cooler?
https://imgur.com/a/O6X8T better resolution
right by the WiFi aerial connection
Comment
What's Going On
Collapse
There are currently 1478 users online. 1 members and 1477 guests.
Most users ever online was 63,956 at 18:56 on 20 March 2025.
Comment