yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] ariesgodofwar:
FYI, not sure of it is the cause of your problem, but about 4 months ago Microsoft pushed out an update file which contained the Acer ADB driver to Windows 8.1 systems. This replaced the original ADB driver of the machines, and will prevent you from connecting to your phone. Here is a thread discussing it: http://forums.androidcentral.com/go...dows-update-acer-composite-adb-interface.html

You want to roll back this update and install universal drivers. It took my forever to figure out what I could connect to my Win 7 Laptop, but my Win 8.1 was a no go, that was the problem. Loading the Drivers in the Toolkit will not fix this. You either have to roll back the update and reboot, or go into Device Manager and uninstall and delete the Acer driver, and replace it with something that works.

Might not be a problem for you, but wanted to toss it out there as a possible cause if you have not rolled back the Acer driver.
[G2 Q&A, Help & Troubleshooting] deschmitzz:
Hi Guys,

im new to the g2 (had it now 1 week) and i flashed it now the first time manually completly back to stock.

but in the download modus i have seen the red rooted logo and i wanna ask you how i can change it to "not rooted"

big thanks in advance and sorry for my ****ty english

greets from germany =)
[G2 Q&A, Help & Troubleshooting] deschmitzz:
nobody can help me? :(
[Off-topic] Marco Lomas:
Im courius about how many people around you, like friends ,family, pals, know at least the basics for android scene.

Be root ,flashing, all that stuf.

Im talking about near people, dont internet or forums :)
[Off-topic] Darth:
Off topic section,

http://xdaforums.com/general/off-topic

??
[Off-topic] Toledo_JAB:
moved to the proper forum
[LG G Flex] wanghaojie630:
Before my phone stuck at the fastboot, and i followed the http://xdaforums.com/showthread.php?t=2666763&page=8 but now my phone cant even go to fast boot. It will just loop the lg logo no matter what key i press.

The computer will not recognize it and adb devices wont show anything either. Is this phone done?
[LG G Flex] mattwheat:
Doubt it. It won't go into factory reset or anything no matter what button combination you use?

If not there is a pretty tricky long process using Linux you could try. I just used the method to bring back a Verizon lg g2 that would only go to the lg logo screen with the small 702 boot certification error in the top left corner.

---------- Post added at 05:43 PM ---------- Previous post was at 05:39 PM ----------

But you would need the

Sbl1.img

Boot.img

Aboot.img

SignedTwrp.img

Tz.img

Rpm.img

And use Linux to push the to the right partitions. Which you'll also have to use Linux to find out which partition locstions/ address (I guess you would call it ) they need to be pushed to.
[LG G Flex] kintwofan:
http://xdaforums.com/showthread.php?t=2582142

This is what matt outs talking about. You may be able to follow this guide using the correct images from kit Kat for your device. Using the aboot.img and recovery.img should be enough to fix you from what i understand you used the jb images from D-FUSE thread only.
[LG G Flex] mattwheat:
Yeah but do not use the stock recovery.img.
[LG G Flex] mattwheat:
And this method if done wrong can potentially render your device useless even to LG. So be careful.
[Nexus 6 Q&A, Help & Troubleshooting] jackdubl:
Several of us who live in the Kansas area on Verizon have had our LTE data borked by some change in the network configuration that happened a couple weeks ago. We are all running GPE roms; stock Verizon roms work fine. We were hoping someone with a Verizon Nexus 6 could do an apn backup and post it so we can either flash or restore it to see if it fixes our problem. Would anyone be willing to do this? I can walk whoever through at least one procedure to backup the APNs. If anyone could help, there would be a bunch of grateful people out here.

Free storage from Copy:

https://copy.com?r=cScoov
[Nexus 6 Q&A, Help & Troubleshooting] akellar:
Nobody has a nexus 6 and a Verizon nexus 6 doesn't even officially exist at this point
[Nexus 6 Q&A, Help & Troubleshooting] ddog511:
Out of curiosity, why does it have to be from a Nexus 6? Why couldn't you just use any VZW phone's APNs?
[Nexus 6 Q&A, Help & Troubleshooting] jackdubl:
Tried standard apn from our stock TW devices, but they didn't work. We were hoping the Nexus might work since it's stock Android like the GPE rom.

Free storage from Copy:

https://copy.com?r=cScoov
[Nexus 6 Q&A, Help & Troubleshooting] norwoodesteel:
Anyone try new sim card
[Nexus 6 Q&A, Help & Troubleshooting] jackdubl:
Didn't think of that. Wonder if that would have some effect.

Free storage from Copy:

https://copy.com?r=cScoov
[Fire TV Original Android Development] rbox:
This is a boot menu that will allow you to select if you want to boot a kernel or reboot in to recovery. I highly recommend everyone install this so you always have a way to boot in to recovery in case of problems. Just like recovery, it will sit at a black screen for an abnormal amount of time before showing. It's something like 20 seconds. But once it shows, you will have 5 seconds to make a selection. It defaults to booting the kernel, but you can use the up down keys to change the selection. Once it hits 0, it will do whatever option is selected. You can also hit enter and it will do that right away.

Right now, this is a very rough version 1.0. I plan to add some more features to it and would like to hear feedback from people to see what they think about it.

As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it

properly

won't brick your Fire TV. Of course, this requires root and unlock.

Installation

Install CWM version 6.0.5.1.4 or higher. You MUST VERIFY CWM is at least 6.0.5.1.4 and it works BEFORE proceeding. You WILL BRICK your Fire TV if you are not properly unlocked, and verifying 6.0.5.1.4 or higher is working will do that.

For the following instructions, replace bootmenu.img with whatever filename you downloaded from this post, for example firetv-bootmenu-1.0.img. Copy bootmenu.img to /sdcard (via adb or whatever). Then from adb shell run this: DO NOT COPY PASTE THE WHOLE THING, DO EACH COMMAND ONE AT A TIME.

su
mount -o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot

Once you have verified it is working, you can replace /system/boot/boot.img with whatever kernel you want. Whether it be the overclocked kernel, or a Fedora kernel, or something else. And you never have to worry about bricking or getting back in to recovery.

Notes

Flashing anything that updates boot.img will cause you to loose bootmenu support. All pre-rooted roms 51.1.4.0 and lower will do this. Anything past 51.1.4.0 will only support booting their kernels through this method. When flashing 51.1.4.0 or lower when using bootmenu, you must repeat the entire bootmenu installation procedure because those roms will overwrite the bootmenu.

Changelog and Downloads:

Nov 15, 2014 - 1.0 (md5sum: a8a3c28baafe43f354d92e6cc8b392d3)
[Fire TV Original Android Development] AQKhanTheOne:
Hmm, tried this and didn't seem to do anything. It did sit at the black screen for a while but then no boot menu comes up. Tried rebooting normally and to recovery but either way no boot menu come up, just boots straight to recovery or to XBMC (I've set XBMC as my launcher).

I'm using your 6.0.5.1.4a recovery, bootloader partially unlocked etc.
[Fire TV Original Android Development] rbox:
It's completely blank? I timed from 'adb reboot' to when the menu showed up and it was 24 seconds. Then you should see *something* on the screen, and then 5 seconds later it should reboot the firetv and then the kernel should start loading. 25 seconds after adb reboot, try hitting the down arrow and then waiting a few seconds. It should boot into recovery. Does that work? Also, are you using overscan in recovery?
[Fire TV Original Android Development] AQKhanTheOne:
Yes completely blank. Actually it only sat at the blank/black screen the first time it rebooted after the install. After that each reboot to either recovery or to XBMC does not result in the long blank screen at all. Though there is the briefest lightening of the screen right before the white amazon logo comes up. And no, I'm not using overscan. The result of the install is below if that helps. It's likely I've made a mistake.

shell@android:/ $ su
mount -o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
smount -o remount,ro /system
u
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/bootmount -
o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
root@android:/ # mount -o remount,rw /system
root@android:/ # mkdir /system/boot
dcc.1/by-name/boot of=/system/boot/boot.img <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.939 secs (5407818 bytes/sec)
root@android:/ # mount -o remount,ro /system
root@android:/ # exit
[Fire TV Original Android Development] rbox:
Well it has no effect on recovery, just the main system. It should do it every time. Not quite sure why you aren't seeing it though.
[Fire TV Original Android Development] AQKhanTheOne:
I did rename the downloaded file to bootmenu.img to avoid having to change the name in the shell command. Don't know if that makes a difference.
[Fire TV Original Android Development] rbox:
No, the name doesn't matter. Try this version. It should have a solid blue background to start and then if you hit the down arrow it'll switch to red. Blue will boot the kernel, red will boot recovery.

EDIT: Okay. I reread your post and saw you included the output from the shell. Don't copy paste it all at once. Do the commands one at a time.
[Fire TV Original Android Development] AQKhanTheOne:
Okay, that did the trick! Now I get the colorful Rbox's Boot Menu with two options, Boot Kernal and Boot to recovery.

Thanks as always for all your great work!
[Fire TV Original Android Development] o-I-c:
Well this looks like its going to be handy.

In with no issues Rbox and countdown

Idea: Press and hold key on the remote or keyboard to get to boot-menu (unsure if this can be done)

Press nothing boots to FTV

Thanks
[Fire TV Original Android Development] nhumber:
Works perfect here, the remote doesnt work tho right? need to use a keyboard?
[Fire TV Original Android Development] rbox:
Yeah. Just like recovery it needs the keyboard.
[Fire TV Original Android Development] cdsn99:
works great , thank you for all your efforts
[Fire TV Original Android Development] heyredy141:
Thanks a lot rbox. This works as described though I am not sure at this point what to do with it. I just installed it as you said it would be useful :)
[Fire TV Original Android Development] rbox:
My main goal with it was to always be able to get to recovery. Secondary goal is to easily use alternate kernels without risk of not being able to get back to recovery. Which really gets back to the main goal. A side effect is that people can load fedora kernels easy without having to screw around with their partitions.
[Fire TV Original Android Development] mastafunk:
Im trying to wrap my head around how this works.. I get what we are doing, but wont flashing something (ie anything with a boot.img) with CWM overwrite the bootmenu?
[Fire TV Original Android Development] rbox:
That's very much correct. I think I'm going to make all my future prerooted images put their boot.img in /system/boot and not flash it to the boot partition.
[Fire TV Original Android Development] mastafunk:
Thanks for your quick reply. Glad I'm on the same page .. I'm working on a custom ROM and was thinking that was something i would address the same way but then thought for a sec maybe you had moded the newer cwm to just do that instead of flashing the boot.img.

EDIT

might want to put some more thought into doing that for the newer pre-roots as someone may flash back to an older one then flash forward and screw themselves.. maybe include some sort of checking in cwm? And maybe include a warning in the OP if they flash any pre-root they loose the safetynet of the bootmenu.img until applied again.
[Fire TV Original Android Development] to0:
Worked great for me. Thanks rbox for all of the support you've given this device!
[Fire TV Original Android Development] ImCoKeMaN:
so I ran the first commands and it looks like I have boot.img in /system:

root@android:/system/boot # ls -l

ls -l

-rw------- root root 1675264 2014-11-21 18:19 boot.img

My concern is that I don't have any free space in system at all:

/system 756M 756M 0K 4096

is this normal to be this tight on the 51.1.4.0 prerooted rom?

I have even removed WhisperplayCore.apk when I was trying to get the chromecast receiver app working (sadly looks like that's fruitless at this point, but that's a separate topic)

I haven't copied the bootmenu image over just incase there is an issue with that boot.img that may not have been a full copy or something. Just trying to be extra careful.
[Fire TV Original Android Development] AFTVnews.com:
One tiny suggestion: Change the wording in your post "When flashing 51.1.4.0 or lower when using bootmenu, you must reflash bootmenu." to "When flashing 51.1.4.0 or lower when using bootmenu, you must repeat the entire bootmenu installation procedure."

The reason: After setting up bootmenu on my test device, I realized it was on 51.1.3.0 when I thought it was on 51.1.4.0. I installed 51.1.4.0 then re-read your note to "reflash bootmenu". I thought "ah simple, i'll just re-run the last dd step since everything is still in place." Of course, I forgot that installing 51.1.4.0 wiped out /system/boot/boot.img so when I put bootmenu in place I no longer had a stock boot image on the box. It was a simple fix (I just used bootmenu to get into recovery and reinstalled 51.1.4.0), but probably best to be explicit with the above sentence.
[Fire TV Original Android Development] rbox:
No, that's not normal. Are you sure you haven't modified it? You could try deleting the Freetime apk I suppose.

Ah, I'll update it.
[Fire TV Original Android Development] ImCoKeMaN:
Well I tried modifying it to run the cast receiver, but that isn't too big. I've had a previous stock image before. Is there any chance it added files to /system instead of flashing the whole partition? I'm not sure what the expected free space is. I've also had the xposed framework for google play store, but if I remember correctly the first thing I did after flashing the rooted image was try the cast receiver and it said I didn't have enough space. then I removed that apk instead of just renaming it.

clearly I can remove that since it's now useless, but I did want to know if it may be something else I should test for first, or reflash etc.
[Fire TV Original Android Development] rbox:
I would recommend flashing the bootmenu first, then flashing 51.1.4.1+fixed from recovery. That'll wipe /system and install the kernel in the proper location.
[Fire TV Original Android Development] qwertywarez:
rbox, I'm having a hell of a difficult time booting into recovery from either stock or CWM. It just sits on the white Amazon logo. I was thinking that flashing this new boot menu might fix that problem. I am currently rooted on 5.1.1.0.1 with CWM latest version. I just never was able to boot into recovery. What do you recommend? Should I attempt to flash this to try to fix the boot to recovery?

Thanks
[Fire TV Original Android Development] rbox:
As the OP states... you MUST verify you can boot recovery before even thinking about using bootmenu. If you can't boot into recovery you didn't install it properly and then installing bootmenu will brick your box.

Although your statement "I'm having a hell of a difficult time booting into recovery from either stock or CWM" makes no sense, because CWM is recovery. How can you not boot into recovery from recovery...
[Fire TV Original Android Development] qwertywarez:
What I meant was that reboot recovery hangs whether stock or CWM is installed. Flashing recovery seems to work though in adb.
[Fire TV Original Android Development] rbox:
Yeah. Dunno what you screwed up if stock recovery won't load.
[Fire TV Original Android Development] ImCoKeMaN:
I removed freetime.apk for the time being to copy the boot.img over just to test bootmenu works before the new flash, looks bigger now:

root@android:/system/boot # ls -l

ls -l

-rw------- root root 10485760 2014-11-22 16:45 boot.img

and I have 13mb free so I'm more comfortable. I'm about to test it and flash the new 51.1.4.1 now.

UPDATE: Flashed and working, the previous space issue was clearly from the cast receiver, not reinstalling as much as I'd love that functionality. Thanks for all your work and support rbox!
[Fire TV Original Android Development] jessenj:
Im stuck but not where everyone else is. My unit boots to the Rbox's Boot Menu screen, shows me both options to boot kernel and launch recovery, and the timer counts down from 5 to 0, but when it reaches 0, it just hangs there. I only have the keyboard installed, and I had just installed completely all the needed steps to update from the last version of CWM to the latest "a" version. What do you think I can do at this point? It's just doing the countdown and then nothing.

Actually - I wanted to update this. I was able to get to the Recovery option, it's the booting into Kernel option, so I put the latest custom rom zip on a usb drive, and as long as I booted with just the keyboard connected to the usb hub, CWM loads fine, and then I was able to pop my usb drive into another port and CWM recognized it as a storage device, so now I'm installing the latest custom zip and will say a little prayer in the meantime.

---------- Post added at 03:42 PM ---------- Previous post was at 03:27 PM ----------

Well - I answered my own question. The install from zip on usb drive WORKED LIKE A CHARM and now I'm getting the system to install the updates. I figured rather than delete this, I'll leave it here in case anyone else has the same issue.
[Fire TV Original Android Development] mroneeyedboh:
That happened to me. I needed to flash his boot menu and then boot to recovery then mount and copy over the new FW. Flash that, then it worked.

The new FW tells the boot menu where the kernel is or something...
[Fire TV Original Android Development] mastermind278:
I am having an almost similar situation. The timer counts down to 0 and I am stuck there. I also have a keyboard installed, however it will not enter the boot kernel or launch recovery. It actually doesn't let me do anything from this screen. I have tried 2 different keyboards. They are working as the CTRL ALT DELETE triggers a reboot. I know the the latest version of CWM was installed. Not really sure how to proceed.

Edit: Apparently I got it working now. Not exactly sure what was wrong but it's up and running. Yesterday when I was triggering the recovery at boot via the ALT PrntScreen i it didn't actually boot recovery, but somehow later it did? After doing that it allowed for movement on the boot menu, but at that point I just loaded 4.0 to remove boot menu. Then flashed boot menu again and everything was working.

I've done a few boxes for family and friends and never had this issue, glad it decided to fix itself one way or another.
[Fire TV Original Android Development] Y314K:
[MENTION=3991724]rbox[/MENTION] Can we do a Factory Reset with all this stuff install without loosing/bricking things... Unlock Bootlooader / BootMenu / Latest PreRooted FW ??
[Fire TV Original Android Development] rbox:
Yes.
[Fire TV Original Android Development] Tenny:
It looks like I'm stuck on this one...

I have 51.1.0.1 installed.

I have CWM 6.0.5.1.4a installed

Now I just installed this boot menu, and it gets to the selection screen. Unfortunately I have tried three different keyboards and none of them seem to be working at all for me. I cannot move the item down to "Launch Recovery" to install 51.1.4.1.

They keyboards at least slightly work as when I press ctrl-alt-delete it does reboot the FireTV. Although that's about all I can do at this point. It obviously won't boot (as it's running 51.1.0.1) and I can't select recovery.

ADB won't connect (didn't think it would, but it was worth a shot).

Any suggestions?

EDIT:

Duh, not sure what it was but after enough alt control deletes and alt i prt screens the keyboard starting working... So if you get stuck in the same spot maybe try those two combos (it seemed the later was the better one).
[Fire TV Original Android Development] rbox:
If you had followed the instructions it would have no problem booting 51.1.0.1... Are you sure you are pressing the correct arrow keys?

Using the sysrq trick enough times would probably trigger it to go in to recovery.
[Fire TV Original Android Development] philo_enyce:
bricked it...

sorry to be the chowderhead who posts this, but i'm hoping against hope that i'm not boned here.

i managed to get the boot menu installed prior to getting cwm installed. i was using imtiaj meah's firetv utility app and did the steps out of order. when the firetv boots it gets to the rbox boot menu, but won't boot the kernel, it just sits there and if i try and launch recovery, i get the amazon system update unsuccessful screen. is there any way of getting around this?
[Fire TV Original Android Development] philo_enyce:
any chance the USB can be used to receive adb commands? i can get to the android system recovery menu as described here - http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/ - but don't have the right usb cable to connect from my computer. i tried to use my nexus 5, but don't know how to get the usb into the right mode to connect to the firetv, if i do an adb devices command nothing is listed.
[Fire TV Original Android Development] rbox:
The Fire TV doesn't support ADB over USB.
[Fire TV Original Android Development] philo_enyce:
och, so i'm truly boned then :(

thanks for your reply.
[Fire TV Original Android Development] vampypang:
Hrm... My FireTV also loads the rbox boot menu, and won't boot the kernel (it just sits there) and launch recovery will return with the amazon system update not successful screen. Any luck with your FireTV?
[Fire TV Original Android Development] vampypang:
I've made some progress... after much persistence of "launching recovering" then pressing (Alt + Prt Sc + i) to reboot it again, then pressing the HOME key, I now have the "Android System Recovery" loaded... I'm now not sure what to do next! Factory reset didn't do much, and I'm not sure how to connect to the firetv when using the "apply update from ADB"... Any tips?
[Fire TV Original Android Development] philo_enyce:
sadly no. got a new one and ran through the process successfully this time.
[Fire TV Original Android Development] bula1ca:
Reinstall bueller-51.1.4.0_514006420-rooted+updated, it will remove Boot Menu and you can start fresh. I installed boot menu manually on all my boxes however on the last one I did for a friend I tried to install it using FireTv Utility (could had been an user error) and I ended up with system not being able to boot up, fortunately boot menu saved me.
[Fire TV Original Android Development] hotterpop:
Just installed this- absolutely no issues. Thanks for the great work! Love the graphic too- reminded me of Banjo Kazooie.
[Fire TV Original Android Development] rbox:
Thanks :) Someone was complaining about the Comic Sans... but if everyone stops using Comic Sans, it'll be as if it never existed...
[Fire TV Original Android Development] hotterpop:
Also, I don't want to sound like too much of a fanboy here, but being able to use my laptop to control the recovery without having to go dig up my keyboard was a magical experience.
[Fire TV Original Android Development] Y314K:
What did you use.. FireTV Utility's Virtual Keyboard ? or FireTV Utility to go directly into CWM & then http://www.aftvnews.com/how-to-remotely-control-clockworkmod-on-the-amazon-fire-tv-using-adb/ ???