Develop Bugs

Fire doesn't connect to Wifi anymore

It was fine for a couple of months but now my Kindle Fire cannot connect to wifi. Tried for home and office spots - open and password protected security options.
Nothing helps. Tried: factory reset for tablet and router, off\on both and PC, rooting, installing CM9, installing modified 6.3.1.
What I'm going to try: use static IP (but even if it would work for home, I still want to be able to connect to other spots), use some official rom older than 6.3.1 (I'm not sure but maybe the issue appeared after 6.3.1 was flashed automatically by amazon).
Amazon support proposed to replace my kindle, but I'm not in US so it's not a trivial thing and I'm still trying to resolve it by myself.
I appreciate any advice what else worth a try.
Thanks!

really sounds like a hardware issue
---------- Post added at 01:32 AM ---------- Previous post was at 01:04 AM ----------
with some of the roms adhoc connections have been a problem I have had several roms not want to connect to my home network hashcodes jellybean and jandycane but they would connect to my phones wifi and other hotspots. No connection anywhere? that screams hardware IMO

The wifi chipset is a jorjin WG7310 there is a micro coax that travels from it up underneath of some shielding to a wifi antena located underneath of the speakers these are the components I would look at for good connections and such

Thepooch said:
The wifi chipset is a jorjin WG7310 there is a micro coax that travels from it up underneath of some shielding to a wifi antena located underneath of the speakers these are the components I would look at for good connections and such
Click to expand...
Click to collapse
thanks, but I don;t want to lose warranty while there are still possibilities of replacement by amazon or by local retailer. And wifi kinda works - it scans and find all available spots successfully, can't connect though.

drink said:
thanks, but I don;t want to lose warranty while there are still possibilities of replacement by amazon or by local retailer. And wifi kinda works - it scans and find all available spots successfully, can't connect though.
Click to expand...
Click to collapse
Does it say connecting or acquiring or authenticating then go to saved then right back to the beginning?

Thepooch said:
Does it say connecting or acquiring or authenticating then go to saved then right back to the beginning?
Click to expand...
Click to collapse
It says Attempting, wifi sign is flashing in the tray a few times anf after a while the Error in Connection message appears: "Unable to connect to .... Please try again."
the conenction is not saved.

Maybe try this is is on hashcodes cm9 post
IF FOR SOME REASON WIFI DOESN'T WORK ON THE FIRST BOOTUP DO THE FOLLOWING: Enter Terminal Emulator Type: su Type: fix-mac.sh Exit Terminal Emulator Reboot
Also a a full wipe a fresh flash decline Google's offer to restore your account or keep your device backed up try this rom http://forum.xda-developers.com/showthread.php?t=1778010 factory reset wipe cache wipe dalvik wipe system wipe flash from and gapps reboot I'm just curious if you don't mind testing
Disregard if your on stock without root...
Getting amazon to replace it would probably be less of a hassle...

nothing helps, ordered replacement at amazon.
another question - would amazon charge me for the new kindle if they found out that the one I returned them is rooted?
if yes - is it possible to unroot and flash default rom if I'm on CM10 now?
thanks )

Observe instructions carefully when you attempt to return to stock wipe everything except your SD card before flashing update.zip or it will brick After you have flashed update,zip and have made it back to the stock os then do a factory reset and they will be none the wiser...

Thepooch said:
Observe instructions carefully when you attempt to return to stock wipe everything except your SD card before flashing update.zip or it will brick After you have flashed update,zip and have made it back to the stock os then do a factory reset and they will be none the wiser...
Click to expand...
Click to collapse
thanks.
btw, I tried CM10 you proposed. looks good )) but no luck with wifi

I'm stuck. windows determines kindle like "Am disk drive" drive so I can't use KFU. I can't get into recovery mode also.

Uninstall your drivers but don't delete them from your system unplug rerun drivers from kfu then plug your kindle in...see what windows install for you
Edit: stuck because you flashed stock?

Recover / Hard Reset

Anyone have the steps to take to preform a hard reset of fix a non booting device?
I am stuck on the amazon Fire TV part where the boot animation is doing nothing. Can't get past this screen and have been stuck for the last 10 minutes.

jamesrascal said:
Anyone have the steps to take to preform a hard reset of fix a non booting device?
I am stuck on the amazon Fire TV part where the boot animation is doing nothing. Can't get past this screen and have been stuck for the last 10 minutes.
Click to expand...
Click to collapse
End Result. If you brick you box Amazon has no troubleshooting steps outside of rebooting the box. Once you get past that step and your still having an issue Amazon will issue you a replacement FireTV.
You will need to call Amazon as the Live chat is useless: 866-216-1072 Press 0 and ask to be transferred to the Fire TV department.

jamesrascal said:
Anyone have the steps to take to preform a hard reset of fix a non booting device?
I am stuck on the amazon Fire TV part where the boot animation is doing nothing. Can't get past this screen and have been stuck for the last 10 minutes.
Click to expand...
Click to collapse
Oh, boy. That is unfortunate. What did you do that lead to bricking your box?

I am in the same situation with one of my FireTV box. What caused it was one of the SQLite editor I used to explore the settings database: it changed the permissions on the files. I only realized the problem once I rebooted it
On the other box, I used the SQLite3 command line client from TitaniumBackup instead, and directly did my edit as root. No problem there.
Unfortunately, I am not in US; so if there is a way to do a hard reset, I would be glad to know.

if you bought yours at a local best buy and are a select customer, you may have an extended return policy.

You must have edited something you shouldn't have with the sqlite editor. I edited mine to allow package installs and did a factory reset and its all good. Did you only disable the updates through pm disable com.amazon.dcp or did you also edit the /etc/hosts? Lets get this figured out so others don't end up the same way.

Stupid question, did you pick TWRP as a method of recovery during the rooting process? I did that on my note 10.1 and boy did it mess up that tablet when I tried to recover it. Luckily I had Odin at the time.
Sent from my SM-N900V using Tapatalk

arman68 said:
I am in the same situation with one of my FireTV box. What caused it was one of the SQLite editor I used to explore the settings database: it changed the permissions on the files. I only realized the problem once I rebooted it
On the other box, I used the SQLite3 command line client from TitaniumBackup instead, and directly did my edit as root. No problem there.
Unfortunately, I am not in US; so if there is a way to do a hard reset, I would be glad to know.
Click to expand...
Click to collapse
Do you recall which sqlite editor app you used that caused the problem?

Be interesting to know if there's a stock recovery, and if there is, if it's looking for an update.zip file on a thumb drive in the USB slot. We can tell that USB slot is getting polled at start time by the way that certain connections to it will hang the device.
If it were me, I'd try is to obtain a 1 gig or so USB drive, format it fat32 and copy the OTA update to it.
- Leave it zipped.
- Name it update.zip
- pull the plug on the FTV
- put the USB stick in
- power it on and leave it for a bit. Watch it - is the power LED going out? If so, it may doing a recovery install of the signed OTA and rebooting - many Android devices will install anything on the sdcard called Update.zip if it's there at boot time.
The idea is that if there's a stock recovery it may be able to see that USB storage and read the OTA file as a recovery source.

roustabout said:
Be interesting to know if there's a stock recovery, and if there is, if it's looking for an update.zip file on a thumb drive in the USB slot. We can tell that USB slot is getting polled at start time by the way that certain connections to it will hang the device.
If it were me, I'd try is to obtain a 1 gig or so USB drive, format it fat32 and copy the OTA update to it.
- Leave it zipped.
- Name it update.zip
- pull the plug on the FTV
- put the USB stick in
- power it on and leave it for a bit. Watch it - is the power LED going out? If so, it may doing a recovery install of the signed OTA and rebooting - many Android devices will install anything on the sdcard called Update.zip if it's there at boot time.
The idea is that if there's a stock recovery it may be able to see that USB storage and read the OTA file as a recovery source.
Click to expand...
Click to collapse
There might be something to this idea. There was a review posted on Amazon and the reviewer had a Best Buy box that wouldn't go past the Amazon screen. They said Amazon told them how to use the USB to get it to work. A couple people asked for more info but they never responded. I have tried going back through the reviews to see if they ever did, but there are almost 6000 reviews.

kairnage said:
There might be something to this idea. There was a review posted on Amazon and the reviewer had a Best Buy box that wouldn't go past the Amazon screen. They said Amazon told them how to use the USB to get it to work. A couple people asked for more info but they never responded. I have tried going back through the reviews to see if they ever did, but there are almost 6000 reviews.
Click to expand...
Click to collapse
i have only sideloaded a few apps , no root or root attempt was made before issues.
i have a similar boot issue ( stops at amazon first screen and led flashes white) . i believe my remote is fried , batteries heated up while pressing the home button to pair remote , i removed battery and found the plastic wrap on one starting to burn . i believe remote is toast .
can anyone verify that the boot will stop until remote is paired ?
ps : amazon phone help mentioned reset on remote was hold right arrow key ( ie right circle ) and home button for 10 secs , to reset just the remote ,. nothing helped mine , i say its dead. another is on the way ,. he also said the lack of pairing with remote should not have stopped the ftv boot , it should have gone past first amazon screen . other than restarting the ftv by disconnecting power he offered no other reset method .

bkdg100 said:
i have a similar boot issue ( stops at amazon first screen and led flashes white) . i believe my remote is fried , batteries heated up while pressing the home button to pair remote , i removed battery and found the plastic wrap on one starting to burn . i believe remote is toast .
can anyone verify that the boot will stop until remote is paired ?
Click to expand...
Click to collapse
Removed batteries from remote and rebooted FTV, boots like normal, could not find a way to delete a paired remote otherwise I would have tried that too,

userr12 said:
Removed batteries from remote and rebooted FTV, boots like normal, could not find a way to delete a paired remote otherwise I would have tried that too,
Click to expand...
Click to collapse
thanks ,. i called amazon they confirmed normal boot even without pairing ,. also said how to reset "just the remote" ,. right tab and home for 10secs.

kairnage said:
There might be something to this idea. There was a review posted on Amazon and the reviewer had a Best Buy box that wouldn't go past the Amazon screen. They said Amazon told them how to use the USB to get it to work. A couple people asked for more info but they never responded. I have tried going back through the reviews to see if they ever did, but there are almost 6000 reviews.
Click to expand...
Click to collapse
I'm trying to find that review now. so far nothing

fireTVnews.com said:
Do you recall which sqlite editor app you used that caused the problem?
Click to expand...
Click to collapse
I have reviewed the logs of what I did, and it was my fault:
I used a non-root SQLite editor, which means I had to give -rw-rw-rw- access to the database folder and content, which I did.
With the SQLite editor, all I did was to explore the database structure.
Once done, I restored the original permissions, fist -rw------- (chmod 660) on the database folder and database file itself.
Finally I restored read-only -r-------- (chmod 600) to the extra files (settings-*), and that was my mistake: I did not notice my chmod line had 2 entries, with the first one being the database folder (wrong)
If only I would have root write access to the file system with adb, I could easily fix it, with a simple chmod 660 on the database folder.
In hindsight, I was very careless to do that directly on the FireTV; I should have taken a copy of settings.db, and explore it on the PC.

Luxferro said:
I'm trying to find that review now. so far nothing
Click to expand...
Click to collapse
Yeah I took a look again today. Their search doesn't really drill down very well.

Luxferro said:
I'm trying to find that review now. so far nothing
Click to expand...
Click to collapse
kairnage said:
Yeah I took a look again today. Their search doesn't really drill down very well.
Click to expand...
Click to collapse
Here are all the reviews with the word "USB" in them on one page:
http://firetvnews.com/review_usb.html
I skimmed through it but couldn't find the elusive review.

@Firetv: please review post #15 in this thread, and consider adjusting the post on your website accordingly - when I saw your site, it was stating that adjusting values in the settings databases risked changing the permissions on those databases.
That does not appear to be the case, but rather reflected confusion on the part of the person who was doing the settings changes and permissions changes from the shell at the same time.
I haven't seen a db editor that changes the permissions of the dbs themselves....'
Back to softbricked devices: I see that Amazon sells a thing called a "fastboot cable" which in theory forces the Kindle Fires to reboot into fastboot mode if attached to a computer. I'd be interested in what one of these did in conjunction with an A to A converter, since I haven't seen fastboot mode available yet (that I know of)

roustabout said:
@Firetv: please review post #15 in this thread, and consider adjusting the post on your website accordingly - when I saw your site, it was stating that adjusting values in the settings databases risked changing the permissions on those databases.
That does not appear to be the case, but rather reflected confusion on the part of the person who was doing the settings changes and permissions changes from the shell at the same time.
I haven't seen a db editor that changes the permissions of the dbs themselves....'
Back to softbricked devices: I see that Amazon sells a thing called a "fastboot cable" which in theory forces the Kindle Fires to reboot into fastboot mode if attached to a computer. I'd be interested in what one of these did in conjunction with an A to A converter, since I haven't seen fastboot mode available yet (that I know of)
Click to expand...
Click to collapse
I've definitely been tempted to remove the warning about SQLite databases after reading arman68's update. I haven't, however, because I've been individually contact by someone stating they used a free SQLite app from the Google Play store which caused them to lose their ethernet connection and soft-bricked after a restart.
I have gone ahead and updated the post to reduce the concern and stated that the SQLite Editor app everyone is using here seems to be safe.
Also, a fastboot connection can be achieved with any A to A USB cable. You simply need to boot the Fire TV while it's connected to a computer and it will boot into fastboot. I've done this myself with a Mac (have not tried a PC). The Fire TV displays a white Amazon logo on the screen and stays there until you reboot it without the cable plugged in. There doesn't seem to be much that can be done with the locked bootloader, but then again, I'm not the one to know as that is all new territory for me. Got any suggestions on things to try with fastboot?

fireTVnews.com said:
I've definitely been tempted to remove the warning about SQLite databases after reading arman68's update. I haven't, however, because I've been individually contact by someone stating they used a free SQLite app from the Google Play store which caused them to lose their ethernet connection and soft-bricked after a restart.
I have gone ahead and updated the post to reduce the concern and stated that the SQLite Editor app everyone is using here seems to be safe.
Also, a fastboot connection can be achieved with any A to A USB cable. You simply need to boot the Fire TV while it's connected to a computer and it will boot into fastboot. I've done this myself with a Mac (have not tried a PC). The Fire TV displays a white Amazon logo on the screen and stays there until you reboot it without the cable plugged in. There doesn't seem to be much that can be done with the locked bootloader, but then again, I'm not the one to know as that is all new territory for me. Got any suggestions on things to try with fastboot?
Click to expand...
Click to collapse
I didn't mean to say you can't hose your device by changing settings with an editor, just that I don't think any of them change permissions. so using them to look but not change is pretty safe, IMO, and I'd hate to see folks discouraged from doing so.
I'm surprised that there's not a better onboard recovery on this device, or at least not one anyone's figured out how to get moving. I'dthink it'd be cheaper for Amazon if the devices had a viable recovery, or if there was a solid reset to factory which actually did a full reinstall of the OS.
Interesting about the fastboot mode - when i connect the FTV to my laptop using an A to A cable I don't get a device recognized in fastboot, but it may be down to not having a driver for it.

[RECOVERY] TWRP 2.8.6.0 for Shield TV (all variants)

I was going to wait for this device to be added to devdb to make a release thread, but that's being delayed, if it'll ever happen. So, I'm making this thread as a placeholder. No big fancy text, just a known problem list and the release. If you're looking for this, you probably know what to do with it. Everything should work from flashing to backup and restore from all external media. If it doesn't, please report it.
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
SOURCE:
device (branch cm-12.1-mrom)
kernel
vendor
CURRENT RELEASE:
For Android M:
twrp-20160222-UNOFFICIAL-foster.img
Known Issue: This release does not work on 4K displays. It boots to a black screen. Please use a 1080p display for TWRP until this is fixed.
For Android L:
twrp-multirom-20151112-UNOFFICIAL-foster.img
OLD RELEASES:
twrp-multirom-20150630-UNOFFICIAL-foster.img
twrp-multirom-20150624-UNOFFICIAL-foster.img
twrp-multirom-20150613-UNOFFICIAL-foster.img

MultiRom will be a must have on this device.
I really appreciate your work, and reading the various thread on xda I found out that you're one of the best developers for Nvidia Shield devices.
Without people like you we would all be locked in a large digital cage.
Compliments

Thanks Steel01!

I'm starting to slowly look at what I can disable in the kernel to shrink it down enough to fit in the recovery partition. Unfortunately, my first two ideas, network and sound, can't be unilaterally removed due to the android USB gadget (used for adb) depending on them. I've got it down to 26 MB, but iI dont know if it still boots. I'll try a few more things and hopefully have something working in the next couple days. I'm also hoping Tasssadar merges the 2.8.7.0 changes soon, the resize functionality will be useful (in testing I somehow shrunk my user data partition to 11 GB and had to reformat it get the full 4?? GB back).

Or it could be quicker than I thought. Todays test was successful. It's small enough to barely fit in the partition and appears to work correct. The link is in the OP. The next update to the multirom TWRP will probably make it too big again and I'll have to rip some more stuff out...

I want to install twrp recovery on my 16gb Shield, but i have no need for multirom. Is there an option to bypass the boot option or should I wait for a standard TWRP?
You didn't take much of a break before going back at it again. Thanks for your dedication!

Well, I'm not going back at it fully yet. Next week and a half will likely be pretty busy. I'm just doing a piece here and there.
This TWRP has multirom support, but does not require it or even set it up by default. In fact, to enable multirom, you have to install a separate zip (which I haven't released because it doesn't work). So no, you won't see any extra boot screens with this.
A standard TWRP build should be simple to make with the sources I've linked in the OP. I haven't released one here (or on any device I support) because I don't want to support it directly (basically, I'm supporting what I use myself). If no one else makes one, I might make a one time build for those that want it.

Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks

Remote controller fix
cdsn99 said:
Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
cdsn99 said:
Hi Steel01, . Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy

Josti-Band said:
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy
Click to expand...
Click to collapse
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.

cdsn99 said:
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.
Click to expand...
Click to collapse
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.

I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy[/QUOTE]
Josti-Band said:
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.
Click to expand...
Click to collapse
Thank you, that makes better sense, I will try and load a rom and gapps and see how it goes. thanks again for the assistance

Steel01 said:
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Hi Steel01 , I have a logitech k400r wireless keyboard and mouse, it seemed to work ok, except was very laggy, had to wait for it a few seconds each time I went to move the mouse, and sometimes mouse would freeze.
Click to expand...
Click to collapse

I have edited and deleted the orginal text from this post,and moved it to it's own thread. I realized I was beginning to hijack steels thread, I couldn't find a way to just delete the whole post, sorry.

Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.

Steel01 said:
Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.
Click to expand...
Click to collapse
What about the kexec-hardboot patch ? Do you have already tried it ?
The others binary for multirom execution are the same for all arm64 devices like the nexus 9 or we need a specific build for shield ? I never played with multirom stuff. There are specific problems to solve ? In case i can help you with experiments if you don't have much time.
P.S.
I tried your patch for the framework and all others new Nvidia binary + resigned private apk like blakepairing and others. But this year Nvidia added many others things to the framework. You can see by yourself with dex2jar.
It's a shame that for a stupid controller there are all this bloatware inside the firmware. Very bad behaviour, that a so big company not publish drivers for an hardware that we have bought. Fortunately we can use also better wireless controllers. But this fact really remove 10000 points from Nvidia as good company.

I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.

Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse
Already tried all. deodexed and resigned stock stuff, also used your framework patch and your (resigned) apks . not work in shield console. as i write above in shield console there are others proprietary things in the framework. Tested also with your wpa_supplicant and hostapd but the result does not change.
In any way i will retry
We can discuss in a separate thread. sorry for off-topic. can be useful also for others developers

This is very interesting, please continue with this work! Would be great to get the remote working on other ROMs.
Thanks!
Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse

Steel01 said:
I
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Click to expand...
Click to collapse
I have a logitech K830 keyboard with trackpad and have exactly the same issue as you. I have to unplug and replug the usb receiver before it will work with the recovery.
The recovery itself is working great for me. I can access my external usb hd from the file manager, and I did a TWRP backup to the external usb drive last night :good: Ive sideloaded this app to boot straight into the recovery from the TV.. https://play.google.com/store/apps/details?id=gt.reboot.utility

Kodi unresponsive

Ok, first off let me start by saying I'm a very new user. I purchased a new Amazon Fire Tv stick and tried installing Kodi. My first try I used AdbFire and was unsuccessful. I deleted and redownloaded AdbFire and was able to get installed. I then added SuperRepo and a few add ons with no issue. Even watched a movie that night. The following day I came home and couldn't get any folders to load movies. Kodi seemed sluggish and wouldn't download anything new. I read everything I could online and decided to reinstall Kodi 15.2 as I had accidentally installed 15.1 the first time. Could not get AdbFire to install. Would just constantly process. Was able to use an android app Apps2Fire and get it installed that way. Although that also took quite some time. Now Kodi doesn't load anything. It's very sluggish, won't fully add sources. If I get a source to download, such as SuperRepo, the add ons stay at 0% then cancel or move very slowly 1-3% then cancel. I've checked my internet which is fine. im not too familiar with how to share my debug log but will try after this post. Any help would be greatly appreciated

JEucce88 said:
Ok, first off let me start by saying I'm a very new user. I purchased a new Amazon Fire Tv stick and tried installing Kodi. My first try I used AdbFire and was unsuccessful. I deleted and redownloaded AdbFire and was able to get installed. I then added SuperRepo and a few add ons with no issue. Even watched a movie that night. The following day I came home and couldn't get any folders to load movies. Kodi seemed sluggish and wouldn't download anything new. I read everything I could online and decided to reinstall Kodi 15.2 as I had accidentally installed 15.1 the first time. Could not get AdbFire to install. Would just constantly process. Was able to use an android app Apps2Fire and get it installed that way. Although that also took quite some time. Now Kodi doesn't load anything. It's very sluggish, won't fully add sources. If I get a source to download, such as SuperRepo, the add ons stay at 0% then cancel or move very slowly 1-3% then cancel. I've checked my internet which is fine. im not too familiar with how to share my debug log but will try after this post. Any help would be greatly appreciated
Click to expand...
Click to collapse
I'd say there maybe something wrong.... Don't know what but ether something is wrong or your not doing something right? 1. I'd go to the kodi apk & clear cache & data 2. Then try using the following add ons & see if these work - Navi-X, Phoenix, UK Turk (seach on Google how to get them & install) see if that works for you? 3. If not id search on Google or Xda on how to reset your fire TV to factory settings (not sure but it might be in fire tv settings? Think I've seen it somewhere?) Then download Kodi again & send to your stick via App2Fire, then try step 2 again & see if all is ok now? Hope this helps & press that like button If it did.

The best advice after you get Kodi working again Is that you make a Kodi backup, save it somewhere safe (on a pc/phone/sd card/us stick or what ever) & if you have any problems again You can just reinstall Kodi & then reinstall your backup.

JEucce88 said:
Ok, first off let me start by saying I'm a very new user. I purchased a new Amazon Fire Tv stick and tried installing Kodi. My first try I used AdbFire and was unsuccessful. I deleted and redownloaded AdbFire and was able to get installed. I then added SuperRepo and a few add ons with no issue. Even watched a movie that night. The following day I came home and couldn't get any folders to load movies. Kodi seemed sluggish and wouldn't download anything new. I read everything I could online and decided to reinstall Kodi 15.2 as I had accidentally installed 15.1 the first time. Could not get AdbFire to install. Would just constantly process. Was able to use an android app Apps2Fire and get it installed that way. Although that also took quite some time. Now Kodi doesn't load anything. It's very sluggish, won't fully add sources. If I get a source to download, such as SuperRepo, the add ons stay at 0% then cancel or move very slowly 1-3% then cancel. I've checked my internet which is fine. im not too familiar with how to share my debug log but will try after this post. Any help would be greatly appreciated
Click to expand...
Click to collapse
Whats your internet speeds ? I always recommend at least 10Mbps if wanting to steam HD , but I seen people do it with less. I had issues like this with fire stick before, thats why I rather use a fire tv. Best advice is to delete and start again. Also make sure you clear cache , I use tvaddon maintenance tools for that. I notice you jump around from source to source , it can hang up especially if you streaming something large in background. Also sometime need a reboot, unplug or hold the two buttons. Also , when changing version of software, be-careful not to install on top old software, Same as restoring from a back up. If you have data in there already, do a fresh start, then restore from you back up. Hope you fix your issues, and good luck, Keep us posted on how you make out .

Req: Hardware root / reflash service FTV Stick (USA)

Just wondering if some kind hacker would like to practice soldering and flashing on my Fire TV Stick. I was one of the folks who semi-bricked theirs with supersu me and Kingroot...
I have ADB but no root, boots to a black screen after animated rainbow logo. I can reboot to recovery, which seemingly does not make any changes to the device. Invoking a program like su or attempting a pm install freezes the adb shell. I haven't tried anything over USB yet. Invoking the settings menu, for instance, has no effect. I can get logs, ps, and navigate folders, but I don't think I'm going to be able to get it to a home screen.
But I wanted to put it out there - I'd throw some money your way for time, trouble, and shipping if you think you can re-flash it.
A dozen thanks in advance...

I have the same problem after I use supersu me with my box. stop at color amazon logo. Hope anybody can give me some idea to make it factory reset or pay for hardware write the emmc