yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] Asphyx:
If the new image flash yields the same result then the unit has a issue with the Video output. Probably time to replace the unit.
[Google Chromecast] l_aios:
Had the same issue being stuck at "Chromecast..." boot part. Was also able to recover by flashing the hubcap image, twice (got quickly updated again).

So, is there a way to block current updates e.g. by blocking the update servers? Like putting them on the router's blacklist after the initial update after Autoroot?

Edit:

Found a response from ddggttff3 regarding a similar request:

https://xdaforums.com/showthread.php?p=49068616

From what I understand (and given it's still the same) there is no way to bypass the Google OTA updates by a simple blacklist entry, because many functions are dealt with server-side.

In addition, staying on EurekaROM (hubcap version) seems to be no option for me. For example Twitch streams don't start and seem to be stuck buffering.

Maybe I'll try a more recent version before going back to Autoroot and Google.
[Google Chromecast] Asphyx:
Before we all panic and wonder if stopping updates is an option....

Remember that this issue could just be a product of this particular release and may not be a big deal.

It wouldn't be the first time Google issued an Update that bricked or borked a CCast.

The fact we are Rooted and have options to put a good firmware on the device is just another reason to be rooted at all.

Stopping Updates is only going to lead to the device not working or losing out on new features or content that will require up to date firmware.

Just keep that USB drive handy or go buy a dirt cheap flash drive just big enough to hold Eureka so if this ever happens again you have a way to recover easily.

Maybe someone will take on the project of making an image we can flash that already has the Autoroot installed to make it easier in future,

But I can't see why anyone would spend the hours to do that just to save the rest of us the 4 or 5 minutes it takes to re-do the autoroot.
[Google Chromecast] Crussader:
Here in Spain it's the same... It sits on "Chromecast..." and does nothing.

I can enter to team eureka bootloader but it ends up with a red light in the Chromecast.

Any ideas please?
[Google Chromecast] Mad07:
Same here....

there only 2 different behavior :

1) black screen with the text "Chromecast...." and nothing more

or

2) an update message, but the red light is lighting all the time

Reset ( 25 Sec. hold the button) doesn't help

Via flashing the old Eureka Vers 1.2 via USB , the Chromecast is at minimum back to life.

After that, following the instruction on the initial post from this thread to install the autoroot... (telnet to the chromecast ; busybox........)

# busybox wget http://pdl.team-eureka.com/recovery/install.sh -O /cache/install.sh

Connecting to pdl.team-eureka.com (95.170.82.169:80)

install.sh 100% |*****************************************************************| 3381 0:00:00 ETA

# busybox chmod +x /cache/install.sh

# /cache/install.sh

AutoRoot-Recovery: Running AutoRoot-Recovery Installer!

0

AutoRoot-Recovery: Downloading now...

AutoRoot-Recovery: Recovery Downloaded Successfully!

AutoRoot-Recovery: Verifiying Recovery...

AutoRoot-Recovery: File Verified Successfully!

AutoRoot-Recovery: Downloading Google OTA...

AutoRoot-Recovery: Verifying Google OTA...

AutoRoot-Recovery: Google OTA Verified! Moving file...

AutoRoot-Recovery: Flashing Recovery...

mtd: successfully wrote block at 0

mtd: successfully wrote block at 100000

mtd: successfully wrote block at 200000

mtd: successfully wrote block at 300000

mtd: successfully wrote block at 400000

mtd: successfully wrote block at 500000

mtd: successfully wrote block at 600000

mtd: successfully wrote block at 700000

mtd: successfully wrote block at 800000

mtd: successfully wrote block at 900000

mtd: successfully wrote block at a00000

mtd: successfully wrote block at 0

First block failed verification at byte 8 of 10743808. Wrote 11 replacement blocks to recovery.

AutoRoot-Recovery: Process Complete! Cleaning and rebooting...

In this moment it is working on my side... hopefully also after reboot ;)

In this moment the version 1.17 is running... It's the question, at which moment the update to 1.22xxxx will be occurred
[Google Chromecast] mcpdigital:
The same here in Brazil. Reinstalled the HubCap and Autoroot. It worked with the old version and updated again to the latest Google version and it is stuck again.

All 4 rooted CC are in the same status. chromecast....

I've received the exact same results as Mad07.

Ouch, how can I stand the kids wanting to kill me ?

Is there a guide of how to reset to factory Google original ??? I can afford loosing root in one of them.

Thanks !
[Google Chromecast] Mad07:
I don't know, if a Google update will be override the recover partition.

That is the last action, which will be override in the install.sh

Maybe it will be enough to add a "#" before the command "flash_image --scan-all recovery /data/temp/root-recovery.img".

On other hand, I'll believe, that an OTA will not touch this area. I'm afraid, that if we haven't an original image of the recovery area, we will have a problem... at min. in the next time.

Also don't forget : we still have change the Recovery partition.

The interesting thing is:

the first CC is in this moment on version 1.17 (this onw, whkch I must reanimate yesterday)... the next updates will we come in the next few days.

The second CC is still on the latest version and worked without any problems. This CC has the same procedure behind as the first one. So there is a change, that the update will be going well. Maybe after the xx try...

The only different is, that from the first CC the country code is CH. Maybe this one must be changed back in the Eureka Image.
[Google Chromecast] mcpdigital:
I have tried in 2 distinct CCs with the same results - stuck at Chromecast....

Tried 3 times at least. As soon as the updates are installed it is back to the same.

Mad07, yes I was looking for an original recovery image since the OTAs available does not have it.

The same conclusion, need the original image.

I really do not get why this image is not available without needing to beg someone to send it.
[Google Chromecast] clubs07:
https://xdaforums.com/showpost.php?p=71674065&postcount=118

I tried to flash it with Flaschast but it fails.
[Google Chromecast] Crussader:
I've flashed and old version and it boots but I can't really use the Chromecast... Is not visible even though it's configured
[Google Chromecast] Crussader:
I mean old version of the Eureka's Chromecast Rom... I still got the very first USB dongle I've used to root it

Funny thing.. it doesn't update
[Google Chromecast] ZaneChua:
I don't think any of the fixes here works. The chromecast still auto updates after reboot and it gets stuck at a black screen just showing "chromecast"
[Google Chromecast] Mad07:
Till you didn't install the AutoRootfrom the first post of things thread , the CC will be not updated at all
[Google Chromecast] Asphyx:
it is the 1.23.84839 Firmware that is causing this issue....

And I also noticed that the Autoroot when it does it's update uses an earlier version of the firmware that then gets updated to 1.22.80438.

That Firmware also works until it tries to update to 1.23.84839.

So I'm wondering if Autoroot downloads the update from a set location but Google changed the location of where those updates are found.

Since Autoroot can't find the image it can't flash it and fails.

And I'm wondering if this is just going to happen on this particular update or if once Google releases a new one it might work again.
[Google Chromecast] ZaneChua:
Yes. You are correct. The 1.23.84839 is the one that is only available to US Chromecast Devices now. This is the firmware that is breaking the auto root. I've actually been doing some debugging into this issue.

No, it's not that Google changed where the location of the updates are found. The original script will load 46278. I've tried force installing 1.22.80438 and that works fine actually. I then tried loading 1.23.84839 directly onto the chromecast via an OTA link and that does not work at all.

The OTA for 1.23.84839 can be found at http://redirector.gvt1.com/edgedl/g....d6f360302fb7115e7825d1402539e725bac905d0.zip.

I'm trying something based on adammw said previously and will report back if I have something concrete.
[Google Chromecast] Asphyx:
That looks like it comes from Eureka and not Google....

Is it as simple as maybe Eureka just got a bad copy of the firmware?

Or have you tried that already?
[Google Chromecast] l_aios:
I see your point and my post regarding stopping updates wasn't intended to be negative in any way. I appreciate the work from all devs that led to this point.

I just wanted to say, in my case I may have to find a way to stay on a semi-up-to-date version, because my Chromecast is not able to handle Twitch streams on the hubcap EurekaROM version, which is its main usage for me lately.

Before it fetches the "faulty" update from Google (please pardon my lack of version knowledge), it does work fine with the initial Autoroot-included version, but does fall back to updating after a couple of hours, which renders it unbootable again.

So again, I appreciate anything that has been done so far and I'm sure there will be a simple solution.
[Google Chromecast] ZaneChua:
Did you see the link? It's from Google. Not Eureka. The chromecast device codename is eureka.

Following adammw's suggestion.

He didn't really give instructions or anything to help you do this though. Something in the boot.img has changed and therefore breaks autoroot. I decided to use the boot.img from 1.22.80438 to replace the original one in 1.23.84839.

You need to reinstall eureka rom and be on a clean installation of eureka rom. Means you need to do a factory reset before you try any of the steps below.

You can find the new OTA from: https://drive.google.com/open?id=0B3jenDHaF8AJMFZMbHVMNmFyeFE

The script is slightly changed to : https://gist.github.com/zanechua/672f741de2add4186e59dd1973663305

You still need to modify the script, host it on your own http server and modify the script accordingly.

You could however do it manually but this may/may not break your chromecast. I'm not at fault here if you do.

I HAVE NOT PERSONALLY TESTED THE FOLLOWING COMMANDS. THESE COMMANDS ARE FOR EXPERTS ONLY. IF YOU HAVE NO IDEA WHAT THESE COMMANDS DO, DO NOT DO IT. THIS CIRCUMVENTS A LOT OF CHECKS IN THE SCRIPT.

The commands would be:

busybox wget http://pdl.team-eureka.com/recovery/releases/autoroot-recovery-r02.img -O /data/temp/root-recovery.img

busybox wget http://fromsomewhere/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip -O /data/temp/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip

busybox cp /data/temp/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip /cache/ota.zip

flash_image --scan-all recovery /data/temp/root-recovery.img

(Wait 5 seconds after flashing of the recovery)

reboot
[Google Chromecast] Asphyx:
Well I only caution you before you did something that couldn't be undone and pretty much turn the device into a useless dongle...

The only Stock Rom I know of that you can use is one that stops updates from happening...

Which is actually pretty old now and a lot of things that work on current firmware likely won't work on that version and with no update you are stuck in that time and firmware...

It might be a bit inconvenient for those who rely on their CCast to do everyday stuff while this gets sorted and in the end if it doesn't get sorted I suspect a solution to go back to true stock will be developed.

But this may be just a minor hiccup that just affects this one single version of the firmware and it is better to be patient than just rushing to a half assed solution you're stuck with for life.

Even if the worst case scenario becomes the reality and there is no real fix...Considering how much a new CCast costs it almost makes a ton of sense to just get a new unit to hold you for the time being and store the rooted units until a final fix is found.

---------- Post added at 10:29 PM ---------- Previous post was at 10:20 PM ----------

So basically what you are saying is we need to update the autoroot-recovery image to work with the new bootloader Google is using...

Or hack the OTA zip to use a different bootloader....
[Google Chromecast] ZaneChua:
Probably need to update the autoroot-recovery image to fix this issue.. I'm pretty new to this but I'm trying to see if i can compare the file changes between both boot.img's.

Not a different bootloader. Different kernel. bootloader is not boot.img
[Google Chromecast] Asphyx:
Well the source is available on Github...

https://github.com/team-eureka/flashcast-flasher/tree/newmode-alpha

So it might be possible to make the changes needed to Git and recompile...But I guess you first have to figure out what actually needs changing first.
[Google Chromecast] ZaneChua:
Yeah. probably need to find out what's causing the hang on the words "Chromecast...". If replacing the boot.img works then it's definitely something in the boot.img that has changed.
[Google Chromecast] Asphyx:
Lets just hope it isn't a root check because that might make a fix difficult...

Unless we can find a way to make our own and even then makes future updates a PITA!
[Google Chromecast] mcpdigital:
Deleting, I think you already provided it with the boot.img from 1.22 if I understood correctly. Thanks

ZaneChua, updated using the modded 1.23 with 1.22 Kernel. It worked, it is now on the 80438 version.

Let´s hope the next update won´t mess with it again. Until then we have to wait.

Just to clarify. I started with the Hubcap Eureka and then I took the risk and entered the commands only, no script no factory reset.

Now it is easy to copy and paste to the telnet terminal.

I will leave the file that I used in my server for a day so users can install. It is a small hosting plan so not that much bandwidth available.

*** Remember, I did that and it worked, but I'm not responsible for any damage this can make to your CC ****

An thanks to ZaneChua for finding the 1.22 Kernel (boot.img)

Copy and Paste in you telnet:

busybox wget http://pdl.team-eureka.com/recovery/releases/autoroot-recovery-r02.img -O /data/temp/root-recovery.img
busybox wget http://mcpdigital.com/android/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip -O /data/temp/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip
busybox cp /data/temp/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip /cache/ota.zip
flash_image --scan-all recovery /data/temp/root-recovery.img
// *** WAIT FOR 5 SECONDS
reboot recovery

Update: Did the same procedure in other 2 CCs.

So now I went from stuck at Chromecast.... straight to the update:

Step1: create a HubCap Eureka USB from image

Step2: install the HubCap (OTG+USB, Reset Button, and Power) * no need to root CC again so it is like the second step of the original Eureka.

Step3: wait until it updates itself from 17977 to 44333 , it shouldnt take long

Step4: telnet your CC and run the busybox commands as showed by ZaneChua

Step5: enjoy

MCP
[Google Chromecast] ZaneChua:
Your chromecast says 80438? Mine says 84839 as the latest firmware when i check via the Google Home App.
[AT&T LG G2] Pritster5:
So recently, i updated from CM12 (some nightly build) to CM13 following this guide titled: Update LG G2 with Android Marshmallow via CyanogenMod CM13 custom ROM [How to instal] ( I Can't link it because I'm a newbie apparently).

Now, if I try to boot my phone, the LG logo appears on the screen for about a half second then disappears, then the screen is very dully illuminated with absolutely nothing on the screen. As of right now, I can access TWRP (2.8.6.0) and do anything that TWRP allows me too.

In fact, when I installed the CM13.zip it said it installed successfully in the TWRP log window. I can also connect to my PC via MTP and add files to the phone (maybe add .img files that could solve this?). Is there anyway to fix this problem using the capabilities listed above?

EDIT: I also do not know which boot-loader I had. I was coming from android lollipop CM12, so I assumed it was bump.
[AT&T LG G2] Subtleone:
You might try reflashing CM12, but if all else fails you can go back to stock from Download mode and start fresh.

http://xdaforums.com/showthread.php?t=2663369
[Galaxy S 5 Q&A, Help & Troubleshooting] Joe333x:
I have an S5 that came from T-Mobile with 5.1.1. I want to go back to Kitkat. I've tried flashing Kitkat roms and also Odin to flash stock firmwares, nothing seems to work. Am I stuck or is there a way to roll back?
[Galaxy S 5 Q&A, Help & Troubleshooting] dwadefanatic:
Guess not

From what I've been told, you can't flash back down firmwares
[Galaxy S 5 Q&A, Help & Troubleshooting] geo2bobbyb:
:good:
[Galaxy S 5 Q&A, Help & Troubleshooting] -Majkel-:
I had lolipop 5.0.1 SM-G900F yesterday and I can tell you that I succeed on downgrade. I now have 4.4.2 but there is one problem, Towelroot don't work anymore so if you want to downgrade your software you can do it by downloading it from sammobile. If you want root it without knox you probably don't find any solution, if you want to mind hit knox you can use chain-fire. I could not find anything that will root it without hiting knox.
[Galaxy S 5 Q&A, Help & Troubleshooting] ddomingues:
Agreed. It it very doable to downgrade back to KitKat but the only thing I found to reroot is Chainfire as well.
[Galaxy S 5 Q&A, Help & Troubleshooting] HustleberryFinn:
Just downgrade to the latest 4.4 with ANE2 Baseband - so Towelroot will work without any problems.
[Galaxy S 5 Q&A, Help & Troubleshooting] androidtweaker1:
If you are on 5.1.1 you cannot downgrade, downgrade was possible on 5.0.x
[Galaxy S 5 Q&A, Help & Troubleshooting] ddomingues:
Joe is your phone rooted? I have the same exact same phone and have successfully rolled it back. If not rooted, here are some links to help you out and then you can flash whatever rom you like. If you are on OG6 use this link: http://xdaforums.com/tmobile-galaxy-s5/development/root-kernel-root-method-fog6-5-1-1-t3178077 or if you are on OF6 use this link: http://xdaforums.com/tmobile-galaxy-s5/development/root-kernel-root-method-fof6-5-1-1-t3158005 After getting root, flash a custom recovery like Philz Touch or TWRP and flash whatever rom you're looking for. Here is also a link to the T-Mobile section of this forum: http://xdaforums.com/tmobile-galaxy-s5/development Everything you need is there.
[Asus  Eee Pad Transformer Prime] amit_26:
hi. I have prime and it is stuck into twrp screen with just teamwin screen keep on flashing. nothing happens and it doesn't boot into recovery(twrp) also. tried to boot into bootloader by holding power button and volume down but nothing happens. then tried adb. used abd reboot bootloader and also adb fastboot recovery. but nothing happens, only shown "waiting for any device". thought adb not working but when I type adb devices.....it shows device serial number and recovery written next to it. I think adb works but I am not able to boot into recovery or bootloader....

earlier I was using cayanogen rom and twrp as recovery... tried to falsh another rom and from that day had this problem. if anyone knows what should do or what's the problem.. I be very thankful... please if you have any idea tell me what to do??
[Asus  Eee Pad Transformer Prime] inbg:
fastboot devices ?
[Nexus 5 Q&A, Help & Troubleshooting] creeve4:
Is the Recent Activity section of Google Play Music supposed to sync between all devices using the same account?

I have noticed that the Recent Activity sections on my phone and PC are separate. I would like them to sync.

The Recent Activity sections on my phone and tablet are in sync, but neither my phone nor my tablet is in sync with my PC.
[Sony Xperia ZL] sirruph:
hello everybody

i had a looooong e-mail battle with Sony support team to include option "disable autocapitalisation" for keyboard settings

can anybody confirm or deny the presence of this checkbox in settings for lollipop? because that is basically the one and only reason for me to upgrade and i'm not sure whether i'm should go with it

thanks in advance

cheers
[Sony Xperia ZL] control freak:
i don't know what exactly are you asking, but i'll try.

In the keyboard, while typing, the first letter is capital. You can tap the capitalisation arrow to make even the first letter small, but you have to do this every time you want the first letter to be in small letters.

hope this helps.
[Sony Xperia ZL] sirruph:
i never experienced a problem with clarity of my speech, but anyway

BEHOLD!

exibit A: some unknown Samsung phone of my coworker

i67 tinypic com/2el6m12.jpg

exibit B: my C6502

i66 tinypic com/k03q14.jpg

(replace spaces with dots)

so, my question: does SONY included this option in the new android version or not

i can install third-party keyboard, like, google's. and the google keyboard do have the "autocapitalization" option. but i really like the appearance and layout of Sony's keyboard, so, i want them to change

if you have a ZL and update it for Android 5.x.x - just go to the keyboard settings. if you see the checkbox for autocorrection - tell me. if you don't see it - tell me anyway, hehe

thank you in advance once again!
[Sony Xperia ZL] control freak:
forgive me my friend for not understanding the first time.

I have updated my Xperia to 5.1.1

as I told you earlier, the keyboard DOES auto capitalise the first letter.(you can change this behaviour on the fly with the Upward arrow below the letter "a" as shown in the screenshots.)

here are these screenshots you requested. see for yourself. if you want any help, I will surely help you :)
[Sony Xperia ZL] sirruph:
OK, auto-capitalization is still turned on by defaut and still unswitchable

guess, i'll stick with KitKat for now

thanks
[LG G Flex] ChiefWilNel:
I replaced my screen with a new screen/frame. it worked fine for a couple of days then the display started looking like this. could it be the video output or the screen? I wonder if I should just give up on the phone.[IMG="phone"]http://i65.tinypic.com/95o7ro.jpg[/IMG]
[LG G Flex] falcon8667:
Your LCD connector may not be properly plugged in, also you have to remember that this is plastic LCD and you may flexed it the wrong way. My suggestion would be removing the frame and making sure that's LCD connector is plugged in the right way and turn the flex on without the frame. Flex cable to LCD also might be pinched. It may sound crazy but I think you did not reassemble it the right way.
[LG G Flex] ChiefWilNel:
it is possible it might not be assembled correctly, I bought it as an assembled unit. since it worked initially maybe the cable came loose in the frame
[LG G Flex] ChiefWilNel:
thanks for your suggestion, I pulled the cable loose from the frame , reseated it and now it works again
[LG G Flex] ChiefWilNel:
what are the antenna wires for, is it wifi or the cell network? i have one that is broken, it was broken when I replaced the screen, but i did get cell service. now that i fixed the screen again, i do not get cell service.
[LG G Flex] falcon8667:
Carefully inspect the wires and back cover. I would suggest to use magnify glass and make sure that the connectors on the end of the wires are not broken . Also expect the back cover .
[LG G Flex] ChiefWilNel:
solder the ends back on, still no go. did factory reset. how could it display new voicemail notifications? I would think it would be hitting the network. could it be that this isnt the sim I activated it on?
[LG G Flex] falcon8667:
If you using SIM from different network then your flex must be first unlocked to access that network. Check your radio signal icon to see if you have a connection. Also check what kind of a network it displays in the settings
[LG G Flex] ChiefWilNel:
nope same network, sim works in my phone, I put the orginal one in the flex and it doesnt receive signal either. oh well to the scrap heap it goes