yashsingh1/xdaforums huggingface dataset:
[Kindle Fire 2 Q&A, Help and Troubleshooting] stunts513:
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
[Kindle Fire 2 Q&A, Help and Troubleshooting] xanthian23:
OK, I have both a tf - micro sd card usb card reader, and a full sd card usb card reader. I'll have to go digging for them in the morning, but I think I can find them. I'm also really good with a soldering iron, (used to be a vcr / tv repair technician), It took me roughly two minutes to do the homemade factory cable. So I am game, especially since at this point I really have nothing to loose by trying. Would you mind posting a link to where the tutorial is? I'm going to go looking for it, but just in case I can't find it, a link would help. And thank you so much for this suggestion!
[Kindle Fire 2 Q&A, Help and Troubleshooting] xanthian23:
OK, I found the tutorial on how to wire everything up and what's needed. I'll have to go get some small wire and a better tip for my iron, but aside form that, the wiring and soldering seems simple enough. My problem is going to be dealing with linux. I know Windows backwards and forwards, but I have a pretty limited knowledge of linux, aside from a few things we did in school to cover general PC repair. I can get it up an running, which I will do tomorrow, but I may need some help sorting out what to do with it once I have the board lined up and ready to roll, which will have to wait till next week when I get back from a work trip. Do you know if kurohyou offers repairs? If it's not too expensive, I would be willing to pay for the fix.
[Kindle Fire 2 Q&A, Help and Troubleshooting] stunts513:
He might repair it, he just made a solderless repair tool to repair them. But like I said I'm more than willing to help with the Linux side, I'm a PC tech myself and use Linux primarily, you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
[Kindle Fire 2 Q&A, Help and Troubleshooting] xanthian23:
Yeah, I've ran a live usb version of unbuntu a few times, and in the past I have had the full version on my system, but I rarely ever used it, so I got rid of it. I have an extra 600 gig's of space just sitting around on my laptop, so I will install a full version, and get off my lazy rear and start learning linux. This should be a good first lesson. I can't do any of this until next week though, so I will be pm'ing you once I've gotten everythig hooked up and ready to go. Thanks again for the help.

I had a question about the repair though. I went through the discussion, and I may have just missed it, but did he ever figure out how to get the OS up and running? From what I could tell, he was still working on it, and hadn't managed to get a working rom loaded. I probably just either missed it, or didn't understand one of the post's.
[Sony Smartwatch] leadingyouupthegardenpath:
There are plenty of notifiers out there for the SW2, some work well and some apparently not so good. What I am wondering is whether anyone has developed a whatsapp application that actually allows you to reply to messages, perhaps by using preset messages in the same fashion that the sms app allows you to?
[Sony Smartwatch] Skajewski:
Good question. Wondering the same thing.. Either whatsapp or even better-- hangouts.
[Sony Smartwatch] stopa10:
I believe that currently the only way to do these (and many other similar) things is to use Tasker. You would need to create a Tasker task to reply to Hangouts messages with pre-defined texts, and then trigger that from the watch
[Fuhu Nabi 2] kaijan:
I wanted to upgrade my Nabi with the latest OTA. I had TWRP 2.2.2.1. I used it to revert to an old backup. After the restore, I tried to apply the OTA updates. After it rebooted and started the install I got an "!" Android logo.

I power cycled and I was able to boot back in. I noticed I still had the Play Store app (which will not work, error about connecting to services) and suspect the "stockunrooted" restore I used may not have been completely "stock". I did lose root and TWRP though.

I tried to reinstall TWRP again, but it appears that Fastboot no longer works since the restore. The tablet just hangs on the Nabi logo indefinitely. When I press Vol - & + with PWR, and select Recovery Mode, I just get another "!" Android logo (is this stock recovery?).

ADB works, it sees the tablet and I'm able to push, access shell etc.

I used motochopper to root the Nabi again. I tried installing flash_image to manually flash a new TWRP recovery.img, but running the command I get an error about "error scanning partitions".

I'm not sure what else I can do to get Fastboot working or a recovery system installed again. OTA upgrade will not apply, and I'm stuck on 1.9.37 at this point.

Does anyone have a suggestion how I can get Fastboot fixed and the Nabi back to "normal" / upgradeable.

Thanks for your help
[Fuhu Nabi 2] aicjofs:
What software rev did you get to when doing the OTA's?

That is usually a sign that various Google services are removed from the system partition. So in that case it is returned to stock, but there is still information of the Play install on the data partition.

Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.

Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.

For example if the recovery image is on the internal SD

dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
[Fuhu Nabi 2] kaijan:
OTA is trying to install 2.1.27

You were correct about the fastboot driver issue. I was using Windows 8.1 and it it wasn't working properly. I switched to Ubuntu and now have no problems.

I was able to flash TWRP 2.3.3 and tried another restore to stock. Did OTA again, but still get the "!" Android shortly after it reboots and starts installing. I can't seem to get rid of gapps either. Play Store is still installed. I've tried wiping /data/media, cache's etc and it still remains.

I'm not sure why the OTA upgrade keeps failing. Do you think it's due to the gapps still being on the device?

Any other ideas on how I can get the OTAs to work?

Update:

I booted up stock recovery and tried the update from cache
[Fuhu Nabi 2] aicjofs:
Hmm that is it weird. It does look like gapps is still installed .As gapps removes gallery2.apk and why it's failing, I don't understand if it's stock how that is happening. Use these updates yet? http://xdaforums.com/wiki/Fuhu_nabi_2
[Fuhu Nabi 2] hotspace:
This thread died out....I hate to bump it back to the top...But I have a NABI2-NV7A that I rooted along time ago....and i booted it up and was gonna do some upgrades and everything went kaboom!!

I have TWRP 2.2.2.1 installed.

I can get into TWRP but not fast-boot mode

I'm on a laptop with windows 10 installed...I don't think it's driver related....as i can send commands via adb while TWRP is up....and the NABI responds to those commands

But i never get past the logo screen....and I'm not sure what to to do with NVflash.

I'm experienced...but rooted this thing and installed GAPPS like 2 years ago and the kids dug this thing up and the play store wouldn't work any longer....i read about the OTA....so i was trying to go back to stock and get those OTA's.

Any suggestions or advice?? Anyone...hello....bueller....bueller :)
[Fuhu Nabi 2] aicjofs:
Have you tried using "adb reboot-bootloader"

There are some things to try before breaking out nvflash. The easiest would be to flash the boot loader and a new TWRP in one recovery session.

Boot twrp2.2.21, Install KK boot loader zip and then install TWRP KK287 zip

Then restore the 3.0.13 ROM

Files and directions here

http://xdaforums.com/nabi-2/general/nabi-information-t3229119
[Fuhu Nabi 2] hotspace:
I did try ADB REBOOT-BOOTLOADER all that happens is the NABI2 restarts and sits at the logo screen.

I'm able to push via ADB, so I will download the suggested files and take your advice. I'll report back. And, thanks for the reply.
[Fuhu Nabi 2] hotspace:
Update...

I was able to push all of the needed files and I verified I pushed them completely by using "adb push -p xxxxxx /sdcard"

I then rebooted back into TWRP

I flashed KK3013bootloader.zip, then flashed twrp-recovery-NV7AUS-287.zip

Rebooted and I can't get back into TWRP. And, now I can't establish a connection for adb commands.

Any advice? tips...pointers? Could this truly be my first bricked device??
[Fuhu Nabi 2] aicjofs:
Nah Nabi2 is practically impossible to brick.

So do you get the command list in the top left when you press the vol and power buttons? i.e the selection continue, fastboot, recovery kernel, forced recovery? or when you select recovery kernel it just doesn't boot TWRP?

I wont type a lot of stuff until I get you answer but if we need to go the nvflash route this is some good reading. You will need to get in to APX mode, install the driver and issue some commands.

Read this post and next few pages after it

http://xdaforums.com/showpost.php?p=46579190&postcount=1687

General idea of commands

http://xdaforums.com/showpost.php?p=48683262&postcount=124

Might be some work, but we should be able to get the device back, I'll let you know which is the best way after I see your reply.
[Fuhu Nabi 2] hotspace:
Yup, no boot options. And, I can't get back into TWRP. I hold power button to shut it down. Then vol+ power and typically I'd get the boot options, but nothing, just the logo. Then hold power button to shut down. Continue...repeat...

I appreciate you sticking in for the long haul on this. :)
[Fuhu Nabi 2] aicjofs:
Damn. It IS going to be a long haul, but you will know the tablet well when its done. I don't have the tablet to test anymore, so I have to work from memory(and that's been a long time)

Well the bad news is this is going to require opening the tablet. See this post http://xdaforums.com/showpost.php?p=46694284&postcount=1701

You are going to have to short those pins to get it in to APX mode and use nvflash

-You will need the APX driver as well.

-The nvflash package

http://xdaforums.com/nabi-2/general/nabi-information-t3229119

I will type more later.
[Fuhu Nabi 2] hotspace:
Sweet! Looking forward to this.
[Fuhu Nabi 2] aicjofs:
Get the nvflash package from the Nabi General Info thread I linked above

Unzip in to a directory of your choosing and open a command prompt in that folder

The Nabi will be broken open and connected by USB to computer

So once you get those pins shorted and press the power button the screen should come on and be completely black(you can tell the backlight is on though)

Check in device manager for a new device(it will be auto detected or you will have to manually install APX driver)

Once the driver is installed you can issue nvflash commands

nvflash --bl bootloader.bin --download 4 bootloader.bin

Before pressing enter for the below command get ready to press and hold the vol+ key.

nvflash --resume --go
[Fuhu Nabi 2] hotspace:
Right on. I'll dig into this in the morning
[Fuhu Nabi 2] hotspace:
[MENTION=4939189]aicjofs[/MENTION], I still haven't begun breaking the Nabi down. I'm working from home today and should be able to squeeze the disassemble in sometime today.

I scanned through the comments you've left since finding out I wasn't able to get to the boot menu...I'll post back once I get it torn apart.
[One (M7) Q&A, Help & Troubleshooting] BTow1105:
Is there a way that I can allow my phone to use the internet connection from my desktop PC? I get a terrible Wifi signal in my bedroom and I also get a terrible data connection from AT&T in here. Is this possible?

My phone is on 4.4.2 Google Edition, S-off.
[One (M7) Q&A, Help & Troubleshooting] dirtbikerr450:
yes follow this guide http://xdaforums.com/showthread.php?t=2287494
[Glass General] adamdescott:
I read somewhere that there is a RX version in the mix. Does anyone know if the current model can be used with RX lenses/frames? I finally received an option to purchase, however I need to be able to see.
[Glass General] danguyf:
Yes, the current version (v2) can be removed from its titanium band and attached to various prescription frames via a single T4 screw.

Rochester Optical has announced that it will begin selling frames and prescription lenses following CES, which runs 7-10 January 2014, starting at $99. Google has released pictures of their own frames but has not announced a timetable for when they will be available.
[Glass General] pytyper483:
That's weird. I just called glass and was told that they are working on a fix for this, but nothing yet. I wear rx glasses too, but using them with glass, it hurts my nose and I see double vision (reflection on my rx lenses). They walked me through tweaks to the nose pieces, but nothing else.
[Glass General] danguyf:
Since Google has not yet announced availability of their prescription lenses and frames, perhaps the Glass Guides are not allowed to talk about them yet? They're not going to advertise Rochester Optical's frames and lenses, as RO is not affiliated with them.

You can remove the Glass body from the frame and attach it to your glasses, if you like. Some people use zip ties; I used velcro strips. This may help with the discomfort. Depending on your frames, though, it may place the Glass screen in a less optimal place, though. I ultimately went back to using the factory titanium band and bend the nose pieces so that they would sit on the bottom lip of my frames, moving the Glass into a good position and making it so that only my glasses are touching my face, alleviating the discomfort.
[Nexus 7 (2013) Q&A] chugger93:
Do any of you guys change your DPI? Does this still affect the play store by changing it? I know in past device history it did, but I havnt touched DPI's since on new devices I've owned.

I was considering upping it to like 240 on my new N7. Just wondering about ramifications..or even if xposed framework could do it...although I didnt see a module. Thx!!
[Nexus 7 (2013) Q&A] Mandelbrot.Benoit:
Yeah use exposed and the module app settings. Change the launcher DPI and it shouldn't affect the play store.
[Android Q&A, Help & Troubleshooting] Inuya5ha:
Hi, I'm about to use this guide to root my Iconia B1-A71 tablet, but there's something not clear and I don't want to take any risks.

The main guide post, under the Acer Iconia B1-A71 Downloads says:

Now, I acquired the tablet recently and applied an official patch provided by Acer directly from the built-in update checker.

My question is: The patch I installed, from the built-in update checker, is the same "Invalid Partition Error fix" mentioned in the guide? In this case, I guess I should skip this step.

Or is it an absolutely different patch and I must install it anyway?

The question raises after I read that the Invalid Partition Error fix is "from Acer", while Acer rarely provides fixes or patches... (and for that reason, all Iconia B1 users are stuck with the obsolete Android 4.1.2, but that's a different story)

Android 4.1.2
Kernel version 3.4.0
Image version Acer_AV051_B1-A71_RV04RC04_WW_GEN1
Build number Acer_AV051_B1-A71_1.174.00_WW_GEN1
Image P/N FM.NLCA0.01M

Thanks in advance for your time.
[Nexus 5 Q&A, Help & Troubleshooting] neocryte:
I am not too versed with this, was hoping that someone could help. My battery life while in idle seems to be suffering quite a bit. Here are the wakelocks that I see using BBS. Any idea what I should do to help my situation?

Do folks keep Google Now off? That seems to be one of the wakelocks but not sure what the other one is.

I'm on stock 4.4.2 using Franco's kernel r24.

Thanks very much!
[Nexus 5 Q&A, Help & Troubleshooting] neocryte:
Don't know why the second pic didn't attach, including now.
[Nexus 5 Q&A, Help & Troubleshooting] alistairs1:
Here's a thread where people have already discussed. No real solution yet other than reboot and hope it goes away ...

http://xdaforums.com/showthread.php?t=2529719
[Nexus 5 Q&A, Help & Troubleshooting] PhilipTD:
I'm also on stock 4.4.2 and Franco, and have the same BBS stats, but when my phone is in stand-by, it only burns 1-2%/hr. SOT, on the other hand, is 9-10%/hr. on low brightness, and can go up to 15%/hr on medium brightness.

Sent from my Nexus 5
[Nexus 5 Q&A, Help & Troubleshooting] Aerowinder:
Switch location mode to device only.

To permanently solve Google Now issues, Greenify it via Xposed. Unsure of the ramifications of this if using GEL.
[Nexus 5 Q&A, Help & Troubleshooting] neocryte:
I'm not familiar with Xposed - isn't Greenify just a regular app? Thanks for the help!
[Nexus 5 Q&A, Help & Troubleshooting] Aerowinder:
Greenify is an app on the play store, but you can't greenify system apps with it unless you get Xposed, and get the donation version of Greenify. That's how you Greenify a system app. If you don't want to go that route, you can try uninstalling Now, then grabbing it from the play store (or just move it to /data). This way Greenify will be able to control it.
[Nexus 5 Q&A, Help & Troubleshooting] neocryte:
Thanks mate. I gave it a try, but for some reason greenify with exposed did some weird things to my battery settings - the screen on time didn't advance (always said 2 min 32 sec), and better battery stats didn't display most of the usual stats. After I disabled Xposed and greenify, it worked fine again. Weird.
[Verizon Samsung Galaxy S III] Mystique:
Things like ps, grep and ls are symlinked to the toolbox binary..

As well as /system/bin/sh..

Any harm or problems with linking those to real busybox?

Or get an updated toolbox binary with updated commands?

Updating busybox seems more realistic than updating toolbox..

I understand running busybox grep or busybox ls -ltr works..

Typing in the terminal via software keyboard isn't the most efficient..
[Upgrading, Modifying and Unlocking] laurencee:
I have a MDA Vario T-mobile U.K. and i have tomtom updated version installed on the MDA, which works absolutely fine. However the only problem i have is when i attempt to peer with the GPS it does not work. My MDA Vario cannot communicate with the GPS device via bluetooth

I tried to configure the GPS on tomtom configuration menu, but i cannot find the COM 6 to enable it to work via bluetooth

Can someone help ?

Thank you :(
[Upgrading, Modifying and Unlocking] indra9110:
just try the configuration for tomtom GPS with the instruction on WIKI

I have the same problem with you but now its solved .... by read WIKI ... :lol: :lol:
[Upgrading, Modifying and Unlocking] Rick GM:
Not sure if this will work for you but it did for me.

http://xdaforums.com/viewtopic.php?t=28386&postdays=0&postorder=asc&highlight=tomtom+5+gps&start=100
[Kindle Fire 2 Android Development] obsolete1:
UNOFFICIAL SlimKat for KindleFire2 **Now with Linaro SaberMod toolchains

Features

**DISCLAIMER**

/*
* Your warranty is now void.
*
* I am not responsible for bricked devices.
* Please do some research if you have any
* concerns about features included in this ROM
* BEFORE FLASHING IT!
* YOU are choosing to make these modifications.
*

I am in no way part of SlimROMS thus take no credit for their source code.

I have just compiled from their source for the KindleFire2

Screenshots

**The first Antutu is with Dalvik (score 9966) the second is ART enabled (score 9505)​

Installation

You must have second bootloader & TWRP 2.7.1.0 or this ain't gonna work

Known Issues

Old release

Change Log

SlimRoms Official change log

**Sep 10, 2014 - Source sync

**Aug 27, 2014 - Source sync, now built with SaberMod toolchains.

**Aug 24, 2014 - Source sync

**Aug 13, 2014 - Source sync, now built with Linaro toolchains.

**Jul, 28, 2014 - Updated *Swapped out NovaLaucher for stock KitKat per request

**Jun 28, 2014 - Updated

**Jun 15, 2014 - Updated

**Apr 12, 2014 - Updated finally

**Jan 18, 2014 - Source sync - Correct SlimKat version now showing in build

**Jan 05, 2014 - Source sync

**Dec 27, 2013 - Initial build

Credits

SlimROM - For their source

CyanogenMod Team

[URL="http://xdaforums.com/member.php?u=4243514]Hashcode[/URL] - Without him this ROM wouldn't be possible

~If I forgot you please let me know!

​
[Kindle Fire 2 Android Development] stevemp:
wipe

Use advanced wipe, select every thing except internal storage to keep your files. Great job porting these roms. :good:
[Kindle Fire 2 Android Development] iamterence:
Sick, dude!! Thank you so much for keeping the Kindle Fire 2 alive!!!
[Kindle Fire 2 Android Development] chronicfathead:
How's SlimKat running for you?
[Kindle Fire 2 Android Development] iamterence:
Haven't flashed it yet, haven't been home to be on my tablet. Did you flash it? If so, how's it running for you?
[Kindle Fire 2 Android Development] mindmajick:
Best to use slim gapps btw

http://slimroms.net/index.php/downloads/dlsearch/viewcategory/978-addons4-4/downloads/dlsearch
[Kindle Fire 2 Android Development] obsolete1:
OP updated thanks!
[Kindle Fire 2 Android Development] mindmajick:
Thank you my friend! Now in running the same ROM on both my phone and my tablet.

Loving the real dark slim :)

--》Sent from my mind to your screen
[Kindle Fire 2 Android Development] mindmajick:
Starting to get funny graphical glitches and ghosting.. Going to try your carbon rom in the meantime
[Kindle Fire 2 Android Development] chronicfathead:
Yep. Had to wipe data coming from Hashcodes CM11 and WiFi didn't want to connect straight away. It did connect after a while though.

I have also had a few graphical issues, in Play books app. Some of the menus are all dotty, then they pop to normal after a while.
[Kindle Fire 2 Android Development] mindmajick:
Dude. Your avatar from "the IT crowd"? I loved that show. Watched it on Netflix.. Wish it had continued

--》Sent from my mind to your screen
[Kindle Fire 2 Android Development] nelsonator1982:
Will this be updated?
[Kindle Fire 2 Android Development] obsolete1:
Yeah...I've been lazy this week.

Just synced...and I'll start the build shortly.

**UPDATE

New build is up, just a source sync
[Kindle Fire 2 Android Development] facelessloser:
multi window?

Does anyone know if this ROM has multi window surport. Or know of another ROM for the kindle fire 2 that does have multi window
[Kindle Fire 2 Android Development] obsolete1:
Weekly build updated. The proper SlimKat version (was showing 1.96).

Will get an update Antutu benchmark screen shot up scores went up slightly :)

Boot animation still offset at start hmmm....
[Kindle Fire 2 Android Development] anomalya:
thank you kindly!

do you mean it's still offset even with this merged?

no big deal, but i agree it's odd since the people over at the KF1s seem to have theirs fixed for a while now.
[Kindle Fire 2 Android Development] obsolete1:
I can cherry-pick it and rebuild :)

**EDIT

No I can't that change is already there...
[Kindle Fire 2 Android Development] jamminjon82:
New to the KF2, what issues are present in this rom besides the boot ani, which isn't a big deal? Thanks and looking forward to some slim kat.