Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is it?
FlashCast is a USB image that provides a standardized way to mod your Chromecast. Think of it like a recovery which runs off of a USB drive. No more struggling with the limitations of the GTVHacker image, which is hard to modify and can only flash the /system partition. FlashCast is based on shell scripts, so it you can use it to do anything you can do with a root shell. It also comes with a comprehensive suite of helper functions, so many tasks actually become much easier than they would be using a regular shell.
How do I use it?
If you prefer to follow a video tutorial, @ddggttff3 has made one here. Otherwise, read on for written instructions.
Preparation
Before you begin, you'll need some materials:
A Chromecast with a vulnerable bootloader. (For the bootloader to be vulnerable, the Chromecast must have never been connected to the internet and have a rootable serial number.)
The latest version of FlashCast (the download link is at the bottom of this post).
A USB drive (minimum size 256MB) which you are willing to have erased.
A powered Micro-USB OTG cable such as this one. (Alternatively, an unpowered USB hub and unpowered OTG cable can be used as shown here. I have not tested this method and cannot help you if your USB drive is not detected.)
Installation
Once you've gathered everything required, you can install FlashCast to your USB drive. To do so, you need to write the .bin file contained in the FlashCast .zip file you've downloaded to your drive. Simply using a file explorer to drag the .bin file to your USB drive is not correct and will not work. The specifics of doing a low-level write differ depending on OS, but, in general, Linux and OS X users should use dd and Windows users should use Win32DiskImager. This operation will erase your flash drive.
After you've written the .bin file to your USB drive, your computer will no longer recognize a filesystem on it. This is normal. In order for FlashCast to set up the drive's filesystem, you need to boot your Chromecast from the drive. To do this, perform the following steps:
Connect the male end of your Micro-USB OTG cable to your Chromecast.
Plug your USB drive into the USB-A female connector of the OTG cable.
Simultaneously hold the button on your Chromecast and connect the Micro-USB power connector to the female Micro-USB port of the OTG cable.
The power must be connected last. If it is not, your Chromecast may fail to detect the USB drive and boot up normally. If this happens, simply repeat the process, making sure to perform the steps in the correct order.
If FlashCast was copied correctly, you will see a red light on your Chromecast for approximately 9 seconds. It will then turn white and your TV will display a screen containing the FlashCast logo (shown at the top of this post) and various instructions. Once you see this screen, you may release the button. The screen will appear for another 9 seconds or so, after which your Chromecast will reboot on its own to the stock image. After it has rebooted (you may disconnect the power when it starts to boot into the stock image if you're worried about it updating), FlashCast is installed on your USB drive and ready for use. Your device is NOT rooted at this point and can still be updated by Google. To root, you need to flash a mod such as Team Eureka's Eureka-ROM. When you plug the drive into your computer, it should appear as an empty drive which you can copy files to.
Usage
FlashCast-compatible mods are distributed as .zip files. To flash a mod, simply copy it to the USB drive with the name eureka_image.zip. Do NOT use dd as you did in the previous section. If you do, you will have to repeat the whole process. Instead, just copy it onto the drive's filesystem as you would any other file. FlashCast is also capable of flashing a GTVHacker-style raw system image; if there are no native FlashCast mods present and the system image is in a file called Chromecast-Rooted-System-GTVHacker-cj_000-July27-635PM.bin, it will be flashed. This method of flashing is very inflexible and is not recommended.
How do I develop for it?
If you are interested in creating mods for FlashCast, please see the developer thread.
Who made it?
FlashCast is based on a generic Buildroot Linux image. Its mod framework was written entirely by me, but I couldn't have done it without the help of various individuals. Thanks, @cj_000, for helping me and putting up with my stupid questions in IRC. And thank you, @tvall, for releasing your update-free images so promptly up until now. Without those, FlashCast would have a much smaller potential user base.
Where do I get it?
Downloads and source code are available at FlashCast's GitHub repository. The latest version is currently v1.3.
Cool! First
Sent from my SCH-I605 using Tapatalk 4
Oh yeah, finally we can update kernels! Thanks for this, got some work to do now.
tchebb, awesome work. Your flasher seems so much more flexible than what we put out (but hell, we did it in 3 days), and it's never a problem to help out. In fact, we LOVE it when someone actually picks up on what we did and makes it so much better.
Can't wait to give it a try, once I get some free time!
CJ
vulnerable bootloader ?
How do I know if I have A Chromecast with a vulnerable bootloader ?
Looks super cool man, I am about to check it out and update my chromecasts now! Great work!!
just flashed over, working great. thanks so much!
stewwmann said:
How do I know if I have A Chromecast with a vulnerable bootloader ?
Click to expand...
Click to collapse
The initial software which the Chromecast shipped with, build 12072, had a vulnerable bootloader. In all following software versions (12840, 12940, and 13300), the vulnerability is patched and FlashCast can't be used. If your Chromecast has been allowed to access the internet, it will have updated itself and will not be vulnerable. If you have not set up your Chromecast and it still has the software from the factory, it may or may not be vulnerable, depending on when you bought it. To check, you can plug it in (but not set it up), and check its "Build" in the Chromecast app. Alternatively, you can simply try to boot FlashCast on it. If it's patched, nothing bad will happen; the USB drive will simply fail to boot.
tchebb said:
The initial software which the Chromecast shipped with, build 12072, had a vulnerable bootloader. In all following software versions (12840, 12940, and 13300), the vulnerability is patched and FlashCast can't be used. If your Chromecast has been allowed to access the internet, it will have updated itself and will not be vulnerable. If you have not set up your Chromecast and it still has the software from the factory, it may or may not be vulnerable, depending on when you bought it. To check, you can plug it in (but not set it up), and check its "Build" in the Chromecast app. Alternatively, you can simply try to boot FlashCast on it. If it's patched, nothing bad will happen; the USB drive will simply fail to boot.
Click to expand...
Click to collapse
I just got 2 units this week from Amazon and they have not been updated from the factory and thus, vulnerable.
tchebb said:
The initial software which the Chromecast shipped with, build 12072, had a vulnerable bootloader. In all following software versions (12840, 12940, and 13300), the vulnerability is patched and FlashCast can't be used. If your Chromecast has been allowed to access the internet, it will have updated itself and will not be vulnerable. If you have not set up your Chromecast and it still has the software from the factory, it may or may not be vulnerable, depending on when you bought it. To check, you can plug it in (but not set it up), and check its "Build" in the Chromecast app. Alternatively, you can simply try to boot FlashCast on it. If it's patched, nothing bad will happen; the USB drive will simply fail to boot.
Click to expand...
Click to collapse
damm, i have this 13300 version. and this will never happen or is there a way?
Updated 3 Chromecasts, thanks for the excellent work!
raydekok said:
damm, i have this 13300 version. and this will never happen or is there a way?
Click to expand...
Click to collapse
Currently there are no other known exploits.
ddggttff3 said:
Currently there are no other known exploits.
Click to expand...
Click to collapse
that is to bad. i'm hoping that it will not take to long.
raydekok said:
that is to bad. i'm hoping that it will not take to long.
Click to expand...
Click to collapse
@cammykool has been hoping that since Google forced 12840 upon him. He has given up hope.
I just finished using FlashCast on 2 ChromeCasts and everything went smooth and great! I could really see FlashCast evolving into a full blown recovery for ChromeCast!
I am thoroughly impressed with FlashCast, amazing work man, well done!
Hey guys, what's the purpose of this? Does it mean we can then use 3rd party developed apps? Apps that allow us to play local videos, etc.?
Thank You, Thank You very much....
Thanks for all the responses, I found a local Best Buy that has one, and I have put it on in store pickup for tomorrow. So if I do end up with one that has original fw, and am successful in installing flashcast, I can use the device as normal after that? no worries of it being locked back down? if we are not sure ,I just will continue using my updated one until then
stewwmann said:
Thanks for all the responses, I found a local Best Buy that has one, and I have put it on in store pickup for tomorrow. So if I do end up with one that has original fw, and am successful in installing flashcast, I can use the device as normal after that? no worries of it being locked back down? if we are not sure ,I just will continue using my updated one until then
Click to expand...
Click to collapse
If it comes with the original version, and you install an image that doesn't update, you can use it as normal and not worry about it being locked down.
cool
:good: *fingers crossed*
So if my Chromecast had been connected to my TV since release date I'm screwed huh
Sent from my Nexus 7 using Tapatalk 2
Dear fellow members, I followed the rooting Directions to the letter, and for some reason everytime I try to flash the chromecast root rom , the chrome cast lights up red and stays red and then when I take the flash drive off the cable and put it back on to the computer in order to finish the last part of the rooting process, the flash drive does not say flashcast , it says( removable disk E ) and will not let me paste the last part of the rom and will not open . I keep getting a disk needs to be formatted message. I reformatted this flash drive like 4 times and tried to flash this rom and it wont work , what do you think is wrong ? also I have never connected it to the internet or let it update. thank you in advance
Hi Wilspeak,
Just in case you don't see my post in the Eureka-ROM thread in reply to you.
Really sorry to be the bearer of bad news however the Chromecast you have purchased is not within the Rootable Serial Number range and therefore cannot be rooted at this time (as it comes from factory with a software version with no currently known exploit)
Unfortunately the highest serial numbers we are aware of working for rooting are 3922xxx and as such your 3Axx will not work. (this has been confirmed by XDA users @mrdelriego and @pandacookie)
My condolences,
Kyonz
I feel your pain man. I was planning on rooting mine but I stupidly plugged it in first and it updated.
I wanted be able to change the dns to be able to grab content from other countries without having to go through checking my router.
Bummety
Sent from my Nexus 4 using xda app-developers app
I want to know if the Team would try to develop a root method for the chromecast's that cant be rooted at this time ?
Kyonz said:
Hi Wilspeak,
Just in case you don't see my post in the Eureka-ROM thread in reply to you.
Really sorry to be the bearer of bad news however the Chromecast you have purchased is not within the Rootable Serial Number range and therefore cannot be rooted at this time (as it comes from factory with a software version with no currently known exploit)
Unfortunately the highest serial numbers we are aware of working for rooting are 3922xxx and as such your 3Axx will not work. (this has been confirmed by XDA users @mrdelriego and @pandacookie)
My condolences,
Kyonz
Click to expand...
Click to collapse
Senior Member - OP
Thanks Meter 5
Posts: 106
Join Date: Jul 2011
Location: ga
MORE INFO >
I want to know if the Team would try to develop a root method for the chromecast's that cant be rooted at this time ? Thank you
This mini-FAQ is intended to avoid clutter in the FlashCast thread.
If you have specific questions/comments/suggestions for FlashCast itself or its developer, or want to get the newest FlashCast, please use the main FlashCast thread.
Likewise, if you have questions/comments/suggestions for Eureka-ROM, its developers, or want to get the newest Eureka-ROM, please use the main Eureka-ROM thread.
IMPORTANT NOTE
The HubCap exploit has been patched in firmware build 19084. This means yet again, only certain Chromecasts can have root. It didn't take long - only about a month from the exploit's release and 2-3 weeks from the source release before a patch arrived.
If your Chromecast is on firmware build 19084 or newer, it is not rootable.
Available root methods depend on what firmware your Chromecast is running:
Original build 12072 (old US released Chromecasts only - see Rootable Serial Numbers thread for guidance)
Hardware requirements:
Powered USB OTG cable
USB flash drive 256MB or larger
Instructions: Continue reading below, past this list
If you really want to, you can use the HubCap root below instead, but it's fewer parts to try the original FlashCast method first.
Build earlier than 19084 (newer US release Chromecasts and all international release Chromecasts)
Hardware requirements:
real (does not work through hubs!) powered USB OTG cable
USB flash drive 1GB or larger
Teensy 2.0 or 2.0++ development board
USB A to Mini B cable (to connect Teensy to PC)
Instructions: Stop reading this thread. Go to HubCap thread for instructions.
The information below pertains to the original FlashCast root method for Chromecasts with the original 12072 bootloader.
First, understand how FlashCast works, and when it doesn't...
FlashCast is not really a "root tool" but rather a ROM/mod flashing utility, similar to CWM or TWRP recoveries in the phone/tablet realm. Thus, "rooting a Chromecast with FlashCast" really means flashing a rooted ROM image using FlashCast.
Currently, FlashCast will only run on Chromecasts that have the original build 12072 bootloader.
Newer Chromecasts shipped from the factory with newer bootloaders, so except for rare exceptions, only initial-release Chromecast units came with build 12072.
The serial number provides a reasonable guess at the build on an unopened, unused Chromecast - see the Rootable Serial Numbers thread
To further complicate matters, Chromecast automatically updates itself once set up, so even if you have a serial number in the range, if it has been set up with Internet access, most likely it has already been updated and FlashCast won't work on it. It is safe to try FlashCast even if you don't think your Chromecast has root potential - either FlashCast will run and you have the option to flash a rooted ROM, or it won't and you don't have root potential.
Second, check the flowcharts for First boot of a newly-prepared FlashCast stick and Flashing Eureka-ROM with FlashCast USB stick
Remember, you need a powered USB OTG cable - it needs to provide power to the OTG host (upstream, not just to OTG devices) as Chromecast needs power to operate.
REMEMBER: For a just-written or re-written FlashCast USB stick, the first boot with it does not root your Chromecast, because it does not write a ROM (which is what preserves root) until the second round, after you load the eureka_image.zip onto the stick. If you haven't put a eureka_image.zip onto the FlashCast USB stick, you have not applied a ROM yet and you are still at risk of losing root (unless you're just applying a mod or new ROM over an existing root-preserving ROM).
If you need to know why you should or shouldn't root, and why you need to decide before you start using Chromecast, check Root Mini-FAQ: What's the big deal with root?
Use of wall (utility) power is highly recommended for flashing - TV USB ports, USB power packs, and other uncontrolled or potentially-non-constant power sources can cause problems if they turn off or give out in the middle of a flash.
If you run into trouble, see below.
FlashCast doesn't show up at all.
Your Chromecast is not rootable, your OTG cable is miswired or defective, your USB stick was not imaged properly, or your USB stick is not compatible.
See these:
Piecing OTG together with Y-cable and adapter
Pictures
Long thread on OTG piecemeal workarounds
Guidelines
on proper OTG wiring/assembly if you aren't using an assembled powered OTG cable.
Here are tips for potentially writing the FlashCast image from your Android device, though using a computer is still recommended.
FlashCast shows up but only get red LED on Chromecast
FlashCast did not find your eureka_image.zip, it is corrupt, or your USB stick has errors
Windows users - make 100% sure that your file is named exactly eureka_image.zip not eureka_image.zip.zip
By default, Windows hides file extensions and this can cause misnamed files.
See this explanatory image
Also check your OTG cable - a flakey OTG cable can let FlashCast start but fail to flash too. See previous links for OTG cable assembly guidance.
FlashCast shows up, the LED is white, but all I see is the line of dots after the reboot
Check that the button on the Chromecast is not stuck down. On some units the plastic button-pusher can get wedged down. Gently but firmly push the button all the way down and wiggle it on release. If that doesn't work, try flicking the button to dislodge it.
I reached "Sorry, your Chromecast is not rootable" in the flowchart.
Try the HubCap exploit.
bhiga said:
This mini-FAQ is intended to avoid clutter in the FlashCast thread.
If you have specific questions/comments/suggestions for FlashCast itself or its developer, or want to get the newest FlashCast, please use the main FlashCast thread.
Likewise, if you have questions/comments/suggestions for Eureka-ROM, its developers, or want to get the newest Eureka-ROM, please use the main Eureka-ROM thread.
IMPORTANT NOTE
The HubCap exploit has been patched in firmware build 19084. This means yet again, only certain Chromecasts can have root. It didn't take long - only about a month from the exploit's release and 2-3 weeks from the source release before a patch arrived.
If your Chromecast is on firmware build 19084 or newer, it is not rootable.
Available root methods depend on what firmware your Chromecast is running:
Original build 12072 (old US released Chromecasts only - see Rootable Serial Numbers thread for guidance)
Hardware requirements:
Powered USB OTG cable
USB flash drive 256MB or larger
Instructions: Continue reading below, past this list
If you really want to, you can use the HubCap root below instead, but it's fewer parts to try the original FlashCast method first.
Build earlier than 19084 (newer US release Chromecasts and all international release Chromecasts)
Hardware requirements:
real (does not work through hubs!) powered USB OTG cable
USB flash drive 1GB or larger
Teensy 2.0 or 2.0++ development board
USB A to Mini B cable (to connect Teensy to PC)
Instructions: Stop reading this thread. Go to HubCap thread for instructions.
The information below pertains to the original FlashCast root method for Chromecasts with the original 12072 bootloader.
First, understand how FlashCast works, and when it doesn't...
FlashCast is not really a "root tool" but rather a ROM/mod flashing utility, similar to CWM or TWRP recoveries in the phone/tablet realm. Thus, "rooting a Chromecast with FlashCast" really means flashing a rooted ROM image using FlashCast.
Currently, FlashCast will only run on Chromecasts that have the original build 12072 bootloader.
Newer Chromecasts shipped from the factory with newer bootloaders, so except for rare exceptions, only initial-release Chromecast units came with build 12072.
The serial number provides a reasonable guess at the build on an unopened, unused Chromecast - see the Rootable Serial Numbers thread
To further complicate matters, Chromecast automatically updates itself once set up, so even if you have a serial number in the range, if it has been set up with Internet access, most likely it has already been updated and FlashCast won't work on it. It is safe to try FlashCast even if you don't think your Chromecast has root potential - either FlashCast will run and you have the option to flash a rooted ROM, or it won't and you don't have root potential.
Second, check the flowcharts for First boot of a newly-prepared FlashCast stick and Flashing Eureka-ROM with FlashCast USB stick
Remember, you need a powered USB OTG cable - it needs to provide power to the OTG host (upstream, not just to OTG devices) as Chromecast needs power to operate.
REMEMBER: For a just-written or re-written FlashCast USB stick, the first boot with it does not root your Chromecast, because it does not write a ROM (which is what preserves root) until the second round, after you load the eureka_image.zip onto the stick. If you haven't put a eureka_image.zip onto the FlashCast USB stick, you have not applied a ROM yet and you are still at risk of losing root (unless you're just applying a mod or new ROM over an existing root-preserving ROM).
If you need to know why you should or shouldn't root, and why you need to decide before you start using Chromecast, check Root Mini-FAQ: What's the big deal with root?
Use of wall (utility) power is highly recommended for flashing - TV USB ports, USB power packs, and other uncontrolled or potentially-non-constant power sources can cause problems if they turn off or give out in the middle of a flash.
If you run into trouble, see below.
FlashCast doesn't show up at all.
Your Chromecast is not rootable, your OTG cable is miswired or defective, your USB stick was not imaged properly, or your USB stick is not compatible.
See these:
Piecing OTG together with Y-cable and adapter
Pictures
Long thread on OTG piecemeal workarounds
Guidelines
on proper OTG wiring/assembly if you aren't using an assembled powered OTG cable.
Here are tips for potentially writing the FlashCast image from your Android device, though using a computer is still recommended.
FlashCast shows up but only get red LED on Chromecast
FlashCast did not find your eureka_image.zip, it is corrupt, or your USB stick has errors
Windows users - make 100% sure that your file is named exactly eureka_image.zip not eureka_image.zip.zip
By default, Windows hides file extensions and this can cause misnamed files.
See this explanatory image
Also check your OTG cable - a flakey OTG cable can let FlashCast start but fail to flash too. See previous links for OTG cable assembly guidance.
FlashCast shows up, the LED is white, but all I see is the line of dots after the reboot
Check that the button on the Chromecast is not stuck down. On some units the plastic button-pusher can get wedged down. Gently but firmly push the button all the way down and wiggle it on release. If that doesn't work, try flicking the button to dislodge it.
I reached "Sorry, your Chromecast is not rootable" in the flowchart.
Try the HubCap exploit.
Click to expand...
Click to collapse
thnx:good:
My Chromecast is running the latest firmware, so it's not rootable. But out of curiosity, aside from developers, what would be the benefit of rooting Chromecast?
@Laserbeak43 - see [FAQ] Root Mini-FAQ: What's the big deal with root?
Hello everyone, I have question is there also something for this for the chromecast 2 where you can cast and make the setup without any internetconnection ? I hope somebody can help me with this. already thanks for the reply.
Hi,
I always found it saddening to notice EZCast5G (the "original") is updated at first and their knock offs are updated way later (as of writing this, there is 16602000 for EZCast5G, 16403000 for MiraScreen5G).
The update tool let's you easily analyze the update process. And if you fake the reply from this URL with (for example) miniweb to always dish out latest EZCast5G firmware then your knock off will become an original.
These are the requests made for a legit EZCast5G and a MiraScreen5G:
Code:
[COLOR="Purple"]curl http://www.iezvu.com/upgrade/ota_rx.php -d "{\"version\":1,\"vendor\":\"ezcast5g\",\"mac_address\":\"authorshxj\",\"softap_ssid\":\"000000-00000000\",\"firmware_version\":\"16602000\"}"[/COLOR]
[COLOR="Blue"]curl http://www.iezvu.com/upgrade/ota_rx.php -d "{\"version\":1,\"vendor\":\"am8252_nand_mirascreen\",\"mac_address\":\"authorshxj\",\"softap_ssid\":\"000000-00000000\",\"firmware_version\":\"16403000\"}"[/COLOR]
These are the official replys where you need to always dish out the first one and the update tool will do the rest:
Code:
[COLOR="Purple"]{"ota_conf_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.conf","ota_fw_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.gz","ota_enforce":true}[/COLOR]
[COLOR="Blue"]{"ota_conf_file":"http://cdn.iezvu.com/upgrade/am8252_nand_mirascreen/am8252_nand_mirascreen-16403000.conf","ota_fw_file":"http://cdn.iezvu.com/upgrade/am8252_nand_mirascreen/am8252_nand_mirascreen-16403000.gz","ota_enforce":true}[/COLOR]
When I opened mine it even read "5G EZCAST V1.4" on it - so I was pretty sure it should work. And it did. So for $17 one year ago I got myself a neat working EZCast5G. The MiraScreen5G gets into bootloader mode by pressing the one and only button right when you plug it into USB - no need to shorten pin 19 and 20 of the AM8252.
Thank you.
Some questions.
How to use this curl command with miniWeb?
Hi,
BUMP
No honestly, could you elaborate how this works ? Have 2 MiraScreen5G dongles...
Ender
Hi,
with some help from Chatty and another forum i got it done !
First i needed to add a line to my hosts file:
(On windows its found in C:\Windows\System32\drivers\etc)
Code:
127.0.0.1 www.iezvu.com
Then i downloaded miniweb and created a file containing the desired server answer.
Miniwebs web root resides in the "htdocs" folder by default, so i created a folder named "upgrade" and in that folder a file named "ota_rx.php.
I edited that file to contain this text:
Code:
{"ota_conf_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.conf","ota_fw_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.gz","ota_enforce":true}
I fired up miniweb with the parameter "-p 80" to listen on the stabdard web port.
THEN i started the EZ Updater app, connected my dongle in Flash mode and VOILA it detected the version i wanted it to detect.
So it flashed (took forever with several loops) my MiraScreen5G to a EZCast5G !!!!
After that initial update the dongle detected a newer version and updated okay.
Please note that AFTER the update you cannot get into flash mode by simply pressing the key. I assume that key is not considered existing anymore since the EZCast5G has none as well
So for further flash-fun we need to short the Pin like its descived by Chatty !
THANKS Chatty & all,
Ender
Just opened a K6 mirascreen and found these
nanya nt5cb64m16fp-dh 128mb ddr3 ram
am8272
samsung k9f1g08u0d 16mb flash
the pcb reads S?-EZCAST-8271-V2F
im unable to find a suitable firmware for it and no idea how to enter download mode....
---------- Post added at 06:02 PM ---------- Previous post was at 05:35 PM ----------
the firmware says 1.3707.11 btw
Hey Guys,
If someone knows, please share the knowledge.
Few Months ago when I was updating the firmware, my Dongle died due to power cut.
after reconnecting my PC couldn't read the version of my dongle. Today I wanted to revive my Dongle But have no to little experience on the Windows Debugging. I know my Dongle is not dead and it has no firmware, I also know that EZCast Repair tool can Flash the Firmware to it, I can download the firmware using the OP, I can also see that The App has options for Manually flashing the Firmware.
But I don't know how and what to do to access the areas shown in the Screenshot.
anyone please help me and point me to right direction.
Thanks in Advance.
SweenWolf said:
Hey Guys,
If someone knows, please share the knowledge.
Few Months ago when I was updating the firmware, my Dongle died due to power cut.
after reconnecting my PC couldn't read the version of my dongle. Today I wanted to revive my Dongle But have no to little experience on the Windows Debugging. I know my Dongle is not dead and it has no firmware, I also know that EZCast Repair tool can Flash the Firmware to it, I can download the firmware using the OP, I can also see that The App has options for Manually flashing the Firmware.
But I don't know how and what to do to access the areas shown in the Screenshot.
anyone please help me and point me to right direction.
Thanks in Advance.
Click to expand...
Click to collapse
Have you found any help? I have updated to EzCast firmware but now my dongle doesn't appear on wifi list and on TV only shows EzCast logo..
dLightas said:
Have you found any help? I have updated to EzCast firmware but now my dongle doesn't appear on wifi list and on TV only shows EzCast logo..
Click to expand...
Click to collapse
No I found no help.
All I need is access the flashing area.
I had 2 tools laying around (think i deleted those)
One was older and directly opened the firmware flashing page, but that doesn't have the partition table of My Dongle.
And the other tool which have the partition table, opens on main page (which is automated and does nothing)
If somehow i could access the firmware flashing area on the newer tool then I could revive my dongle.
If your dongle contained older chip of Action Electronics (earlier than 52) then the older tool can flash your dongle.
nostupidthing said:
Just opened a K6 mirascreen and found these
nanya nt5cb64m16fp-dh 128mb ddr3 ram
am8272
samsung k9f1g08u0d 16mb flash
the pcb reads S?-EZCAST-8271-V2F
im unable to find a suitable firmware for it and no idea how to enter download mode....
---------- Post added at 06:02 PM ---------- Previous post was at 05:35 PM ----------
the firmware says 1.3707.11 btw
Click to expand...
Click to collapse
Today there was a firmware upgrade available and after updating it's dead any help
Edit: OK I was able to flash using this tool (https://mirascreen.com/pages/repair-tool-for-chip-8272-products) but still nothing comes up...
Edit 2: The new firmware is 1.10505.52
MiraScreen G9 Plus
=================
[Name Model] , [Vendor String] , [Supported of the "MiraScreen G9 Plus"]
(EZCast5G) - ezcast5g - Not supported
(MiraScreen5G) - am8252_nand_mirascreen - Not supported
(EZCast 2H) - am_8270_ezcast4k-dongle_ezcast2h - Not supported
(EZCast TX) - am_8270_ezcast-tx_nand-std - Not supported
(EZCast 2) - am8271_ezcast2K - Not supported
(EZCast 4K) - ezcastduo - Not supported
(EZCast Band1) - am_8271_ezcast2-dongle_b1 - Not supported
(EZCast Ultra) - am_8275_ezcast-dongle_ultra - Not supported
(AnyCast M100) - sage_8272_mirascreen-dongle_anycast - Supported
(MiraScreen K6) - am_8272_mirascreen-dongle_std - Supported
Check Firmware over http api:
https://api.ezcast.com/api/firmware...mirascreen-dongle_std&firmware_version=1.10.3
https://www.ezcast.com/service/ota/..._8272_mirascreen-dongle_std&rx_version=1.10.3
Current official firmware version for the "Mirascreen G9 Plus": 1.10505.61
Do you know others? I would for the model "Mirascreen G9 Plus"?
"Mirascreen G9 plus" supports alternative Firmware (Firmware tested on the "MiraScreen G9 Plus"):
FW v1.13610.47: http://cdn.iezcast.com/upgrade/am_8...dongle_std_official-1.13610.47-0x99A7C4FD.img
Flash Tool: https://cdn.shopify.com/s/files/1/0017/6553/9884/files/MiraScreen_8272_Repair_Tool.rar
FW v1.10505.3: http://cdn.iezcast.com/upgrade/sage...gle_anycast_official-1.10505.3-0x937AC2AD.img
Flash Tool: https://cdn.shopify.com/s/files/1/2427/2515/files/AnyCast_M100Repair_Tool.zip
Small modification of Wi-Fi antenna:
https://forum.xda-developers.com/t/mirascreen-g9-plus-hw-fw-mods.4391225/
Hi to all, can anyone help me please with my EZ mira app and dongle device associated with it (miracast).
I have tried to upgrade software for my miracast device thru EZmira app, but suddenly Commercials pop up and my upgrade has been stuck at 10% and won't go further , worse after disconnect or reset there is no signal at all anymore it does not start /boot nor emmit wifi signal. What to do (because of stupid commercial)??
I tried to reset device several times but nothing, tried reseting thru PC but it does not load or Windows does not recognoze device to upgrade it thru web tools.
Please can anyone get that firmware back in my device and restore it .
Much appriciated and thanks in advance!
Anton TNT said:
Hi to all, can anyone help me please with my EZ mira app and dongle device associated with it (miracast).
I have tried to upgrade software for my miracast device thru EZmira app, but suddenly Commercials pop up and my upgrade has been stuck at 10% and won't go further , worse after disconnect or reset there is no signal at all anymore it does not start /boot nor emmit wifi signal. What to do (because of stupid commercial)??
I tried to reset device several times but nothing, tried reseting thru PC but it does not load or Windows does not recognoze device to upgrade it thru web tools.
Please can anyone get that firmware back in my device and restore it .
Much appriciated and thanks in advance!
Click to expand...
Click to collapse
Do you have a specific device?
Manufacturing publishes tools to restore some firmware here:
EZCast: https://www.ezcast.com/repair
MiraScreen:
https://mirascreen.com/pages/repair-tool-for-chip-8268-8252-products
https://mirascreen.com/pages/repair-tool-for-chip-8272-products
AnyCast:
https://any-cast.com/pages/repair-tool-for-chip-8268-8258-products
https://any-cast.com/pages/repair-tool-for-chip-8272-products
renda-l said:
Do you have a specific device?
Manufacturing publishes tools to restore some firmware here:
EZCast: https://www.ezcast.com/repair
MiraScreen:
https://mirascreen.com/pages/repair-tool-for-chip-8268-8252-products
https://mirascreen.com/pages/repair-tool-for-chip-8272-products
AnyCast:
https://any-cast.com/pages/repair-tool-for-chip-8268-8258-products
https://any-cast.com/pages/repair-tool-for-chip-8272-products
Click to expand...
Click to collapse
I have trided this solution , but no prevail, like device is dead, nothing just blank screen after failed update
Anton TNT said:
I have trided this solution , but no prevail, like device is dead, nothing just blank screen after failed update
Click to expand...
Click to collapse
This procedure works 100%, completely restores the firmware. If only an incorrect update occurred.
renda-l said:
This procedure works 100%, completely restores the firmware. If only an incorrect update occurred.
Click to expand...
Click to collapse
I'm not shure maybe I'm doing something wrong, but even windows doesn't recognize device
Anton TNT said:
I'm not shure maybe I'm doing something wrong, but even windows doesn't recognize device
Click to expand...
Click to collapse
Yes, of course, if the firmware is faulty, the device is not recognized and does not work. You must follow the Firmware Recovery Procedure. The device will most likely be repaired. Unfortunately, unless you specify a specific type, you can't be specifically advised on how to proceed.
renda-l said:
Yes, of course, if the firmware is faulty, the device is not recognized and does not work. You must follow the Firmware Recovery Procedure. The device will most likely be repaired. Unfortunately, unless you specify a specific type, you can't be specifically advised on how to proceed.
Click to expand...
Click to collapse
It is MIRACAST, I dont know chip number but it is dongle type round shaped eith EZmira app controlled
Anton TNT said:
It is MIRACAST, I dont know chip number but it is dongle type round shaped eith EZmira app controlled
Click to expand...
Click to collapse
Set your device to Recovery mode according to the procedure and use the tool for chip 8268/8252 or 8272. If the response is "device connected", it is a given chip set.
renda-l said:
Set your device to Recovery mode according to the procedure and use the tool for chip 8268/8252 or 8272. If the response is "device connected", it is a given chip set.
Click to expand...
Click to collapse
on which side is pin 7 and 8 ? Chip on my board is square shaped and got pins on all sides. Just to be sure not to fry anything, which side is NAND memory
Anton TNT said:
on which side is pin 7 and 8 ? Chip on my board is square shaped and got pins on all sides. Just to be sure not to fry anything, which side is NAND memory
Click to expand...
Click to collapse
If your device has a button, first try to enter recovery mode, press the button and connect USB.
In the procedure is a photo of the MCU and these pins are shown.
Hi All.
I trust you well. I was wondering if I could request your assistance with updating my TF701T to a new version of android. I have tried many methods and none has worked. I am actually more confused now as to where to start and what to download and install. :silly:
If possible maybe direct me where I could get a step by step guide with the links to the correct downloads/procedure.
I imported the pad from USA to South Africa and barely used it.
Kind Regards
Rob
(h-tee-tee-pee-s) androidbiits.com/root-asus-transformer-pad-tf701t-easily/
probably use the versions of magisk + twrp that are linked at the site, as they are tested with that hardware -- the latest versions may not work. i do not own that particular device and am not a programmer -- just trying to help you out. search the web for info if anything is confusing in the instructions -- i can't really walk you through it, but the person at that site may be able to help you out if you get stuck.
you'll need to connect the asus pad to a computer, so you'll need the usb data cable & adb installed on the computer.
you will likely also need open gapps to get the play store + apps working. select processor type, android version, then variant. you can find it here ==> (h-tee-tee-pee-s) opengapps.org <== but i'm not sure how long that will be functional, as hosting is apparently migrating to sourceforge.
please note that there are no w's in either address mentioned previously.
here's an explanation of gapps ==> (h-tee-tee-pee-s + w's) androidfreeapks.com/apk/download-gapps-for-android/
...and there are also download links for various variations at that last address too. cheers!
you will not be able to install *the latest* version of android (it's just plain not out there as a mod for a device this old) but you *can* get something a bit newer than the stock version on it.
best of luck!
one last thing (pertaining to the very first thing you have to do) is unlock the bootloader.
(h...s + w's) asus.com/us/Tablets/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
you will find the utility to do so at the above site. select Android, then under "Utilities"
click "See All Downloads" - therein, the 2nd thing from the bottom in that section is the unlock tool,
which says: Unlock Device App. V1.o (there's only one thing with that name. size is 448.82 kb)
and it will only work from the stock Android version, which i assume is still functional on your device.
Magisk is apparently a newer replacement for SuperSU, which doesn't flag the system as altered...
therefore you *may not* need to install Gapps if using Magisk - that seems logical to me, but i am not certain.
thanks for the assistance Dorkus.........this is killing me....but I will keep the faith and try again
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
bobwho said:
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
Click to expand...
Click to collapse
Same here. I tried to contact Asus but no hope... We're completely blocked unless they do something? No other way to unlock?
greetings all, it is i, dorkus, of the house of mallorcus. haha. my name is actually reni.
xda keeps locking me out for some reason. i've now created 2 accounts (3 including the one from which this comment is posted) one even with a dedicated e-mail address just for this, but if i try to log in with either one, i get some "invalid" whatever message. admins: what have i said that was grossly incorrect? those links may not be presented in absolutely the most coherent way, but they're the best reasonable explanations of the procedure involved that i could find with about an hour or 2 of research, which i did because of intending to get one of these devices myself (which has now occurred! yay). besides that, who else with greater experience has chimed in on this thread? yes, i've reset my password, on both accounts. after i do so, both times: same "invalid" message. it's wasted over an hour of my time, when i'm just trying to help these people. it's highly annoying & if it continues, well, they'll just have to go it on their own.
to the point:
as luck would have it,
i was able to acquire one of these devices, still in superb condition, for a great deal from ebay. i have been in contact with Asus support & the word is: it's an EOL product, so the unlock servers have been shut down & there is currently no recourse end users have for unlocking their devices. i feel it's doubtful that they'll fire up a server again, but maybe we can pester them enough to develop a fastboot unlock tool? it sure would have been nice if it worked like that in the first place, but oh well, like the song says:
you can't always get what you want.
i will surely let you all know if am able to make any progress on unlocking my TF701T.
footnote: i also have a TF700 model which is in fact unlocked, has TWRP installed, and is running Android 5.1.1 {zombie-pop} which works a bit better than the Cyanogen mod flavor that it came to me with: somewhat improved user experience, maybe a little snappier too, but speed improvement is fairly minimal. most importantly, almost all of my apps work on it - a few don't even have an installer for Android 4 at the Play Store. the 701 is noticeably more responsive than the 700 model, even running 4.2.2 - the main issue with it for me is not being able to run all of my apps, some of which are purchased. i'd probably sell the 700 if i could get everything on the 701. oh well. it's an excellent reader + portable video viewing device even at stock. it's definitely worth what i paid in the condition received, but it'd be even better if i could unlock the bootloader & get a newer version of Android on it! i could possibly even be so happy that i'd float a couple bux Tim Duru's way, the guy primarily responsible for porting Android 6+7 (the latter of which apparently does not have a working camera) to this device.
footnote #2: the first day i got the 701, i tried to do a firmware update (proper region, latest available. full battery charge. the battery in the one i picked up is in fantastic condition, the thing is practically brand new + functions nicely... but now Asus won't let me unlock it, even though it's well out of warranty! grrrrr) which crashed mid-way & then it proceeded to get into an update / crash boot loop. i was pretty sad for a while, but did not give up & found a way to restore the original firmware (which turned out to be a very minor upgrade) from the SD card, thanks to information in a post here in the xda forums. that post is the link which follows. my thing would still go into fastboot (albeit slightly corrupted) + recovery mode, which enabled an SD card firmware flash to happen {...and lo, my little slab of Jelly Bean was resurrected...} so i did not require the NvFlash tool at all... but it's still there at the provided links in that thread.
to summarize the procedure:
1) format an SD card to fat32
2) download the appropriate firmware from Asus [**please note the region: if you flash the firmware from a wrong region onto your device, you will -hard- brick it + will then be required to use the NvFlash tool**]
3) un-zip the firmware (not completely, just remove nesting - so you have only one zip file)
4) rename the one remaining zip file: t4_sdupdate.zip
5) put that file on the root directory of SD card, then into the tablet (while turned off)
6) invoke recovery mode (power + vol down) & choose the recover [RCK] box (hit volume up, while it's the selected of the 3 choices) and from there the firmware update happens automatically. you can apparently upgrade to any official firmware by this method, but **cannot** downgrade... so i'd suggest leaving it at 4.2.2 until we are 100% sure that there are zero bootloader unlock options, because apparently the unlock tool, from what i understand, only works from the original 4.2.2
without further ado:
https://forum.xda-developers.com/transformer-tf701/tf701t-nvflash-unbrick-solutiontested-t3742848
it's now a few hours later from my original post, near bedtime for me, and the xda gods let me log into this account to make this edit... and it's even allowing URLs now! will wonders never cease? not sure what the problem was earlier, but it was quite annoying. anyway, if it lets me log into the account with the dedicated xda e-mail address, that's the one i'll use in future. username is renigade.
fly a kite said:
...
Click to expand...
Click to collapse
Hello @fly a kite @dorkus mallorcus @renigade
Please consult the inbox of your private messages. Thanks for your cooperation!
Stay safe and stay healthy!
Regards
Oswald Boelcke