yashsingh1/xdaforums huggingface dataset:
[LG V10 Q&A, Help & Troubleshooting] Hunais:
Any luck on rooting the LG V10 H961N dual sim verison.
[LG V10 Q&A, Help & Troubleshooting] shchiam1978:
Just got the phone today. Seems like no info yet for this particular model. Feels so weird using the unrooted phone.
[LG V10 Q&A, Help & Troubleshooting] rowihel2012:
i hate to use unrooted phone

i hust wanna buy lg v10

but dont know what model to buy and has root
[LG V10 Q&A, Help & Troubleshooting] shchiam1978:
USA model has root. Saw it in the YouTube. Korea and Hong Kong not yet
[LG V10 Q&A, Help & Troubleshooting] rowihel2012:
so usa models works with gsm freq?
[LG V10 Q&A, Help & Troubleshooting] shchiam1978:
Not sure on the frequencies. Sorry
[LG V10 Q&A, Help & Troubleshooting] hokage0002:
Still no root of the H961n?
[LG V10 Q&A, Help & Troubleshooting] warlet:
Hi there..does anyone got latest sofware update?
[Shield Android TV Q&A, Help & Troubleshooting] slammertime:
Turning off location services seems to stop this too

I'm 100% that no ethernet stops the rebooting (got a few hours of testing and no crashes). Tried turning off location services after I saw the logs of the error, and I've had about 30 min with no crashes, so that's obviously a much more preferred way to address this issue until nvidia fixes the bug
[Shield Android TV Q&A, Help & Troubleshooting] Syfer198754354:
well interesting to know about this issue.
[Shield Android TV Q&A, Help & Troubleshooting] blyndfyre:
Has having locations services turned off solved the random restarts for you inevitably?
[Shield Android TV Q&A, Help & Troubleshooting] slammertime:
Yes, it seems so
[Shield Android TV Q&A, Help & Troubleshooting] grivad:
Sorry for resurrecting an old thread, but I'm still having this issue.

Tried disabling location, changing languages, every other suggestion here and elsewhere online.. still getting reboots ~3-5 mins after the system starts, and random lockups. Only started happening post 2.1. The device is basically unusable at this point.

I'm just about to factory wipe/reinstall. Is there any other solution?
[Shield Android TV Q&A, Help & Troubleshooting] peppy6582:
Same

I am having the same issue. Talked to support, and they told me to unpair, and reset my devices that were attached to it, and unplug the hdmi and power, and still no dice.
[Shield Android TV Q&A, Help & Troubleshooting] grivad:
I got sick of it, wiped the device, and did a fresh install of 2.1 (IIRC, whatever factory image was available a few weeks back) and applied the OTA once prompted. Zero issues since. It took some time installing and configuring everything again, but having a completely stable device made it worth it. It was unusable before, as it'd reboot every few minutes no matter what it was doing.

It looks like they have the 3.0 image up now, if you're thinking of reinstalling as well.

https://developer.nvidia.com/shield-open-source
[Shield Android TV Q&A, Help & Troubleshooting] peppy6582:
Yeah, I actually did that, with a fastboot -w after the system.img part, just to make sure.
[Shield Android TV Q&A, Help & Troubleshooting] Avanox:
hey guys, do you still have the problem with the random reboot?

I have the same problem with the 500gb version but I didn't root this device or whatever, it isn't even my intention to root it.

Any idea what it is?? Nvidia want to send me a new one (or refurbished item) but I have like the idea that it will not be solved if I get a new one.

I read to much people with the same problems, even on 2 links I read from someone who got a new one and the problem was still there :s

I'm a little scared to send it back , because I fear it will not be solved.

Any idea guys???
[8125, K-JAM, P4300, MDA Vario General] hellomota:
I installed some sh!tty player on on my precious wizard, then removed it. Now I can't open my media files with wmplayer. I mean I can open them from the inside of the player, but not when I browse them from file explorer. I looked for reg edit command to change the program media files open with, but now luck? Anybody knows how to do this?

Also I cannot seem to get my image vieweing thing to do a slideshow.

Thanks -Greg.
[8125, K-JAM, P4300, MDA Vario General] xeno1:
Just choose the file you want to play in file explorer and then click menu-->open path-->new path and direct it to WMP in the windows folder. After that, all of your files of the same type should open with WMP again, atleast that's how you fixed it in WM2003 anyway. I haven't had to try it in WM5 or WM6 to know for sure.

I don't know about the slideshow thing though, I've never used that before.
[8125, K-JAM, P4300, MDA Vario General] hotdog53:
The crappy player you installed was associated with (wav) files that are for windows media player. Try re-installing that same player, look at its file associations, uncheck (wav) may have kept settings after removal, and then remove the player again if you still don't want it. soft re-set, check files in file explorer, and if all the above actuated, the files should have the wmp icon. Word of advice from experience....always remove settings from programs that were installed before you remove that program. As far as slide show, are you meaning where songs play in sequence (queued up)? By the way, what was the crappy player? I've removed a few of them myself..
[8125, K-JAM, P4300, MDA Vario General] hellomota:
hey guys thanks much for replies. Xeno I couldn't get the path thing to work. If I type in \windows\wmplayer.exe it just opens player in library mode, doesn't change the way it opens either. The player was pocket dvix player. I was looking for something that will play AVI dvix and xvid files. Now I installed something called TCPMP pocket pc player and it works very very well.
[8125, K-JAM, P4300, MDA Vario General] xeno1:
TCPMP is way better than WMP anyway. Sorry the open path didn't work, but like I said, I wasn't sure if it still worked that way or not in WM5 and 6. Atleast now you have a better media player. TCPMP is the only player I ever use.
[Xperia Z3 Q&A, Help & Troubleshooting] kubaz9991:
Hi,

I got problem with my Xperia Z3. Top speaker is very quiet when I call or listen to music for example on YouTube. Is it software or my speaker is broken?

Android version is 5.1.1.

Wysłane z mojego D6603 przy użyciu Tapatalka
[Xperia Z3 Q&A, Help & Troubleshooting] arturviana:
i have the same problem. Z3 d6633 (brazil)

ringtone is very low. I think it's the version of lolipop.
[Xperia Z3 Q&A, Help & Troubleshooting] kubaz9991:
Do you know when will they update it to 6.0?

Wysłane z mojego D6603 przy użyciu Tapatalka
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Matthew2D:
I was trying to root my Kindle Fire ($50 version). I used this file http://rootjunkysdl.com/getdownload.php?file=Amazon Fire 5th gen/root_fire.zip. I followed the instructions inside the file. I ran root.bat and followed the instructions inside there. The installation failed. I dont have a picture of the log in the cmd sorry.

The screen says the following:

USB Transferring...
USB Transmission OK Time:174ms Vel: 25576KB/s

I tried holding the shut down button but it wont turn off. What do I do?

Thanks.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Matthew2D:
Actually nevermind. I was able to turn it off an hour later.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] nyln:
There is no root available for the Fire HD models, the supertool is for the 7" model.

If you want to delete the firelauncher:

http://xdaforums.com/hd8-hd10/general/tut-remove-default-launcher-amazon-fire-t3288192
[Google Chromecast] ddggttff3:
What is it?

This is my final gift to the Chromecast community, called Flashcast-AutoRoot. This is a special recovery image for the Chomecast v1 device that will allow it to take official Google OTA's, and then root them during the flashing process. This means you get to keep root, while staying up to date with Google images!

Features:

Auto roots any official Google OTA sent to your device

Supports automatic Recovery Image updates

Spawns a root telnet server

Supports a custom startup script

DHCP and Custom DNS

Q and A:

Q: How do I setup a custom startup script?

A: Just write your script to a file at /data/user_boot_script.sh, and set the executable bit for the file. Once done, it will be loaded on next boot.

Q: How do I setup custom DNS servers?

A: Put the IP addresses of the DNS servers in a file at /data/dns.conf, one per line. On next boot these will be used for DNS requests. Note if you are coming from EurekaROM, it will already have your old settings in place. :)

Q: How do I setup the EurekaROM Web Panel?

A: By default this ROM has no Web Panel, but this can be added by bootstrapping onto the custom startup script, but I will leave this up to you. ;)

Q: Can Google unroot my device in the future?

A: Technically yes, but they would have a hard time doing so. To get technical, the bootloader partition can't be updated from the stock OS due to the kernel hard-setting it to "ro". While the recovery image can be flashed from the OS, the root process replaces the included recovery image with it's self to prevent any update. The recovery is also unable to update the bootloader partition, so you should always be able to re-flash using a OTG cable. With that said, I have also put in an update method so I can push updates to the recovery image if needed, but at this time I have no plans on doing so unless required,

so use this image at your own risk

.

Installation:

To install this, all you need to do is SSH/Telnet into an already rooted Chromecast, and run the following commands:

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

Note:

If this is ran on a different ROM than Eureka-ROM there may be an error when ran, but rest assured the flashing process will still work. :)

GPL/Source:

https://github.com/team-eureka/flashcast-flasher/tree/newmode-alpha
[Google Chromecast] extrem0:
Thanks for all your work for our chromecasts!

Confirm this is working like a charm!
[Google Chromecast] crazy24hraday:
Thank you once again for all the great work you have put in on this device.
[Google Chromecast] MildlyRegularPerson:
[MENTION=2212097]ddggttff3[/MENTION] Is ssh supposed to work after installing? I'm only able to connect to the chromecast via telnet.
[Google Chromecast] extrem0:
telnet only (port 23)
[Google Chromecast] Asphyx:
For those with windows 10...

Telnet is disabled by default.

Run a command prompt with administrator privs (Shift RClick and run as Administrator) and type in the following to enable it

dism /online /Enable-Feature /FeatureName:TelnetClient

Installing now and all seems to be going well as it is currently downloading the Google OTA.

Thanks very much [MENTION=2212097]ddggttff3[/MENTION] for this!

Ok Install is done....Had only one error reported about verification and writing to block 8 which was replaced by recovery.

Unit rebooted and is working fine.

Only strangeness was it took a minute and a reboot for the unit to register with The Google Cast (DIAL LIST) but after a reboot it showed up and connected which I believe may be a local unit thing that happens with my unit from time to time not anything to do with this project!

GREAT JOB!
[Google Chromecast] Johan1976:
Yup. Worked as expected. Now Im prepared for new update who hope fully also bring multiroom support to standard chromecast as well (keep my fingers crossed)

Skickat från min GT-I9505 via Tapatalk
[Google Chromecast] badm0j0:
huge thanks ddggttff3, your the man.
[Google Chromecast] Prack:
Subscribed to the thread. Thank you again for everything you did for the chromecast :)
[Google Chromecast] MildlyRegularPerson:
[MENTION=2212097]ddggttff3[/MENTION] , could you please make a tutorial on how to install the web panel?

Sorry I'm new at this.
[Google Chromecast] Srandista:
[MENTION=2212097]ddggttff3[/MENTION], thank you so much for this!

I try this few times on my 2nd CC. First time from Eureka ROM, then from stock rooted.

I receive two errors, one during the first flash (regarding recovery), other during flashing from rooted stock. I guest, they all right, but just to be sure:

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

/cache/install.sh: line 67: EurekaSettings: not found
expr: syntax error

Also have a two questions:

What's the difference between recovery used in previous Eureka ROM and the one used in this rooted stock?

And once new OTA for stock CC arrives, I should run this command manually again, to receive it, right?
[Google Chromecast] Asphyx:
I got the first error the same as you but it did not seem to have any affect since the unit completed the rest of the install and is working just fine.

I dod not get the second error you mentioned though.
[Google Chromecast] kefallo:
Should we run this every time we want to update Chromecast, or is it automatically updating itself when new firmware released?
[Google Chromecast] ddggttff3:
The errors you saw are normal, and are nothing to worry about. As for the questions, the recovery on this has some custom scripts (can be seen in the repo) that do the entire process, so once google pushes an update to your device using the stock update binary, this special recovery will automatically root it during installation.

Completely automatic, so there is nothing you need to do. :)
[Google Chromecast] ImCoKeMaN:
Awesome work, I'm not sure if I want to update my device with this yet since we have the current Eureka rom, but if that was the last this is an excellent way to allow future versions and keep root, thanks for your work!
[Google Chromecast] ghowse:
Hi,

Just found this thread and about to SSH in do the update. Unfortunately I've lost the user/pass.

Help please.

Cheers

Geoff

Edit>> took a guess and was correct. User: root, no need to enter password.

Updating now .....
[Google Chromecast] MildlyRegularPerson:
Try reflashing Eureka rom

Enviado desde mi GT-I9506 mediante Tapatalk
[Google Chromecast] ghowse:
Thanks, I was able to do the update via SSH.

Like an earlier poster, I don't know how to boot the web interface. I'll be doing some research, but hopefully someone will give some hints.

Cheers

Geoff

Edit>> I'm trying to learn about using sed to edit the script file(s). Am I on the right track?
[Google Chromecast] ghowse:
Sed is available on the CC but looks a bit dangerous. I don't want to brick my device. I'm still looking for another editor. There is no nano, pico, vi etc that I can see.

Still trying .....
[Google Chromecast] ImCoKeMaN:
I ran this on my eureka rom Chromecast last night and the script seemed successful and then said rebooting, I saw flashcast on my tv but now it just shows white "chromecast..." letters on a black screen. I had it plugged into power on the TV's usb port during the process is there a chance it needed more power during the flash and got corrupt? Any ideas to try to revive it?
[Google Chromecast] mcpdigital:
You are correct. The image came from the Desktop app that is not showing the correct version. Home APP show the same as yours.

MCP
[Google Chromecast] ZaneChua:
ah. Maybe the desktop app and Google Home app have different ways of reading the firmware version. I don't really have the time to go fully take a look at both boot.img's but i did manage to extract both and do a diff between the two folders.

So if anyone wants to take a look.

https://gist.github.com/zanechua/f6f1478e75c34e02e9b8d88f41e081f7
[Google Chromecast] alx1880:
I got the same problem of chromecast unable to boot and showing a black screen with the word Chromecast... written at the bottom. I decided I no longer need root, how do i unroot my chromecast?
[Google Chromecast] zando2712:
Thanks ZaneChua for a working solution and mcpdigital for hosting.

My rooted chromecast can now completely boot up.

Only thing, I don't think the web interface works now.
[Google Chromecast] Asphyx:
This worked like a charm. It may not last past the next OTA but it buys us some time to figure out a permanent fix!

Without knowing exactly what is in those files it's hard to say what is breaking...

But if I had to take a wild guess it would be either the DMTABLE or they changed the partition structure...

I'm leaning towards the change of Part structure!

Looking at the Autoroot source there is code to init-partitions.

https://github.com/team-eureka/flas...-alpha/bundled-mods/init-partitions/imager.sh

Note the commented line at the top! LOL

I wonder if they changed the partition structure in the new boot img and flashcast can't find the files it need to boot.
[Google Chromecast] ForbEx:
any chance to repair it without teensy (hubcap)??

Will it repair itself when new update be released? Sometimes im getting wait until your chromecast will be updated eureka screen...
[Google Chromecast] ZaneChua:
They did. They changed how the system partition is mounted in the init.rc script.

?? Why do you need a teensy? You don't have to use the hubcap version. You can just flash the eureka rom with flashcast and you would only need an OTG cable.
[Google Chromecast] Mad07:
This worked like a charm.

You can insert the commands also via telnet session.

After "reboot recovery" you need a little bit time: Smoke 2 cigarettes and all things running well.

THX a lot for your fast solution!

Cast-Firmwareversion: 1.23.84839
[Google Chromecast] ForbEx:
DELETED will try something
[Google Chromecast] Asphyx:
You don't need Teensy at all...Just the image from Hubcap. Use the OTG cable and make sure you get a white flashing LED (If red just unplug and replug it into the CCast) and when Eureka is loaded and rebooted use the Autoroot commands in Telnet posted above.

So the question is I guess....can we change what is in the Autoroot Git to work with the new mounting needed?

Or can we only fix this by hacking the init.rc itself?
[Google Chromecast] ForbEx:
need to use boot.img with win32disk sure?

I cant get it working.. made usb with boot img with wind32disk and then plugged flash into otg, then chromecast to tv turned on with usb and on screen is only chromecast (white), when holding reset for 30 sec only red flash... :(
[Google Chromecast] Mad07:
No 2 is back to life ;)

[MENTION=5104317]ForbEx[/MENTION]

you need only the USB Stick with the Eureka-Image (which you've used for rooting). Plug it into the OTG cable, hold the button and connect the power. If the red LED is lighting, wait a second, release the button and after flashing is finish (you're now on an old Eureka Version) wait for the update of the last Eureka Version.

After that, open a Telnet Session and insert one after the other command into the shell. If something is happen, start from the first command.
[Google Chromecast] ForbEx:
im doing on it acutally i am on 17977 waiting to update itself to 444***
[Google Chromecast] eKeith:
Unfortunately after entering the very first command within a telnet session, it returns the following error:

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

wget: can't open '/data/temp/root-recovery.img': No such file or directory"

Any ideas? Note that I am behind a VPN as I am outside of the US.

Thanks.
[Google Chromecast] Mad07:
Wrong comand?

insert following as first command (without " ") as one line

"

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

"

For sure, copy the commandline from a few posts above and paste them into the terminal, one by one.

Keep care, there a few very long commands over more as 1line.

The first 3 commands are starting all with "busybox........."

The fourth with "flash_image...." and the last with "reboot...."
[Google Chromecast] ForbEx:
you must create directory with this command

mkdir /data/temp/

then run commands... had the same problem, it solved..
[Google Chromecast] eKeith:
Thanks for your reply. But I'm not using the quotes. I just added them in my post to specify the command used... my bad.
[Google Chromecast] ForbEx:
I replied you fix command... look up
[Google Chromecast] eKeith:
Brilliant! Download in progress...
[Google Chromecast] ForbEx:
Im done right now. CR is working like a charm. Thanks for help, I hope I helped many users with can't open problem...(they will not ask)
[Google Chromecast] eKeith:
Successfully updated 1 of 2 rooted Chromecasts to 1.23.84839.

Thank you all!

On to No. 2 now...

PS FYI

My 3rd Chromecast is pure stock...
[Google Chromecast] ZaneChua:
Not much point hacking the init.rc, it'll just be replaced with the next version and it'll break again. Probably will have to fix it at the autoroot level but I gotta understand what's going on first and I may not even be able to do it.
[Google Chromecast] Asphyx:
Well when I meant hack I was thinking pf autoroot writing a compatible Init.rc to the update before installing...That seems like it might be impossible...

I agree it is probably best to be done by changing Autoroot to work with the new init method.

And no one ever thought it would be easy to do that! LOL
[Google Chromecast] extrem0:
Would you have another mirror? Yours seems to be broken now.
[Google Chromecast] mcpdigital:
I will put it back on the server now, so try to download ASAP please.

MCP
[Google Chromecast] fortis91:
I'm missing the flash_erase command, is that available somewhere?
[Google Chromecast] Crussader:
I think you mean the flash_image...

I had the same issue but then I opted for the install script from [MENTION=2690092]ZaneChua[/MENTION] but then it failed to update the chromecast... but it did download the required tools ( flash_image ).

Then I executed the commands by hand... and voila! it's alive :)
[Google Chromecast] fortis91:
flash_image....Thank you.

No internet on the Chromecast so I have to put the files on a webserver and use wget. I'll try to grab the file from the script.

Thanks.
[Google Chromecast] funkypc:
I didn't want to pull out my OTG cable.

I had the same problems (flashing white light) and had SSH access to my chrome cast(user root - pass letmein ) so I modified the commands and did the following:

busybox wget http://pdl.team-eureka.com/recovery/releases/autoroot-recovery-r02.img -O /tmp/root-recovery.img
busybox wget http://mcpdigital.com/android/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip -O /tmp/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip
#NOTE - you will have to modify the following line - check which folder has been mounted and has ota.zip in it - it will be tmp.??????
busybox cp /tmp/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip /tmp/tmp.PrADEY/ota.zip
#Flash Recovery
dd if="/tmp/root-recovery.img" of=/dev/mtdblock6

I think I maintained root doing this but I lost telnet access so don't hold me responsible for any issues.

My Chromecast is now working.
[Google Chromecast] ZaneChua:
Flashing White Light = Chromecast is flashing a firmware.

You have to be in Eureka Rom so it has the flash_image command.
[Google Chromecast] Rooksx:
The latest firmware update seems to be causing problems. The Chromecast is now stuck on the black screen which just says "Chromecast..." My phone can't detect it either.
[Google Chromecast] Mad07:
Please read the last ~15 posts in the thread.... we have had all the same issue
[Google Chromecast] bhiga:
Might be good to put it on AndroidFileHost or somewhere that won't impact your hosting plan.

If you have don't have an AFH account I can put it up on mine if you're okay with that.

Users would still need to put it on their own web server for the wget pull to work, but that could be a local server.
[Google Chromecast] Asphyx:
I may have a theory on what has happened....

https://github.com/tchebb/chromecast-tools

If I read his read.me correctly, The Boot Image would have it's header changed to trick the bootloader into thinking it is a signed image.

I am guessing either mkbootimg is choking on the new boot.img or the header has changed so that the image is no longer useful and is corrupted after cc-mangle-bootimg has done it's deed.
[Google Chromecast] oppy:
EDIT: didn't notice bhiga's post. ;) If someone could host it more permanently that'd be great!