yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] rbox:
OK. I just asked one other person if Netflix is working for him. If it's not working for him either, I'm gonna add a warning on the post for now. I have 2 ideas on how to fix it. As I was going through the update I noticed some drm stuff had changed and the tz (trustzone) image had changed. Ideally I'd just include the updated tz image, but there is a slight chance of bricking depending on how sneaky Amazon is, so I'll have to investigate that a little before attempting that. The alternative is to try to roll back the drm stuff to what's in the old version and pray the new version of Netflix isn't dependent on any of the new stuff.
[Fire TV Android Development] jmerrilljr2:
No hurry. There's always my ATV3.
[Fire TV Android Development] rbox:
I did come up with a 3rd alternative which is to figure out how they are forcing the update of Netflix, and block that. Hopefully I'll have some time this week to look at some things.
[Fire TV Android Development] Y314K:
Can some one extract the new NetFlix .apk & sideloaded into PreRooted-51.1.3.0_513011820 & see if it even installs/loads/works ??

Also, unless Voice search is part of this NetFlix update or not sure if it was already functioning ?? Isn't it better to just sideload NetFlix from the PlayStore since it's the one that gets the most/quickest updates anyway ?? And get rid of this one ?
[Fire TV Android Development] mastafunk:
Playstore version of netflix doesnt do HD or DD.
[Fire TV Android Development] jarayn:
also its touch screen interface .. so .. terrible idea.
[Fire TV Android Development] Y314K:
Thanks for the clarification... Hope there is a work around to be able to enjoy the new NetFlix app...
[Fire TV Android Development] niphoet:
Is it possible that the Netflix app is detecting root? Has anyone tried using Rootcloak or something? Thanks
[Fire TV Android Development] moqwai.:
Tried Rootcloak, no success
[Fire TV Android Development] niphoet:
Thanks, moqwai. Worth a try.
[Fire TV Android Development] rbox:
I added an updated zip that fixes the Netflix problem. I'd like to hear from people using DNS unblocking if Netflix is working for them.
[Fire TV Android Development] Skater4599:
Nice! I'll have to re-update when I get some time lol.

Quick question, in what you found, any chance of keeping the old netflix app on the new firmware or is it hard-coded in there? I don't mind it, but my family doesn't like the new UI at all.

OH wait, still going to wait till xposed module gets an update to work with this firmware, I hate scrolling through all the options on the stock UI to get to setting etc.
[Fire TV Android Development] rbox:
It seemed like I was able to sideload the old Netflix apk and use it. But it didn't show up in the menu.
[Fire TV Android Development] mjbxx:
Delete the current Netflix App First?

Is it necessary to delete the current Netflix App before going forward with the new iteration through CWM?
[Fire TV Android Development] rbox:
When you run it the first time after updating in cwm it forces an update to the new one.
[Fire TV Android Development] rotor00ter:
I'm downloading the 51.4.0 pre-rooted update now. I use unblock-us DNS settings as I am in Canada. I'll let you know the results once I get a chance to try the new Netflix app on it.
[Fire TV Android Development] Y314K:
Partial solution maybe: http://xdaforums.com/fire-tv/general/easy-to-access-apps-t2921479
[Fire TV Android Development] mjbxx:
That is not an alternative that I would ever consider unless there was no other choice through root. I am running the SPMC Launcher and fully enjoying an optimum XBMC/Kodi experience within the Amber skin at this time.
[Fire TV Android Development] Y314K:
It was a partial solution for the "I hate scrolling through all the options on the stock UI to get to setting etc.". To get to apps. Just an option.
[Fire TV Android Development] rotor00ter:
So I'm having a strange problem. I have tried to push the rom update to my Fire TV via adb commands, adbfire, and also with winscp by ssh. It shows that the file is in the proper folder when I check but then when I reboot into recovery to flash the rom the zip file isn't there at all. Its like recovery isn't accessing the proper folder or something. I tried to put it into downloads or somewhere else but no luck there either. It just doesn't show up in recovery. I have done this before but not since using the jmandawg version 2 drive mounting script so I'm not sure if that has anything to do with it or not? In the SDcard directory that comes up on recovery it sees the 2 mounting scripts, the revert script, and busydrop 1.0 which I also installed. But I can't see any of these on the SDcard directory when I look through it on winSCP SSH. Very strange, any ideas?

So I found those other missing scripts in /mnt/shell/emulated but when I moved the rom to that folder it still doesn't show up.
[Fire TV Android Development] Sus_i:
Yeah, I think it's ok ;) Worked for me fine.

Cache is also read only, must be an interference between to long wires.

Short down the wires. Power down and restart your laptop. Place the script on desktop, plug in the usb stick with the shared folder, do the pv install, set permissions and run the script with sudo.
[Fire TV Android Development] Sus_i:
Ok. Sorry that i couldn't help you. I don't know what causes this read only thing for you. I never had such problems, did five buellers and two montoyas until now, without any hassle.

I tell you what i think, maybe it helps, maybe not.

In the old hardware root thread here on xda, I've read about errors/problems above 5 inches. You can look/search into this thread, there are many hints about this in there. Just for information, my (from exploiteer badly copied selfmade pcb, self soldered) emmc adapter needs wires about 3 inches max... and yes, thats makeable. ;)

You could do a few things if you like, systematically exclude possible error sources...

1. Plug a sdcard in your reader and check if the card gets read write mounted in your ubuntu system, maybe copy a few files onto the card as a test.

2. Check your sdcard reader. You know this thing can read in 1bit mode, but can it write in 1bit mode too??? You could do the DAT1-3 taping with a SDCard and check r/w access in ubuntu.

3. You could try an older ubuntu version. The version I know that it worked fine for me is 16.04.

4. If you think that your problem is software side, you could ask for help on xda or at ubuntu forums, maybe a linux skilled person could help you to track down this issue, running a few diagnostics, check mount, autofs, fstab or whatever, idk. Skilled linux users can remount rw and dd a image to a mmc in notime, without any script at all.

5. Exploiteers have tried a lot of readers, but only recommend one! Maybe it's worth a shot, idk, your decision. I have this reader too.

Besides that, it could be possible that your bricked fireTV has a somekind damaged emmc, but I think thats unlikely. I would rather suspect the sdcard reader/the cable length/ubuntu system setup, in that order.

Last, there are typos (not from you) in the script you posted, therefore I would recommend you the script I've tested/posted... just if you get this read only thing worked out. Wish you good luck. :good:

Edit: I forgot to say, it's normal that some partitions aren't accessible, there are about 18 partitions on the emmc.

Eidt2: You get the "Read-only file system while setting up superblock" message. I remember superblock errors at my first tests (with too long cables). But I think the sdreader is my first suspect for now.
[Fire TV Android Development] snebojsa:
Thank you for your help.

I will not abandon this project till I have something to try and experiment :)

First I will try to short down the wires little bit more and see if it helps. Second, will try Ubuntu version that you have. Will experiment with SD card and reader and see if it can write 1bit mode (just bought this reader for 15 euros.)

I think I used your scripts, what typos do you mean?

If there are 18 volumes in emmc, why I can see only 6?
[Fire TV Android Development] snebojsa:
I have this SD card

Found online that I have to cover pins 1, 2 and last one (from left to right), is that correct?

When I insert SD card prepared like this in reader it can't be mounted at all, so cannot neither read or write.
[Fire TV Android Development] Sus_i:
Ok. Don't rush it, it's sometimes better to leave it alone for a while ;)

I placed my emmc adapter right next to the small black emmc chip, the contacts near the PCB from the fire tv (looking at your picture, the other side 90° degree clockwise). You don't need to tape the wires down, it's good enough if you tape the fireTV PCB, the emmc adapter with the reader and maybe the usb reader cable a little bit.

I mean you should use thisone.

Many of them are in RAW data format, that ubuntu can't read.

Your message "Read-only file system while setting up superblock" prints usually if there are some in/out errors, i.e. faulty usb devices... Therefore I suspect the reader and the wires as suspicious... the ubuntu system just after that.

---------- Post added at 11:43 AM ---------- Previous post was at 11:34 AM ----------

Yeah, thats right. From the side with the square cut outgoing. Don't know, maybe try to use fewer tape, only small tape snippings at the contacts...
[Fire TV Android Development] snebojsa:
Used Ubuntu 16.04, have shortened the wires on about 1.5 inches, nothing, read-only...

Think that is a reader, must buy Transcend TS-RDF5K, right?
[Fire TV Android Development] Sus_i:
Looks good. :good:

As a last try before buying the TS-RDF5K, you could pull out the clk line under the shield. If there is the slightest short to ground, the system flags your emmc as faulty... Be careful, the clk pad is a critical point.

Edit: also take care that the wires don't touch the others, just for precaution. You need to restart the ubuntu system, so ubuntu forgets about faulty flags ;)

Edit2: goal is to avoid (not measurable) cross talking interferences...
[Fire TV Android Development] snebojsa:
Ok, restarted Ubuntu, re-solder everything so wires do not touch anything and do not touching eachother, read-only...

Will order Transcend TS-RDF5K, hope that will be it.
[Fire TV Android Development] Sus_i:
:good:

We'll see, I bet it works out of the box :fingers-crossed:
[Fire TV Android Development] snebojsa:
Actually, it's worse.

I bought Transcend TS-RDF5K in local shop, plugged in but it won't mount anything. After one minute or so there is a message "unable to mount volume...".

Blue led in Transcend blinking and turn off, blue led on emmc adapter goes solid blue but after couple of seconds turn off.

Plugged in old SD reader for checking and it's open volumes like before.

Don't know what is wrong, I checked the wires couple of times with multimeter and it's all ok, they don't touch anything and don't touch eachother.

Transcend reader is USB 3.0, do I need USB 3.0 on laptop to make it work? Have 2.0 only.
[Fire TV Android Development] Sus_i:
Ouch. Bad luck.

I hope your white cable is a long thin usb cable from china, would explain that error.

Please test another usb cable, probably a short usb3 (better quality) or try to use an powered usb hub between your laptop and the sdreader, with short/good cables.

Maybe test another port of your laptop too. The blue ones are better.
[Fire TV Android Development] snebojsa:
Yes, cable is thin and long (1.8 meters). It's Hama, made in China.

I made some gymnastics and succeed to plug Transcend directly to USB port, but it's the same.

Don't have blue USB 3.0 on laptop, will try on desktop but don't have USB 3.0 extension cable or USB hub...
[Fire TV Android Development] Sus_i:
OK. Strange thing.

Your direct connection to a laptop usb port eliminates a possible faulty cable.

Could be that the port itself is worn out or doesn't provide enough current to supply the reader. USB3 ports have usually a higher current as USB2 ports, it's better to choose the blue one.

But an USB Hub with ext. power supply would be best, i.e. max. current at all ports.

If you test it on a desktop, take the blue ports.

Can you measure the voltage of the fireTV power brick in operation? Or can you exchange it with another one, for a test?

I'm curious if that ends well. Hopefully it isn't the emmc itself (or the soldering of the emmc). :confused:
[Fire TV Android Development] snebojsa:
I really don't know what else to try..

Fire TV voltage is about 6v.

Tried with desktop PC, (now my back hurts because I was kneeling under the table :) ) blue port on the back, plugged directly without any cables, won't mount anything.

Tried with powered USB hub and nothing, argh!

---------- Post added at 07:44 PM ---------- Previous post was at 06:59 PM ----------

I de-soldered everything, bridged CLK and powered up, nothing changed, got white Amazon logo for a minute and then shutdown. Wanted to check if messed up even more but not.

Will try tomorrow from scratch, maybe it will help.
[Fire TV Android Development] Sus_i:
Thats ok.

Hmm, don't know. I think you have done allmost everything I could think off. Better leave it alone for a while.

Could be that the emmc adapter from exploiteers or your new reader is faulty too, but thats very very unlikely, probably extremely unlikely ;)

If you see this as a kind of hobby and if you like to tinker with this a little bit more, you can try to get somewere a second bueller fireTV for cheap, in a used but functional condition. Then you can see if you can root that box with your given hardware. It's the same procedure and if all goes right, your first box has probably a bad emmc on the pcb. That is maybe fixable, since the chip is readable in one of your readers, it maybe needs only a reflow with hotair and flux, don't know.
[Fire TV Android Development] snebojsa:
Yes, it's a hobby for me and ability to help friends :) I'm the only one in my surroundings that know a little bit of electronics, computers, soldering, etc.

You are probably wright that I should leave it for a while. I will try it another time from scratch and see how it goes. It's not a rocket science, got hardware and have to solder 4 wires. If it won't work than it's probably the hardware fault, and it will go in the box with other broken Android boxes :)

But it's bugging me, working halfway, can read but won't write, I'm always thinking that I'm not see something obvious...
[Fire TV Android Development] Sus_i:
Fore sure there are a lot of options to check memory faults with ubuntu, i.e. diagnosis, but I don't know details how to do that. :confused:

If diagnosis approves a bad emmc, you could do a backup of all partitions included the raw data ones and replace the entire emmc chip with a similar one from china, then 'dd' data back to it. ;)

Easiest method to do further checks, is to get another bueller. You see the difference, get a second chance to test your hardware. You could do it with a first gen fire Stick too, called montoya, but soldering is much harder (much smaller components on the stick + you need to solder on both sides of the pcb).
[Fire TV Android Development] snebojsa:
Probably there is but I don't know Linux. This is a second time that I boot Linux, first time I was trying (and succeeded) to make bootable SD card for Amlogic Android box.

For replacing emmc chip I don't have skills so that is not an option for me.

If some very cheap bueller show up will buy and see what happens. :)

So, checked the wires before soldering again, length is about 1.5 inches so that is ok. Soldered carefully again and test connection with multimeter, all ok.

Connect with Transcend and won't mount anything.

Connect with previous card reader and mount ok.

Script is the same as before but ends a little bit different:

DD: writing to ' /dev/disk/by-partlabel/system' : Operation not permitted

On post #1373 you said "also change the path to the locked bootloader, boot.img". I didn't done that, where in the script is the path for boot.img? I changed the path for SHARED and SDAT2IMG, that's ok.
[Fire TV Android Development] Sus_i:
In the script I copy/pasted you, I picked the right bootloader for you. If you want to look at it again, open the shared folder with the prerooted rom, you see two boot images, in the script is a line with a path that points to one of the two img files.

Operation not permitted means that you don't have the rights to do that, i.e. you forgot to run the script with sudo and/or you doesn't give the script the right permission (sudo chmod u+x filename.sh) before running it.
[Fire TV Android Development] snebojsa:
No, I run script with sudo, script name is flash.sh:

sudo ./flash.sh

I executed this too:

sudo chmod u+x flash.sh
[Fire TV Android Development] Sus_i:
Then you need to umount that partition before 'dd' (and you didn't use the script that I've linked a few posts ago) or (if you used the linked script) it 's an additional sign for a faulty emmc.
[Fire TV Android Development] snebojsa:
Yes, I'm using the script you linked.

I think we done everything we can. I asked for help in this thread but last activity was about a year ago, will see if someone will reply.

If it's hardware fault, maybe I can give it to my friend who have mobile repair shop to try to reflow emmc chip.
[Fire TV Android Development] Sus_i:
Yeah, thats right. Only thing left is to test your hardware (sdreaders + emmc adapter) with a second (not bricked) box. ;)

I would wait with a reflow until that last test is done.

Edit: You see, on the emmc adapter is a small chip, a kind of signal level converter that changes the dat0 level in relation to the given voltage of the emmc chip (1,8v), normal SD has about 3,3v so that needs to adjusted/converted. An error on that side could be possible. Only way to know it, is a test with a (as working known) box or a second emmc adapter.

You could do tests on other devices with emmc chips too, if you know where to solder the wires, i.e. the dat0, clk, cmd... is known, like for the nintendo switch emmc board.

Edit2: Of course, you know your box is a brick, so it's very unlikely that the emmc adapter is faulty. Culprit is your box, I think up to 99,95% ;)
[Fire TV Android Development] snebojsa:
Ok, thanks.

Would like to try with another aftv but have to wait until find it. Looked on eBay and found one that cost about 25 dollars but unfortunately not shipping in Serbia. I would even try with aftv stick regardless it's harder to solder (bidding starts with 5 dollars on eBay) but again, not shipping in Serbia.

So, have to look and wait :)
[Fire TV Android Development] Sus_i:
Yeah, do that and you get a box for about 10 bucks ;)

You can take look into the procedere for the montoya stick at exploiteers.
[Fire TV Android Development] snebojsa:
I just tried something.

Taped DAT1-2-3 on SD card that I have, put it in Transcend but Ubuntu won't mount it.

Boot up Windows and SD card was normally accessible, can read/write.

Hook up AFTV in Windows and got about 20 volumes, unreadable of course but was there.

Boot to Ubuntu again but all the same, taped card is not accessible.

Can the Ubuntu be the problem, version is suggested, ubuntu-16.04.1-desktop-amd64.
[Fire TV Android Development] Sus_i:
Thats strange. :confused:

Maybe, idk. You could test any other linux, you may try debian...
[Fire TV Android Development] snebojsa:
Tried with Debian, it's the same, when insert reader with taped card absolutely nothing happened.

Now I'm in Windows, can normally access files on card, delete, copy/paste on card, everything.

Don't know what to think...
[Fire TV Android Development] Sus_i:
Hmm, you could think that your new sdreader is faulty (or a new hardware revision?). :confused:

At least, that sd card should be read/writeable with linux, as you know that the card is ok.

Have you tried to read/write the card in ubuntu without the taped contacts?

You could open a terminal and do a "mount -l" and "dmesg" with and without taped contacts, look for errors & differences.
[Fire TV Android Development] LocoMexican:
I'm back. I have another 1st gen. aftv which is in the same condition as my last except this one has never been rooted, so the boot loader is still locked (otherwise it is bricked like my first device). Can I run the "flash.sh" script on this new unit if I change the script to show "unlocked = no" instead of "unlocked = yes" since this device has a locked boot loader???? Also, can I use the same information I got before on this new device; i.e. just go directly to the "flash.sh" command? Thanks for your help.

---------- Post added at 03:07 AM ---------- Previous post was at 02:19 AM ----------

Sorry, I'm referencing the files you attached in post #1330.
[Fire TV Android Development] Sus_i:
good luck :good:

You can use that script, but you have to edit one line. The yes/no switch does nothing. It's that line that needs your attention:

dd if=$ZIP/boot.img | pv -s 6627328 | dd of=$DEVIR/boot

You can choose between boot.img and boot_unlocked.img. Of course, if you have a locked box, use boot.img, i.e. edit the script from post #1330 to that.

Yes, if the shared folder and it's contexts is the same yet as before, you can just go to the flashing script.

There is a new update out, 5.2.7.1. You can edit the build.prop file (to a custom build number) to prevent the update, I think I telled you weeks ago. If you want you can edit the file with the emmc adapter before disconnecting the wires, you find that file on system partition.
[Fire TV Android Development] snebojsa:
SD card is absolutely ok in Ubuntu without taped contacts.

Can read/write/delete/copy/paste/open/format, everything is good.

With taped contacts absolutely nothing happened, like I didn't insert anything.

Tried with both Transcend reader and build in card reader in laptop, it's the same.

Boot to Windows with taped contacts and card is fully accessible.
[Fire TV Android Development] Sus_i:
There should be NO operational difference.

I never had any problems like that. Same for [MENTION=8133270]LocoMexican[/MENTION].

You may ask for support at ubuntu forums. Tell them that you want achieve 1bit mode read/write access and ask why the heck it won't work (for you) with ubuntu.
[Fire TV Android Development] snebojsa:
Ok, will try. Thanks.
[Fire TV Android Development] LocoMexican:
Patience is a virtue. I don't have too much at times. Regardless, I flashed the device with "flash.sh" before I asked the question last night. I simply changed the "yes" to "no" on the "locked" switch since I knew the bootloader was locked, but that's the only edit I made in the script. Afterward, It would boot to recovery, but not to the system. Just white amazon logo on and off. This morning, I made the edit you suggested to the "flash.sh" script and reflashed the device. I can get into twrp recovery, but when I reboot system, it stays in a the same condition as last night. I tried to do a factory default wipe in twrp, but it fails to mount cache and data and the format fails. The only good news is I can still boot into twrp. Bad new is I'm lost as to how I might try to get it to mount the partitions. Any help is appreciated. Thanks.
[Fire TV Android Development] Sus_i:
Do you used this line in the script?

dd if=$ZIP/boot.img | pv -s 6627328 | dd of=$DEVIR/boot

In TWRP you see in the left row the button "Mount" - there you can mount the partitions you like. If data and cache is mounted, try to remount (remove hook, set hook).

Go back and click the Wipe + Advanced Wipe button. Select: data, cache, dalvik, and if you like Internal Storage, and do the wipe. Press reboot...

Edit:

If you want to connect the emmc adapter again, you can add this to your script (behind clearing cache):

echo -n "Clearing data..."
umount $DEVDIR/userdata
mkfs.ext4 $DEVDIR/userdata
echo "Done."