Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
[ROM] Mecool M8S Pro L Stock & Nano Nexus ROM (Android 7.1)
Collapse
This is a sticky topic.
X
X
-
Guest
So, I loaded a M8S PRO L burn package into USB Burning Tool and hit Start, then tried a "reboot bootloader" command, and it just rebooted and hung at the boot logo. The WorldCup driver and USB Burning Tool didn't detect the device. Using "reboot recovery" also just rebooted to TWRP recovery without the device being detected.
However, if I restart with "reboot update", that works and immediately kicks off the burn package flash. Unfortunately, I don't know how useful that is, because most of the time when you really need to flash a burn package instead of an OTA update, it's because you can't boot to a terminal window, even in TWRP.Last edited by Guest; 30 November 2017, 10:44.
Comment
-
Originally posted by Magendanz View PostSo, I loaded a M8S PRO L burn package into USB Burning Tool and hit Start, then tried a "reboot bootloader" command, and it just rebooted and hung at the boot logo. The WorldCup driver and USB Burning Tool didn't detect the device. Using "reboot recovery" also just rebooted to TWRP recovery without the device being detected.
However, if I restart with "reboot upgrade", that works and immediately kicks off the burn package flash. Unfortunately, I don't know how useful that is, because most of the time when you really need to flash a burn package instead of an OTA update, it's because you can't boot to a terminal window, even in TWRP.
Comment
-
#19.1Guest commented30 November 2017, 10:49Editing a commentYou type that from a terminal window. On my custom ROMs, you can enable that with the "local terminal" setting in Settings->Developer Options. Alternatively, you can install an app like Terminal Emulator for Android.
And also, kicking off any update via the OTAUpgrade app seems to call "reboot update" internally.
-
-
I know this question was asked earlier somewhere, but i can´t find it atm.
If I choose OTAupgrade and want a clean install of the stock ROM without loosing L1 keys then I have to choose install local file and wipe data .
Is that correct ?
Comment
-
Thank you !
one more question please :
I do prefer your Nano an Stock ROMS because Amazon Prime Video App will do and I have most of my apps from playstores and don´t have to sideload.
The next device is for my kids. It would be easier for them to have a launcher like the old Mecool or Beelink laucher. Is that possible ? what do I need ?
Comment
-
Guest
Changelog (20171202):- Updated to latest M8S Pro L OEM firmware (20171127.165619.V0928)
- Added local update and backup option from Settings->About->System update based on Amlogic stock OTAUpgrade app.
- Latest build from Open GApps (20171202)
- Wake from sleep will usually result in a restart. This seems to be a bug in the underlying OEM firmware.
- Clicking on Vision Settings in the setup wizard will launch an unsupported activity in Settings.
- You can enable the nav bar in Settings->Display->Statusbar, but may need to toggle back and forth before it will show.
- Nano Variant: BURN PACKAGE (915MB IMG file), OTA UPDATE (471MB ZIP file)
- Stock Variant: BURN PACKAGE (1.39GB IMG file), OTA UPDATE (787MB ZIP file)
Comment
-
Guest ..weren't you gonna integrate the gamepad drivers?
the good news is that I was able to get the gamepad to work once I did insmod on the hid-dr file....but it doesn't remain loaded
for the next upgrade see about having the kernel load those gamepad drivers by default
btw...really would like to have this working perfectly before the 16th....this box is suppose to be a xmas present
Comment
-
Originally posted by Magendanz View PostChangelog (20171202):- Updated to latest M8S Pro L OEM firmware (20171127.165619.V0928)
- Added local update and backup option from Settings->About->System update based on Amlogic stock OTAUpgrade app.
- Latest build from Open GApps (20171202)
- Wake from sleep will usually result in a restart. This seems to be a bug in the underlying OEM firmware.
- Clicking on Vision Settings in the setup wizard will launch an unsupported activity in Settings.
- You can enable the nav bar in Settings->Display->Statusbar, but may need to toggle back and forth before it will show.
- Nano Variant: BURN PACKAGE (915MB IMG file), OTA UPDATE (471MB ZIP file)
- Stock Variant: BURN PACKAGE (1.39GB IMG file), OTA UPDATE (787MB ZIP file)
Guest here some questions:
i want to update to stock variant of this rom with usb burning tool. I understand that i have to follow your instructions:
Hit Start when you have the image loaded in USB Burning Tool, boot the device normally, connect the USB cable to the USB OTG port, and then type "reboot update" from a terminal window. The WorldCup driver should then detect the box and the flash will automatically commence.
my questions:
1) you say: boot the device normally. You mean to boot the box with the normal dc charger connected and then connect the usb a_a cable with the laptop (to keep the power) and then switch off the power charger?
2) is the configuration of the burning tool correct as i show on my picture?
3) the alternative would be to make the update with the update app which comes with the original firmware, using the ota update zip-file on a sd card or usb-pen.
But what would be finally the diference between the 2 installation methods (final result the same) ? If yes, i prefer the ota update, which seems to be easier.
Is the final result the same between the two installation options?
thanksLast edited by tombraga; 03 December 2017, 13:20.
Comment
-
1. Yes. You don't have to disconnect the power, but you probably could (because the USB OTG will provide power...if you're hub has enough).
2. Yes.
3. Yes, that's why the OTA update is also provided. Most find that more convenient.
When done correctly, the ultimate outcome should be the same, since the same partition images are flashed for both the burn package and OTA update. While the OTA update is more convenient for most, it can't change the partition map (required when upgrading from Marshmallow) and won't work if your bootloader or recovery partition is corrupted. For situations like recovery using Mask ROM mode, you'll need the burn package.
-
Guest
only to confirm:
when i install the ota zip-update file, then i have automatically the TWRP 3.1.1-0 installed, is that right?
not need to flash separately the twrp file which is also on your download-site?
in the meanwhile there is the new twrp-version 3.2.0-0 out which i have already installed on my android fone and tablet.
do you have in plan also to update this new version for the mecool box?You may only view thumbnails in this gallery. This gallery has 1 photos.1 Photo
Comment
-
Yes, you'll get TWRP now with either the OTA update (.zip file) or burn package (.img file). And yes, I was tracking the TWRP 3.2 release, but it hasn't propagated yet to the minimal OmniROM manifest that I use: https://github.com/minimal-manifest-...fest_twrp_omni
-
-
Originally posted by tombraga View Postand one more question, Guest : in this "normal" Adnroid 7.1 rom (not TV) is there the comand line below visible? I mean the home-button, volume + and - button, switch-off button and so on....
Comment
What's Going On
Collapse
There are currently 3834 users online. 1 members and 3833 guests.
Most users ever online was 37,478 at 04:14 on 26 June 2024.
Comment