If you want to offer help PLEASE read through the thread, or at least the initial post. It seems like I'm repeatedly answering the same questions that were already answered.
I've tried to boot in APX and all I get is the black screen, yet neither Windows 7 64bit/Linux Mint 64 on one PC and Windows XP on another don't detect it at all. I know the cable works because when I had CWM installed I could see it attached via ADB. I'm a b30
Edit: I managed to get the stock ROM back on it, but it still doesn't want to boot into the bootloader/APX mode. I know it's not necessary but I would like to have it as a failsafe for the future.
brando56894 said:
This all started with me wanting to go back from AOKP to stock, I flashed a rooted version of 9.2.1.17 and it kept telling me to update, but when I did it failed because CWM was installed. It also wiped my system. I found 9.2.1.24 but couldn't flash it because TWRP wouldn't stick. I tried to install the stock recovery, which worked in a sense that it removed CWM but left me with just the Android and the exclamation point (I can't seem to get past that no matter what I do [vol +, Vol -, power or any combination of those] ) I decided to use NVflash to get back to complete stock and start over.... The only problem is that Windows 7 doesn't even detect the TF when its in APX mode, hence it doesn't ask me to install the drivers, nor will they install manually.
So my TF is soft bricked and nothing works. I'm going to reboot into Linux now to see if I can get nvflash working. Any other suggestions?
Edit: Linux Mint didn't detect it either I know it's not the cable since I was able to see the TF via ADB when I had CWM installed. Also the major thing that is worrying me is will the TF be recoverable if the battery dies? I have no way of knowing if it is actually off or just in APX mode, I obviously can't do a battery pull and I can't power it down from the recovery or the OS. IIRC it also won't charge when it is in recovery and I'm assuming the same is true for boot-up and APX mode.
Click to expand...
Click to collapse
Same to me-- win7 does not recognize my tf 101- apx is installed-works with another transformer well- if i do vol down and then vol up i see the laying android with exclamation mark.
no solution till now- hope you had more luck-
By the way- try to load it normal - in my case it works.
kind regards
gandalf
I just tried connecting it to an older Dell with a P4 in it and it doesn't detect it either, it just seems like the TF doesn't want to boot into APX mode. I'm doing Vol + and Power from both the recovery and from the initial splash screen, then it reboots to a black screen which I'm assuming is APX mode. From the black screen I've tried Vol + and Power for as long as 30 seconds and still nothing. There were also times when it would sit at the initial splashscreen and then go to a black screen, then I'd try to enter APX mode from there but it would be the same thing.
I've been contemplating getting a Nexus 7, partially because I lightly stepped on the screen of my TF one night and damaged it enough to cause the LCD crystals to break (there about two or three grayish "lines" where I stepped on it) but not hard enough to crack the glass. The screen will also flicker some times on that side and will also randomly shut the screen off. Maybe this is a sign telling me to get a N7?
Do you have debug mode enabled?
Where did you get the win 7 APX mode software. Some links in this site are to defective software. Go to the SDK kit site and download the software there. http://developer.android.com/sdk/index.html
Rumbleweed said:
Do you have debug mode enabled?
Where did you get the win 7 APX mode software. Some links in this site are to defective software. Go to the SDK kit site and download the software there. http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
Debug mode is for ADB, not APX. Debug mode is set in Android and with APX no Android is loaded.
I have used the live cd of Ubuntu 11.10 without installing any driver by myself. It recognized the TF with APX in my case.
There is no debug mode considering that the OS isn't installed. AFAIK debug mode is only necessary to use ADB while booted into Android. APX is something that is built in to the device. I downloaded the drivers from android.mobi which has an "unroot/unbrick" package, that doesn't matter though because Windows never asks me to install the driver so the drivers don't seem to be the problem, considering Linux (which doesn't require any drivers) doesn't see the device either.
I had the same, downloaded the drivers, but couldn't install.
After I made sure I had the correct drivers, I clicked in hardware settings on the thingy with the exclamation point, I choose manual search and had Windows search the entire c:\ drive, after a while it installed
Sent from my Transformer TF101 using xda premium
That's my problem guys. APX mode/unknown device doesn't show up in device manager
oi, than I cant help you, sorry
I think it's F'ed because I took it apart to make sure it was turned off by disconnecting the battery and then did the power and Vol+ combo but the PC still doesn't detect it.
1. your battary is empty, charge it
2. your battary is done.
3. your power key or vol-up key do not work.
4. you did not press two keys in the same time long enough
5. cable doesn't work
6. usb port doesn't work, try another one.
7. you did not pay attention on the sound of device connected nor the device list.
8. your windows broke. try another pc.
---------- Post added at 11:39 PM ---------- Previous post was at 11:33 PM ----------
get a micro sd and copy rom to it and flash, since you said cwm works ok
vista1984 said:
1. your battary is empty, charge it
2. your battary is done.
3. your power key or vol-up key do not work.
4. you did not press two keys in the same time long enough
5. cable doesn't work
6. usb port doesn't work, try another one.
7. you did not pay attention on the sound of device connected nor the device list.
8. your windows broke. try another pc.
---------- Post added at 11:39 PM ---------- Previous post was at 11:33 PM ----------
get a micro sd and copy rom to it and flash, since you said cwm works ok
Click to expand...
Click to collapse
1 & 2 It boots up to the initial splash screen and to the android recovery so the battery is ok
3. The Vol + does work unless it suddenly died because I was using it moments before I bricked it
4. I would say 30+ seconds is long enough
5. The cable does work because it charges the unit and when I had CWM installed I could see it via ADB
6. Tried another port, nothing
7. The sound is definitely noticeable and it's kind of obvious if it's not in the device manager list
8. I tired two different computers, and three different operating systems. Including Linux.
I know you are trying to be helpful but ALL of these were answered in previous posts, if not the OP.
I'm having the same issue with my pad not booting into APX, might I ask how you got the stock ROM back on it without APX?
Luckily I had the stock recovery installed and I was able to place the OTA on A MicroSD card and named it so that it would flash automatically once I booted into the recovery.
Sent from my Transformer TF101 using Tapatalk 2
Edit: here's how to do it
baseballfanz said:
Download the latest official firmware from Asus.
Extract the zip from within and rename it to "EP101_SDUPDATE.zip" (without the"" )
Put it on the root of your sdcard
Boot into stock recovery and it should flash it
Click to expand...
Click to collapse
I have to go with #5. My Transformer would charge when using my cord and so I thought it was good. Plugged it into the computer and nothing. Switch to my wife's cord and the computer saw it instantly. It was then able to see APX mode.
Yea it was actually the cord being stupid, when I got back to my house I tried my other cord and it connected just fine. I actually just sold my TF yesterday to a friend for $250 so that I can get a Nexus 7
Sent from my ADR6425LVW using Tapatalk 2
So this is making me thing that my cord is the issue, but I tried 3 different cords and none of them recognized. Is it possible the device itself has a faulty connection?
It's entirely possible, have you tried a different computer/different USB ports first though?
Tried every port on two machines as well as in linux. My HTC G2 connects just fine to everything.
You may be screwed Do you have the dock? Does it connect and charge fine with that?
Related
Okay im running windows xp, and i have all those drivers installed...
http://www.userdrivers.com/PDA-Mobil...dows-XP-Vista/
and http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
so what am i missing to get my vibrant to be recognised by odin in download mode????
What are you running currently?
simply honey 3.6..... gingerbread
By chance did you forget to enable usb debugging?
idk, i flashed from a 2.2.1 rom to simply honey 3.6 through rom manager, but i did have it enabled through before i flashed for sure.... And usb debugging is not required for download mode as (i think) thats a whole different thing???
It needs to be enabled to use Odin. Also, sometimes for Odin to see my phone I have to unplug my phone and open Odin a few times before I finally get Odin to see my phone. It's very finicky for me, always has been
Sent from my SGH-T959 using XDA Premium App
helikido said:
Okay im running windows xp, and i have all those drivers installed...
http://www.userdrivers.com/PDA-Mobil...dows-XP-Vista/
and http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
so what am i missing to get my vibrant to be recognised by odin in download mode????
Click to expand...
Click to collapse
Go into windows device manager. Make sure that your computer is even seeing the device and that it has recognized the drivers for it. If it recognizes it, try rebooting computer then restart the process. Also make sure your phone is actually in DOWNLOAD mode. Not Recovery mode.
If you do not know the difference between the two, let us now and we'll assist further.
Happy hacking!
I use to always have trouble with Odin..then one day someone mentioned they always right clicked on Odin and chose "run as Administrator", I have never done that because I figured I was the administrator....but once I did it, never had a problem since.
Another problem I run into (well not anymore) is the USB port I plugged into. If I was on a hub or something it wouldn't work. If I plug right into my computer it works properly.
I also use adb commands to get into download and recovery when I'm Odin'ing. It also let's me know if my phone is detected by the OS.
#adb devices (should show your phone listed)
#adb reboot download (reboots your phone into download mode)
#adb reboot recovery (reboots your phone into recovery mode)
You'll need the SDK installed for adb to work.
Since I started doing these things, I have had ZERO problems with Odin and flashing my phone.
ay.. usb debuging was enabled before i flashed... now if my turn turns on it goee onto a bootloop... so everytime i cinnect my phone to the computer it says device not recognised. ohh and one thing to mention is that my computer doesnt have a highspeed usb port
Three button to download mode - power+vol up+vol down and see if you can get it into download mode then plug in usb (1.0 should work), then run odin...
otherwise i think you're looking at trying to make one of those jigs or replacing your phone...
try
1. Start Odin
2. Plug USB cable into pc
3. Power off the Phone.
3. Pull the Battery.
5. Plug USB cable into Phone.
6. Press and Hold: Volume UP + Volume DOWN + Power, all at the same time.
7. Re-insert the battery.
8. The phone will power now, when the screen starts a cycle of going to a BLACK screen, release ONLY the POWER button.
9. When you see the download icon release the volume buttons,
10. Odin back to stock by putting the PIT file into the appropriate area and the .tar in the PDA area.
Afaik the three button combo is for
Recovery mode. Follow the above directions up to the power button part. While holding both volume buttons, it should go directly into download mode when the usb us plugged in
Try removing all drivers then reinstall if xp doesn't pick it up
Beware of angry gingerbread man
power off phone
pull out battery
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
Enjoy and also make sure u have the proper samsung drivers
Install samsung kies mini. It gives you the correct drivers. I once installed those and it messed it up. So install kies mini.
adamcooks said:
Afaik the three button combo is for
Recovery mode. Follow the above directions up to the power button part. While holding both volume buttons, it should go directly into download mode when the usb us plugged in
Try removing all drivers then reinstall if xp doesn't pick it up
Beware of angry gingerbread man
Click to expand...
Click to collapse
This is what happens when you do it a certain way for a long time, you forget certain things...lol
try another computer?
goodluck
Hi,
I. Have gotten myself into quit a frustrating situation. My nexus 7 was unlocked, rooted and had several different custom roms installed at various times and had never had a problem. But then one time in particular, when trying to flash a rom (which I can't even remember which one it was,) after the rom had "successfully" been flashed, it rebooted to the splash screen, which it stayed at for a very long time; before just turning into a series of flashing vertical lines that never end. I can use the power+vol- method to get to fastboot, but not recovery; it would appear that my recovery has been wiped as I get the same google splash screen loop as when I try to boot. My problem is that nothing I do allows me to successfully connect the device to my pc (w7, 32bit.)
I have uninstalled any conflicting drivers, un/re-installed the proper drivers from like 7 different guides, I have also tried two different nexus root toolkits. I even tried to use a Linux machine to no avail. I have switched USB cables, everything I have tried has not worked. This is by no means my first foray into android devices, I even freshly installed my android SDK and still my computer just fails to recognize the nexus 7 in fastboot mode.
Any tips or advice would be a godsend. Thanks.
This sounds like a issue a few people have been having.. As far as i know as of a week ago there is no solution . You need to flash the boot-loader it sounds like. There is a thread about this. Search for NV FLASH .. OR APX MODE. Sorry for being lazy and not looking for the thread for you..
They may have some things in that thread that you have not tried.
Turn your Nexus off and plug it into your computer. Does your Nexus start charging? A completely bricked Nexus wouldn't charge. If it starts charging, then try turning it on into Fastboot mode.
Sorry, I'm no dev. Just a random thought to try. But if your Nexus can charge you shouldn't be fully bricked, hopefully. At least this is what I think.
When you say your computer fails to recognise the device...
If you open your device manager in Windows and then plug in the nexus 7 in fastboot mode, what happens? Does it show up in the device manager in any category? Even with a yellow exclamation mark or as unknown device?
Sent from my Nexus 7 using Tapatalk 2
My bro bricked his N7
He was rooted and unlocked, flashed a rom now it bootloops on the logo. Now when doing adb devices, it doesnt detect the device when in bootloader, went to device manager and shows problem with driver. Tried other drivers but says its up to date. Thing is I just upgared his friends N7 with the same drivers so I know thats not a problem.
It wont go into recovery either. Now when it is bootlooping, the decive is recognised when doing adb devices. So can I flash a factory image when it is bootlooping or does it have to be in fastboot?
TRY THIS
from powered down,
hold VOL- and POWER for ten seconds,. then let go of POWER and still hold down VOL-
dramdrum said:
When you say your computer fails to recognise the device...
If you open your device manager in Windows and then plug in the nexus 7 in fastboot mode, what happens? Does it show up in the device manager in any category? Even with a yellow exclamation mark or as unknown device?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
it doesn't even acknowledge that I plugged anything in to the computer at all.
chismay said:
TRY THIS
from powered down,
hold VOL- and POWER for ten seconds,. then let go of POWER and still hold down VOL-
Click to expand...
Click to collapse
Just goes to bootloader?
Edit seems to be working now even though when doing adb devices in fastboot it doesnt list the device id
In fatboot mode you don't have adb access - down load a recovery image and name recovery.img
Hold shift and right click in the folder recovery.img is in
Choose open command here, in cmd type
fastboot devices
If you see your serial number proceed
fastboot flash recovery recovery.img
When finished reboot to recovery and flash rom of choice
ps, you have had to either change your path in enviromental variables to include platform-tools from the sdk or have both fastboot.exe and recovery.img in the same folder that cmd is pointed to
Sent from my HTC Vision using xda premium
I have tried many options. My Nexus died shortly after a KitKat update, but it may have been frazzled by a faulty car charger.
Cannot access recovery mode.
Cannot get PC to see ADB device
Would replacing the USB board help?
Out of warranty so willing to try almost anything.
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
xateeq said:
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, I was only ever stock. Unrooted, but had USB debugging.
I sideloaded KitKat when it came out and installed the Google Experience launcher. Received an OTA a day later that was only 1-2Mb.
The sideloading worked perfectly using the adb sideload kitkat.zip.
The evening after the OTA and the unit died. It is possible that it was a car charger, but I think highly unlikely as it never affected a Kindle or Xperia Z. But now I cannot get the PC to even see that the device is connected and neither can I get Recovery Mode to fully start. I select Recovery Mode and all I see is the Google logo. I have tried all sorts of button presses to get the android on its back with the red triangle. I may have missed something obvious so any suggestions would be a help.
Connect to wall charger if u cant get it to charge then it is ok,
try changing ur data cable that ur using to connect it to pc.
if ur tablet was not connected to charger when it dies then it is not the carger. OTA usually mess things up on modified/ rooted devices.
Hi, Thanks for the response.
I've tried all my cables. I can get the unit to charge no problem. It is just that I cannot get it to recover itself.
Powering on freezes on the Google logo and the CPU overheats like a really good overheating thing.
I go into the bootloader and if it doesn't freeze I can select all the various top level options. I have tried selecting Recovery mode and I cannot get that to work either. If I select Recovery mode and hit the power button it once again freezes on the Google logo. I have tried holding the volume up and pressing the power, but nothing happens. The only option I have is to power off again.
I had hoped that the nexus Root toolkit would help, but as it is never seen or recognized by the laptop I think I am totally screwed. I am thinking that my best hope is to sell it for spares. Unless there is a way of resetting the machine without a computer or being able to access recovery mode. I haven't seen anything like this.
I own an LG G2, i recently got this phone yesterday from a person on craiglist. Don't worry i didn't pay him i gave him my older phone i dont use anymore. SO This phone is practically stuck in Firmware Update (As i read that post) , i spent about a day and half figuring it out and what happens is that.
I CAN get into recovery its TWRP v2.7.0.0 by Turning off the phone first and then Holding Vol UP, Power, Vol Down at the same time until the LG Logo comes up and then i am still holding them down, and it says Recovery Mode please wait and bam TWRP.
But heres the problem i can't mount my OTG and i can't ADB Sideload. So what do i do from here?? this guy rooted this phone and soft bricked it i think? and he wiped the phone but i also did when i had the chance and wiped it completly via recovery.
The only way i got into "Download Mode" / "Firmware Update" was to take the back cover off and unscrew a few screws on the side and unclip the battery for a few seconds and then plugged it back in and then I held the VOl UP button and plugged my USB into the phone and the other end is in my PC. My phone says "Download Mode please wait" and then prompted with the Firmware Update screen. BUT my pc doesnt detect the phone whatso ever and i've already installed drivers and etc from this forum ( http://forum.xda-developers.com/showthread.php?t=2432476 ) its the 2015 method that i downloaded.
so what do i have to do, i havent tried using different usb cables, the port seems fine to be plugged in since in TWRP it says 84+ so i meant its charging right? help me out guys idk what else to do or flash or anything.
IAmTechFreq said:
I own an LG G2, i recently got this phone yesterday from a person on craiglist. Don't worry i didn't pay him i gave him my older phone i dont use anymore. SO This phone is practically stuck in Firmware Update (As i read that post) , i spent about a day and half figuring it out and what happens is that.
I CAN get into recovery its TWRP v2.7.0.0 by Turning off the phone first and then Holding Vol UP, Power, Vol Down at the same time until the LG Logo comes up and then i am still holding them down, and it says Recovery Mode please wait and bam TWRP.
But heres the problem i can't mount my OTG and i can't ADB Sideload. So what do i do from here?? this guy rooted this phone and soft bricked it i think? and he wiped the phone but i also did when i had the chance and wiped it completly via recovery.
The only way i got into "Download Mode" / "Firmware Update" was to take the back cover off and unscrew a few screws on the side and unclip the battery for a few seconds and then plugged it back in and then I held the VOl UP button and plugged my USB into the phone and the other end is in my PC. My phone says "Download Mode please wait" and then prompted with the Firmware Update screen. BUT my pc doesnt detect the phone whatso ever and i've already installed drivers and etc from this forum ( http://forum.xda-developers.com/showthread.php?t=2432476 ) its the 2015 method that i downloaded.
so what do i have to do, i havent tried using different usb cables, the port seems fine to be plugged in since in TWRP it says 84+ so i meant its charging right? help me out guys idk what else to do or flash or anything.
Click to expand...
Click to collapse
I think the methods leave out that you need to change your phone to com port 41 on device manager > ports in order to be detected. Then you need to unplug it and reconnect to computer when the program shows waiting for device, with the phone in download mode already.
Also, to get to recovery you hold vol down and power, when the LG logo comes up release power and hold it again until the reset screen comes up.
To get to download mode you turn the phone off then hold up while plugging the USB cord in with it connected to pc... This launches download mode.
Sent from my LG-VS980 using XDA Free mobile app
Yoinx said:
I think the methods leave out that you need to change your phone to com port 41 on device manager > ports in order to be detected. Then you need to unplug it and reconnect to computer when the program shows waiting for device, with the phone in download mode already.
Also, to get to recovery you hold vol down and power, when the LG logo comes up release power and hold it again until the reset screen comes up.
To get to download mode you turn the phone off then hold up while plugging the USB cord in with it connected to pc... This launches download mode.
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
Well you see man , I cant change anything in Device Manager since my phone isn't being detected. It didn't install drivers fully fully since my phone isnt recognized. Even in TWRP or "Download Mode/ Firmware Update" Nothing happens no drivers installing or anything even but it does boot it up to that point....and its just normal boot up i see the LG logo and my led goes from green to blueish in a smooth transition and it doesnt stop until i turn it off. The method i got into recovery is holding all those buttons down its not a problem for me to get into it. I also have another problem it doesn't seem to want to mount my usb otg by samsung.
what do i do
So i tried the otg route but I can't mount it. I have everything connected and once I go into recovery to mount usb-otg, nothing happens.
I just need some way to get a ROM.zip in my phone
Computer does not recognize my phone.
Stuck at LG logo unless I enter recovery.
Sideload doesnt work.
OTG doesnt work.
I've tried at least 4 different guides with no luck.
Why don't you manually install drivers from online?
ive tried
tzzeri said:
Why don't you manually install drivers from online?
Click to expand...
Click to collapse
ive tried that already and it doesnt list anything from the LG folder.
I realized the phone will say start the adb sideload feature. so, when i put the "abd sideload file.zip" command on my pc i just wait a few minutes and it says daemon not running on port 5037 and then start successfuly and then error :device not found.
it can seem to reognize my device wether its in recovery, or download mode or fastboot mode.
Try again in other pc that has never been conected to an LG Phone before. It can perfectly be a conflict with drivers installed in the OS.
I've tried man
AFter i cleaned the usb port in one of the chats or forums, i waited a day ovbiously without turning on the phone and cleaned the usb port with alchohal and a q tip and i plugged my phone into my computer and my PC detected something but it only says "Unknown Device" everytime no matter what pc i use it says that. nothing else. but before that none of my pcs would detect theirs a phone plugged in at all.
IAmTechFreq said:
AFter i cleaned the usb port in one of the chats or forums, i waited a day ovbiously without turning on the phone and cleaned the usb port with alchohal and a q tip and i plugged my phone into my computer and my PC detected something but it only says "Unknown Device" everytime no matter what pc i use it says that. nothing else. but before that none of my pcs would detect theirs a phone plugged in at all.
Click to expand...
Click to collapse
Might be a problem with the cord
Sent from my Motorola DynaTAC using XDA Free mobile app
tzzeri said:
Might be a problem with the cord
Sent from my Motorola DynaTAC using XDA Free mobile app
Click to expand...
Click to collapse
No there is no problem with your USB cord or port. You need to do following steps.
http://forum.xda-developers.com/showthread.php?t=2432476
https://www.youtube.com/watch?feature=youtu.be&v=g01Pa7cgdSM&app=desktop
Please let me know if you succeed.
All credit goes to #bender_007
Hey gents,
Received my unit today which has the dreaded boot loop,
I can get onto a screen with my usb a cable mentioning something about an os.
Windows finds it (xp) i have got some drivers from modaco root zip which is and and fast boot.
Tried both drivers ,
Mad catz is found but can't use any commands get failed when i try following the root procedure.
I tried pressing the buttons to get into recovery as well but I just have a black screen no writing at all and the blue led doesn't load up.
Window cannot find the driver and has usb default but the drivers i used earlier won't work.
Any help ?
Can you get into TWRP recovery following the guides? You should have no problem once installed. Try this guide here if no OS is installed.
I had bootloop before and managed to recover easily but I used Linux. It looks like a similar method all told though.
Managed to get cmd to send files to the mojo but my screen doesn't change
K-Project said:
Can you get into TWRP recovery following the guides? You should have no problem once installed. Try this guide here if no OS is installed.
I had bootloop before and managed to recover easily but I used Linux. It looks like a similar method all told though.
Click to expand...
Click to collapse
I have fast boot now but no adb
All I can say to my friend is you will have to read thoroughly the guides around here. Have you read this one thoroughly? It says you must remove the USB cable when it says booting OS. This is typically the thing that catches many out. You need to make sure all your files are in place on the SD card once you get to recovery. In all honesty it has been a while since I did this but I used Linux and can flash one of these in seconds. If you're getting the "booting OS" message then the machine is NOT BRICKED and is recoverable.
---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------
From here in bold:
Download the Superboot zip file above and extract to a directory
Put your device in bootloader mode - Unplug the power cable and any USB cables (the dongle can stay in), insert the USB Male A-A cable in the port labelled '2.0', then insert the power cable. 'Key driver not found.. Booting OS' will appear on screen.
WINDOWS - install the device drivers from the directory you extracted above if required, then run 'superboot-windows.bat' as Administrator
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by 'sudo ./superboot-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by 'sudo ./superboot-linux.sh'
You will see 'Booting downloaded image' and a black screen, then the screen will return to 'Key driver not found.. Booting OS'. At this point, unplug the USB cable and the power cable, wait a few moments, then reconnect the power cable to boot as normal.
You are using this method to install TWRP recovery, which will then allow you to install your choice of OS. Read, read, read everything you can. I know how it is because I spent a whole long weekend at this over last Easter. It's a drag at first but great once you figure it out.
K-Project said:
All I can say to my friend is you will have to read thoroughly the guides around here. Have you read this one thoroughly? It says you must remove the USB cable when it says booting OS. This is typically the thing that catches many out. You need to make sure all your files are in place on the SD card once you get to recovery. In all honesty it has been a while since I did this but I used Linux and can flash one of these in seconds. If you're getting the "booting OS" message then the machine is NOT BRICKED and is recoverable.
---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------
From here in bold:
Download the Superboot zip file above and extract to a directory
Put your device in bootloader mode - Unplug the power cable and any USB cables (the dongle can stay in), insert the USB Male A-A cable in the port labelled '2.0', then insert the power cable. 'Key driver not found.. Booting OS' will appear on screen.
WINDOWS - install the device drivers from the directory you extracted above if required, then run 'superboot-windows.bat' as Administrator
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by 'sudo ./superboot-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by 'sudo ./superboot-linux.sh'
You will see 'Booting downloaded image' and a black screen, then the screen will return to 'Key driver not found.. Booting OS'. At this point, unplug the USB cable and the power cable, wait a few moments, then reconnect the power cable to boot as normal.
You are using this method to install TWRP recovery, which will then allow you to install your choice of OS. Read, read, read everything you can. I know how it is because I spent a whole long weekend at this over last Easter. It's a drag at first but great once you figure it out.
Click to expand...
Click to collapse
Done exactly what you wrote and i just get this boot loop again
Right currently installing android tv whoop
Followed the Russian site 4pda they have a good write up
Basically i just had two commands
So downloaded openrecovery and then fastbooted to open recovery .
Android TV launcher stayed in boot loop but cm 12.1 is working great
Excellent! Glad you got it going. Yes it's effectively two commands really, but you have to have everything in place.
You're getting a bootloop on Android TV, but my understanding is that will disappear once you flash the SuperSu zip. But if you're good with CM 12.1 I'd stick with that. I never tried Android TV since CM 12.1 did everything I need.
Have you flashed your GApps? I'd go for the nano set.
Yes i flashed gapps but fancied trying android TV again basically you don't flash root when asked i don't think you can root android TV without bricking.
I have a different launcher on it now by chain fire halauncher and kodi running.
I've yet to put emulators on it.
Controller is not the best for android TV to be fair constantly switching modes....
Quick question can the controller pair to a smartphone without the dongle.
As I've tried holding start down for five seconds it goes purple than flashes blue and red but my phone can't find it
sutty86 said:
Yes i flashed gapps but fancied trying android TV again basically you don't flash root when asked i don't think you can root android TV without bricking.
I have a different launcher on it now by chain fire halauncher and kodi running.
I've yet to put emulators on it.
Controller is not the best for android TV to be fair constantly switching modes....
Quick question can the controller pair to a smartphone without the dongle.
As I've tried holding start down for five seconds it goes purple than flashes blue and red but my phone can't find it
Click to expand...
Click to collapse
I'm sure someone round here said you could but it wasn't worth it as performance wasn't so good. The retail one doesn't need a dongle fwiw, and connects to the phone just fine.
Yeah, with CM 12.1 I've managed to minimise mode switching on the pad as it is as you say a bit of a pain. I only switch to mouse mode when using Google Play or shutting down the system. Other than that I occasionally swipe apps away by double tapping the Home button, and that needs mouse mode. Otherwise all emulator, game and KODI use is via the pad mode.