It's finally here! TWRP recovery for the FireTV Stick. Most likely, I will not be updating this thread with new releases, as the prerooted ROMs will always contain the latest version. This thread is just here so people can initially get TWRP installed.
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, but doing stupid things with it might.
The Stick is much harder to recover from than an unlocked Fire TV 1 or a Fire TV 2 that can run preloader commands. Please be very wary of the instructions!
Installing this requires root. If you are not rooted, figure that out first.
Installation
This requires that you are rooted.
Copy the montoya_recovery_vX.zip file to /sdcard
From within adb shell, use su to become root, and run this command (replace vX with the actual version you downloaded)
Code:
sh /data/media/0/montoya_recovery_vX.zip
Reboot
Notes
This includes bootmenu. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. For the time being, it does not support USB keyboards, so you will need to use the mouse emulator in adb to interact with it. To get adb, just plug the stick in to your computer. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
For the time being, there is no wifi, although I have explored it and it is possible, just need to work out some details.
To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions. Sliders don't require sliding, so you can just hit enter/click on them.
Installing zips
You can push zips to /sdcard or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
Source Code
You can find the source code here:
https://github.com/androidrbox/firetv-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
Finally, thanks to everyone who has donated to me.
Changelog and Downloads:
December 18, 2016 - v1 (md5sum: bd69911e9eeb37d9d6ebafe5302db5fe)
Awesome work!
Dont want to seem stupid here but i cant make out how im supposed to select recovery from the boot menu.
I have just recently re installed my windows system and im quite sure i have adb installed correctly but cant seem to connect to the stick (with usb).
thanks for any pointers.
sconnyuk said:
Dont want to seem stupid here but i cant make out how im supposed to select recovery from the boot menu.
I have just recently re installed my windows system and im quite sure i have adb installed correctly but cant seem to connect to the stick (with usb).
thanks for any pointers.
Click to expand...
Click to collapse
Does adb work while the stick is booted? For windows, you have to screw around with drivers. Otherwise, get a real OS, and then it "just works".
rbox said:
Does adb work while the stick is booted? For windows, you have to screw around with drivers. Otherwise, get a real OS, and then it "just works".
Click to expand...
Click to collapse
No its not working while windows is booted either, I do suspect its adb driver issues but for the life of me cant find the drivers I had and used previously.
Im now using Windows 7 64bit as I downgraded from windows 10 64bit as its rubbish.
So from my understanding while its booting and on the selection screen I will open cmd and ADB connect through usb to the stick and then use the virtual abd mouse?
If so can you elaborate on how the mouse is launched?
If I get chance later im going to try find the correct driver I need (ill search and try numerous drivers I have to hit the correct one after a while)
Thanks for the pointers
sconnyuk said:
No its not working while windows is booted either, I do suspect its adb driver issues but for the life of me cant find the drivers I had and used previously.
Im now using Windows 7 64bit as I downgraded from windows 10 64bit as its rubbish.
So from my understanding while its booting and on the selection screen I will open cmd and ADB connect through usb to the stick and then use the virtual abd mouse?
If so can you elaborate on how the mouse is launched?
If I get chance later im going to try find the correct driver I need (ill search and try numerous drivers I have to hit the correct one after a while)
Thanks for the pointers
Click to expand...
Click to collapse
While the bootmenu is showing, just type 'adb shell' then at the shell type 'mouse'.
So i now found the correct drivers and it now connects to Firestick while its booted up but will not connect when Firestick is booting on the Recovery menu, any ideas ? thanks
sconnyuk said:
So i now found the correct drivers and it now connects to Firestick while its booted up but will not connect when Firestick is booting on the Recovery menu, any ideas ? thanks
Click to expand...
Click to collapse
It's possible the device id is different while in bootmenu vs when it's booted. I can take a look tonight.
rbox said:
It's possible the device id is different while in bootmenu vs when it's booted. I can take a look tonight.
Click to expand...
Click to collapse
Excellent.
If I get it up and running I will post how I managed it.
Is it possible to root Fire Tv Stick gen 1 on 5.2.1.1 or the New Fire Tv Stick Gen 2. That would be sweet and Do you think its safe to use Xposed on fire tv stick 1. I want to install Google Play but Do NOT want to get bricked.
Android Doge said:
Do you think its safe to use Xposed on fire tv stick 1. I want to install Google Play but Do NOT want to get bricked.
Click to expand...
Click to collapse
I have been using Xposed / rbox mods & YouTube AdAway on 5.0.5.1 with the help of sconnyuk's guide since September with no problems. No idea on Google Play but you can disable Xposed easily now with custom recovery.
Thanks @rbox !
sconnyuk said:
Excellent.
If I get it up and running I will post how I managed it.
Click to expand...
Click to collapse
So yeah. Looks like it has the default google ids while in bootmenu. So installing a google fastboot driver should make it work.
It's working beautifully! Many thanks rbox, this is a fantastic development.
I've installed TWRP with no dramas and then I flashed the new pre-rooted ROM.
I had a bit of a brain [email protected] when connecting the stick to my PC, I was wondering how I was supposed to see what was going on when using mouse in shell. Then I realised it had to be plugged into the TV AND my computer. Sigh! The other discovery I made was being able to put multiple characters in to move the mouse pointer a lot in one go.
So all is good, no boot loops whatsoever and I now have recovery and root goodness.
Thanks again Rbox!
Can anyone please share the Adb drivers that they have installed on a windows 7 64bit system?
No matter what package I try I end up with the same issues, will connect fine with USB while the stick is booted (adb shell, giving [email protected],) but when I adb shell or adb connect*serialnumber* while on the boot selection menu I either get cant connect or device null.
Any help from you guys is welcome.
sconnyuk said:
Can anyone please share the Adb drivers that they have installed on a windows 7 64bit system?
No matter what package I try I end up with the same issues, will connect fine with USB while the stick is booted (adb shell, giving [email protected],) but when I adb shell or adb connect*serialnumber* while on the boot selection menu I either get cant connect or device null.
Any help from you guys is welcome.
Click to expand...
Click to collapse
Try this, worked for me.
First, Thanks rbox, awesome work as always.
Now for my issue, I can adb connect via network, but with the device pluggin to my pc i'm not seeing it in adb devices, or device manager even after installing drivers, minimal adb like above. this is on a win 10 x64 pc. any ideas? different usb cable or am I somehow missing an obvious step?
Thanks!
EDIT: Never mind, seems like it was a USB cable issue, swapped cables and all is working
ytsejam1138 said:
Try this, worked for me.
Click to expand...
Click to collapse
Thanks, will give them a go
---------- Post added at 09:26 PM ---------- Previous post was at 09:03 PM ----------
ytsejam1138 said:
Try this, worked for me.
Click to expand...
Click to collapse
Sorry, i already have these, i think my problem lies with the device driver for AFTM in device manager, is there any chance you could upload the driver for that ? thanks in advance.
---------- Post added at 10:09 PM ---------- Previous post was at 09:26 PM ----------
rbox said:
So yeah. Looks like it has the default google ids while in bootmenu. So installing a google fastboot driver should make it work.
Click to expand...
Click to collapse
Tried a bunch of different ADB drivers and AFTM device drivers and still no further forward.
When it boots to your selection screen i have in my device manager AOSP on ARM emulator, with no driver.
As soon as the countdown box ends, the Stick boots and my normal Adb devices is back in device manager.
Have you any idea on how to sort this issue ? cheers.
sconnyuk said:
Have you any idea on how to sort this issue ? cheers.
Click to expand...
Click to collapse
Yup. Get a real OS. Can't really help with Windows driver insanity. But I do know there are tons of posts on how to clear adb/fastboot drivers and reinstall them, and what not.
how is fire stick plugged into pc and tv at the same time ?
fattso123 said:
how is fire stick plugged into pc and tv at the same time ?
Click to expand...
Click to collapse
you need an adaptor
http://www.aftvnews.com/how-to-conn...-to-a-rooted-fire-tv-stick-with-an-otg-cable/
Related
I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
NewDev4IOS said:
I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
Click to expand...
Click to collapse
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Bricked Tablet Help
Gage_Hero said:
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Click to expand...
Click to collapse
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
NewDev4IOS said:
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
Click to expand...
Click to collapse
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Maybe this helps
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Bricked tablet
sj010489 said:
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Click to expand...
Click to collapse
Thanks
Im not sure if it is a bad usb cable, i think it is my computer because my computer doesnt even recognize my iphone and i have itunes installed,
i think it is partially due to a funky computer for me.
BRICKED
Gage_Hero said:
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Click to expand...
Click to collapse
It says fastboot
I sent my tablet in to asus
just waiting on them to reply
I have a ICOO D70PROII tablet, with a Rockchip 3066. After installing the Chainfire 3D driver, the tablet stucks at ICOO boot screen, even before the Android animation. I've started the tablet in recovery mode (appears the Android guy with the open bonnet and a red exclamation point).
I have the ADB drivers installed, i can access to almost everything in the ADB tool, except the "adb shell" command, even pushing up the mksh file to /system/bin.
The fastboot doesn't work, because the tablet turns off the screen, but appears in Device Manager an unknown driver, that I can't find the driver for it.
The RKBatchTool 1.3 and 1.5 doesn't recognize the tablet.
The only way I can see to fix this is doing the job in ADB command line, but the only way that I know to uninstall the Chainfire 3D driver is in Shell. Could anyone help me in this problem?
I made a small and simple recording showing the driver, RKBatchTool error and ADB errors. (please copy the following link to the browser's URL bar, I can't post direct links)
youtube.com/watch?v=4iQi5SkKGe4
Best regards and thank you in advance,
Ivan Santos.
IvanSantosPT said:
I have a ICOO D70PROII tablet, with a Rockchip 3066. After installing the Chainfire 3D driver, the tablet stucks at ICOO boot screen, even before the Android animation. I've started the tablet in recovery mode (appears the Android guy with the open bonnet and a red exclamation point).
I have the ADB drivers installed, i can access to almost everything in the ADB tool, except the "adb shell" command, even pushing up the mksh file to /system/bin.
The fastboot doesn't work, because the tablet turns off the screen, but appears in Device Manager an unknown driver, that I can't find the driver for it.
The RKBatchTool 1.3 and 1.5 doesn't recognize the tablet.
The only way I can see to fix this is doing the job in ADB command line, but the only way that I know to uninstall the Chainfire 3D driver is in Shell. Could anyone help me in this problem?
I made a small and simple recording showing the driver, RKBatchTool error and ADB errors. (please copy the following link to the browser's URL bar, I can't post direct links)
youtube.com/watch?v=4iQi5SkKGe4
Best regards and thank you in advance,
Ivan Santos.
Click to expand...
Click to collapse
Did you make a backup B4 installing Chainfire?
ken.okech.94 said:
Did you make a backup B4 installing Chainfire?
Click to expand...
Click to collapse
I didn't. But even I've made a backup, I can't connect the tablet to the computer with RKBatchTool and I can't install the Rockchip 3066 driver, only the ADB Android driver (which i can connect via adb).
Use ADB
IvanSantosPT said:
I didn't. But even I've made a backup, I can't connect the tablet to the computer with RKBatchTool and I can't install the Rockchip 3066 driver, only the ADB Android driver (which i can connect via adb).
Click to expand...
Click to collapse
Google a pre-made adb backup specifically for your tablet and restore it via adb. Or you can just use fastboot to flash a new ROM.
ken.okech.94 said:
Google a pre-made adb backup specifically for your tablet and restore it via adb. Or you can just use fastboot to flash a new ROM.
Click to expand...
Click to collapse
Did you read what I said?
I have the ADB drivers installed, i can access to almost everything in the ADB tool, except the "adb shell" command, even pushing up the mksh file to /system/bin.
The fastboot doesn't work, because the tablet turns off the screen, but appears in Device Manager an unknown driver, that I can't find the driver for it.
The RKBatchTool 1.3 and 1.5 doesn't recognize the tablet.
Click to expand...
Click to collapse
IvanSantosPT said:
Did you read what I said?
Click to expand...
Click to collapse
I think adb shell doesnt work because your tablet has not yet booted and will not be booted as long as it is in the current state.
Your only hope is RK Batch tool. Uninstall all current versions and the drivers you have in your computer and try reinstalling this and the drivers.
https://mega.co.nz/#!TIFwFCob!YniP23RpZH6hRj1Q-WSYvgQ4v28FUjU2qJ8b_4xLJXg
Your only hope!
ken.okech.94 said:
I think adb shell doesnt work because your tablet has not yet booted and will not be booted as long as it is in the current state.
Your only hope is RK Batch tool. Uninstall all current versions and the drivers you have in your computer and try reinstalling this and the drivers.
mega.co.nz/#!TIFwFCob!YniP23RpZH6hRj1Q-WSYvgQ4v28FUjU2qJ8b_4xLJXg
Your only hope!
Click to expand...
Click to collapse
Thank you, I reinstalled the driver and it worked. I installed the CWM 6.0.2.7 and all was working fine. Then I installed the CyanogenMod for RK3066 (cm3066.com) and the device doesn't boot, doesn't even shows the battery charger indicator and I can't mount or format anything in the CWM. I've lose the SD card, but I will borrow someone and try to reinstall the CWM, because I can't go to the RKBatchTool option.
Y u so Ungrateful?
IvanSantosPT said:
Thank you, I reinstalled the driver and it worked. I installed the CWM 6.0.2.7 and all was working fine. Then I installed the CyanogenMod for RK3066 (cm3066.com) and the device doesn't boot, doesn't even shows the battery charger indicator and I can't mount or format anything in the CWM. I've lose the SD card, but I will borrow someone and try to reinstall the CWM, because I can't go to the RKBatchTool option.
Click to expand...
Click to collapse
<<<<<<<<<<<<<<<<<<<<Hit thanks button if I helped , dude.
ken.okech.94 said:
<<<<<<<<<<<<<<<<<<<<Hit thanks button if I helped , dude.
Click to expand...
Click to collapse
No problema. But now I can't even reflash the CWM or the ROM, the tablet is soft bricked.
UPDATE: To access to the Downloading Mode, I had to click Vol+ plus Vol- when I connect the device to USB port. I am trying to flash with official firmware.
UPDATE 2: I've noticed that the ROM that I installed damaged the kernel, and now I need someone's boot partition dump.
UPDATE 3: I downloaded the oficial ROM from soft.aoicoo.com/soft/show.asp?id=285 and flashed the device. Then the device started! I installed the CWM 6.0.2.7 and then installed DarkwaterV2 CM ROM (not required). The tablet is working better than never with 10279 points scored in AnTuTu Benchmark v3.3! Thank you all!
I was trying to do this http://forum.xda-developers.com/showthread.php?t=2577826 and got up to replacing system.odex and everything crashed now it wont get past yellow load screen. I have safestrap but dont have more than one backup. Every time i run Adb come up with error:closed .I thought factory reset would fix but didnt now ive lost hope. HDX7 Help needed pls
and i tryed adb on multiple computer with no luck + different drivers. does show up in devices
Solved
that usual guy said:
and i tryed adb on multiple computer with no luck + different drivers. does show up in devices
Click to expand...
Click to collapse
Needed to input adb sideload rom.zip (Zip was also in file name but shouldn't be) and flashed to stock firm ware
Reflash?
Fixed
johnwaters said:
Reflash?
Click to expand...
Click to collapse
I fixed it by installing a new rom from adb
May i ask you a question?
How to connect adb?? i'm not connect adb...what is your os? win?or linux?
um.. please tell me the tutorial how to connect adb?
cjdfyd2 said:
How to connect adb?? i'm not connect adb...what is your os? win?or linux?
um.. please tell me the tutorial how to connect adb?[/QUOTE
I had safestrap so I put it in adb sideloader mode. And your device should be detected in device manager, if not install the right drivers. then go in cmd and navigate to adb file in platform tools from the package you should've downloaded. Then enter adb USB devices and it should show it connected. -windows xp
Click to expand...
Click to collapse
The titel says it all , and I need some help. I can still go in recovery but adb won't recongize my HTC, but I can still find it in fastboot. I formatted the sdcard, so I have nothing on there. Help would be much appreciated.
vsp33ddyv said:
The titel says it all , and I need some help. I can still go in recovery but adb won't recongize my HTC, but I can still find it in fastboot. I formatted the sdcard, so I have nothing on there. Help would be much appreciated.
Click to expand...
Click to collapse
Oh, trust me that's not your phone being bricked. You guys seriously need to know the correct vocabulary.
Bricking the phone: The phone's only use is to use it as a literal brick. It does not turn on, does not recover, does not charge, does not do anything and it can never be restored.
HOX+ can NOT be bricked unless you are S-Off'ed. Now that we got that out of the way,
you seem to understand that ADB is the solution here, that you need to sideload a rom, the question that you have is the adb does not recognize your phone, so follow these steps:
-Connect the phone using a different usb port, (basically thats the easiest thing), if its 2.0 then try 3.0 and vice versa.
-Restart your computer
-Restart your phone
-If you are on windows Vista and later, open start menu search for "cmd" then right click and run it as administrator, then you need to cd to your adb directory.
Code:
cd C:\Android\sdk\platform-tools
for example. then try adb devices.
Anyway hope you get it to work and have fun
Ghand0ur said:
Oh, trust me that's not your phone being bricked. You guys seriously need to know the correct vocabulary.
Bricking the phone: The phone's only use is to use it as a literal brick. It does not turn on, does not recover, does not charge, does not do anything and it can never be restored.
HOX+ can NOT be bricked unless you are S-Off'ed. Now that we got that out of the way,
you seem to understand that ADB is the solution here, that you need to sideload a rom, the question that you have is the adb does not recognize your phone, so follow these steps:
-Connect the phone using a different usb port, (basically thats the easiest thing), if its 2.0 then try 3.0 and vice versa.
-Restart your computer
-Restart your phone
-If you are on windows Vista and later, open start menu search for "cmd" then right click and run it as administrator, then you need to cd to your adb directory.
Code:
cd C:\Android\sdk\platform-tools
for example. then try adb devices.
Anyway hope you get it to work and have fun
Click to expand...
Click to collapse
The only thing I can do is use fastboot , thx for noticing that I know I need adb sideload If I look in devices on my PC I can see 'ONE' with a yellow triangle next to it ( so this means drivers) I downloaded my HTC drivers and I right clicked on the device and then update from PC , I go to the folder where I installed it and click on search and it says it can't find a driver for this device.
I also tried 4 different USB ports both 2.0 or 3.0 , no result. I also tried to install TWRP instead of cmw but on TWRP my touchscreen doesn't work while on cmw it does. So i went back and flashed my recovery to cmw again ( I tried version 2.6 - 2.7.0.1 , no result )
So my problem right now can be solved once my device can be recognized by my PC. (Have HTC maneger installed , also downloaded drivers formy phone , got fastboot and adb on my PC )
For anyone who knows thanks
vsp33ddyv said:
The only thing I can do is use fastboot , thx for noticing that I know I need adb sideload If I look in devices on my PC I can see 'ONE' with a yellow triangle next to it ( so this means drivers) I downloaded my HTC drivers and I right clicked on the device and then update from PC , I go to the folder where I installed it and click on search and it says it can't find a driver for this device.
I also tried 4 different USB ports both 2.0 or 3.0 , no result. I also tried to install TWRP instead of cmw but on TWRP my touchscreen doesn't work while on cmw it does. So i went back and flashed my recovery to cmw again ( I tried version 2.6 - 2.7.0.1 , no result )
So my problem right now can be solved once my device can be recognized by my PC. (Have HTC maneger installed , also downloaded drivers formy phone , got fastboot and adb on my PC )
For anyone who knows thanks
Click to expand...
Click to collapse
Hmmm. I would say in the device manager right click on the one and uninstall. Then in fastboot mode unplug and replug the device, let it install fastboot again and then try if adb can read it now.
Ghand0ur said:
Hmmm. I would say in the device manager right click on the one and uninstall. Then in fastboot mode unplug and replug the device, let it install fastboot again and then try if adb can read it now.
Click to expand...
Click to collapse
Still can't read it...
This has happened to my phone twice... fixed it the first time by using USB deview to remove all Android/HTC drivers, then reinstalled them with the HTC Sync installer. Couldn't get that to fix it last time though, so I tried another computer and it worked just fine. So my advice would be to find another computer and try it.
911jason said:
This has happened to my phone twice... fixed it the first time by using USB deview to remove all Android/HTC drivers, then reinstalled them with the HTC Sync installer. Couldn't get that to fix it last time though, so I tried another computer and it worked just fine. So my advice would be to find another computer and try it.
Click to expand...
Click to collapse
YES THIS IS WHAT WORKED ONLY I DID SOME OTHER STEPS TOO!!! Now I got adb running again and I can only push , I'll explain later in a full tutorial how to fix this now you guys can help me , I'm trying to download a cyanmod for my HTC because the stock is german and I can't download it , so can anyone upload the cyanmod endeavouru for me I keep getting error 502 bad gateway I almost fixed it !!!!! I need it badly !
OOkay so I thought I had figured it out , I uste TWRP to push files from PC to my Phone , then I installed cmw and tried to install the ROMS , but apperantly my roms were deleted. (I can't use TWRP because I need touch and the touch doesn't work , while in cmw the touch does work)
So if we can fix the TWRP touch I will know how to fix my problem !
I fixed the problem
I fixed the problem , thread how comming soon !
Here is my thread http://forum.xda-developers.com/showthread.php?p=52550145
I'm aware there is another thread on this, but his solution was simply switching the cable. For me, adb is currently working on multiple other phones, but on the G8X, it simply doesn't list the device. Any idea?
I do NOT have the full Android SDK, only the "minimal ADB and Fastboot" package, which just comes with adb, fastboot, and a couple other things. I love it and hope I don't have to install the full SDK for fastboot to work. D:
USB debugging is enabled, the device is connected as "File Transfer," and everything else is as it should be.
1337haXXor said:
I'm aware there is another thread on this, but his solution was simply switching the cable. For me, adb is currently working on multiple other phones, but on the G8X, it simply doesn't list the device. Any idea?
I do NOT have the full Android SDK, only the "minimal ADB and Fastboot" package, which just comes with adb, fastboot, and a couple other things. I love it and hope I don't have to install the full SDK for fastboot to work. D:
USB debugging is enabled, the device is connected as "File Transfer," and everything else is as it should be.
Click to expand...
Click to collapse
Same issue. Trying to use the Button Mapper app, and windows Button Mapper Setup keeps saying "Make sure the device is connected and USB Debugging is enabled."
Help?
You must try multiple times until a notification shows up to trust your PC.
hasso96 said:
You must try multiple times until a notification shows up to trust your PC.
Click to expand...
Click to collapse
Actually it was more "complicated" than that, as it said it ran an older version of the server than the phone at first. I googled some more, and managed to solve it. It was the installation of the LG USB mobile driver. I tried with the windows stock one at first, then tried Google USB driver from the SDKmanager, and even an universal driver didn't work. And even then when it was installed, THEN it said "unauthorized" and I had to just accept the connection on my phone
It's sorted now!
THANK YOU SO MUCH! Man, I wasn't expecting a reply after all this time, figured my unit was somehow defective or something. This worked perfectly! To others suffering, here's the direct link to the LG drivers, current version as of now, 4.4.2: tool.lime.gdms. lge .com/dn/downloader.dev?fileKey=UW00120120425 (Remove the spaces before and after the "lge").
Now I can tweak my system settings, debloat, use Button Mapper. Thanks again!