I have a couple of questions about Linux and its communication with Android. Linux is supposed to communicate better with your device, right? Or have I been lying myself. So, what exactly are your options to debrick a device using Terminal in Linux ( I'm using ubuntu )? You cannot use adb if you havent enabled USB Debugging mode, which is not enabled on the tablet I'm trying to revive, and cannot use fastboot with no root privileges on the device. All this time I have thought that Linux communicates way better with android devices than Windows does, but I cant find any guides on how to unbrick this tablet. Although I have posted a thread about the specific model, I'm not gonna post it here to make it blah-blah-blah thread, I dont want you to do all the work, I just need somebody to point me in the right direction. Bricked tablet, USB Debugging not checked, not rooted, bootloader locked. What can be done within Linux to Revive the tablet?
Anybody?
Well, all the inter operating system communication is relative. I personally prefer Linux. And fast boot doesn't need root. If your device isn't booting up yet try using lsusb after plugging the phone to check whether the phone is connected. Add that to udev rules and then fastboot should work
Coltie ~ Did you get this worked out?
Where's your other post w/specs?
Related
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
fightingcrest said:
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
Click to expand...
Click to collapse
Make sure that you've mounted USB as "None", you can do so by pulling down the notification bar. Hope that helps!
fightingcrest said:
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
Click to expand...
Click to collapse
make sure usb debugging is ON, set usb connection to NONE. I'm assuming you have sdk installed in c:\ of computer. Then go to cmd prompt and type: "cd c:\android-sdk-windows\platform-tools" [enter]
Then, type: "adb devices" [enter]
Should detect device, or something is wrong.
Hell, just go install the CWM and install the mods that way. A lot of them are updated to now work with CWM. See here: http://forum.xda-developers.com/showthread.php?t=1019143
Tried ViperMod, SparkyRoot with no success.
SparkyRoot fails at stage 2 as Asus Backup fails every time...
With ViperMod i can't see the device when connected to MacBook Air [./ADB devices - no devices listed]
SO... either looking for a way to get something like SparkyRoot to work or tips on how to get TFP visible with Mac OSX Lion OR something new.
Please devs help a man out!!
I also use a Mac and have rooted just fine using ADB Push.
If it's not detecting your device it sounds like you haven't enabled USB Debug Mode in Settings -> Developer. I'd double check that.
Thanks - yes tried all the usual stuff - must have read 100's of posts in case I'm missing something silly.
Tried on Mac OSX Lion - MacBook Air and Mac Mini
Mac OSX Tiger - old iBook
and even built a VM on Mac Mini running XP [scuppered there as couldn't get ADB drivers to work]
I wouldn't mind if I was fumbling around with the wrong commands in Terminal or something, but i'm not even getting the damned thing to be seen on any PC/Mac except as a sync device or camera.
Please please somebody find a true 'one stop root' that doesn't need tethering or ADB.
I really want to get bootloader unlocked, CWM and CM9 on this thing - and unleash the real potential.
trying to use SparkyRoot but need help please, asus prime TransformerTF201
Trying to use the SparkyRoot but getting message in step 1 saying exploit not working, then step 2 fails to backup. Am i supposed to have installed other stuff first?, or how can i get this to work
Just root manually through adb, it's easy enough if you know how to read.
still need specifics
rand4ll said:
Just root manually through adb, it's easy enough if you know how to read.
Click to expand...
Click to collapse
ok, i can do that :-> , but can you give me a specific link or directions, an it needs to be very specific breakdown of directions, i'm a total newbie, and don't even know what you mean by adb!! Yes there are still some of us like that who exist out there, :-€ but can follow a very laid out step by step procedure. Please don't say search cause then so much comes up an i'm just boggled! :9)
Root method for windows or Mac?
Is there a root method for the .15 build available for windows or Mac? I do not have linux. I have a Chinese machine and want to install the proper android market. I have found the instructions of what to do once the machine is rooted, but cannot get to root itself to work. Tried using Primetime, but that only works upto .11 from what I can tell.
Cheers for any replies,
David
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Hi
I do have a basic knowledge of bootloaders, rooting etc (have done all that on various Android phones), but with my new LG G5 H850 Unlocked European phone, I'm stumped. I have activated the unlock OEM in Dev Options, have enabled USB Debugging, installed who knows how many LG drivers, USB drivers, ADB drivers, etc, yet the DOS window can't see the phone.
I have a Windows 8.1 laptop. When I type adb devices into my Dos window, it can't see the phone (nothing comes up in the list). I type ADB reboot bootloader & it just says "Error: Device not found". In my laptop Device Manager it shows as a G5, it shows in Device Manager as the various Android devices when I change the various USB options from charge to photos, to file transfer, etc, I can happily move files between the phone & laptop within Windows Explorer, but my laptop just doesn't seem to see it within DOS.
I can't even manually boot the phone into Bootloader using the vol key & on/off switch, but I guess that'll take practice (even have trouble taking screenshots that way).
I guess I can't root without unlocking the bootloader? I've tried one-click root & King root, but both fail.
I'm obviously being a complete pratt & missing something somewhere (& am sure I'll kick myself if/when I find out).
Thanks
rockluvva said:
Hi
I do have a basic knowledge of bootloaders, rooting etc (have done all that on various Android phones), but with my new LG G5 H850 Unlocked European phone, I'm stumped. I have activated the unlock OEM in Dev Options, have enabled USB Debugging, installed who knows how many LG drivers, USB drivers, ADB drivers, etc, yet the DOS window can't see the phone.
I have a Windows 8.1 laptop. When I type adb devices into my Dos window, it can't see the phone (nothing comes up in the list). I type ADB reboot bootloader & it just says "Error: Device not found". In my laptop Device Manager it shows as a G5, it shows in Device Manager as the various Android devices when I change the various USB options from charge to photos, to file transfer, etc, I can happily move files between the phone & laptop within Windows Explorer, but my laptop just doesn't seem to see it within DOS.
I can't even manually boot the phone into Bootloader using the vol key & on/off switch, but I guess that'll take practice (even have trouble taking screenshots that way).
I guess I can't root without unlocking the bootloader? I've tried one-click root & King root, but both fail.
I'm obviously being a complete pratt & missing something somewhere (& am sure I'll kick myself if/when I find out).
Thanks
Click to expand...
Click to collapse
try to use driver from link below
https://1drv.ms/f/s!Au9ppCUF0J7lgZpUFNW-cf8ot0EweA
now while making sure usb debug is enabled, try to see if in device manager in windows, you have the proper driver selected
I remember one time Windows did use a generic ADB driver that did not work with my G5 so this might be your case also
alternative way of testing is by trying to install a virtual machine and see if you can read it from there
most of the cases this is windows fault (you I know Microsoft douh)
gwolfu said:
try to use driver from link below
https://1drv.ms/f/s!Au9ppCUF0J7lgZpUFNW-cf8ot0EweA
now while making sure usb debug is enabled, try to see if in device manager in windows, you have the proper driver selected
I remember one time Windows did use a generic ADB driver that did not work with my G5 so this might be your case also
alternative way of testing is by trying to install a virtual machine and see if you can read it from there
most of the cases this is windows fault (you I know Microsoft douh)
Click to expand...
Click to collapse
Hi Gwolfu
Yup, I have that driver already, thank you for that. But I've now been able to unlock the bootloader. Guess a reboot was in order, as it's the first time I've turned on the laptop today.
Thanks so much for your reply though
Sigh!
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
cq_ said:
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
Click to expand...
Click to collapse
First verify drivers are working. For whatever reason legacy composite drivers from Motorola seem to work best with this device regardless of platform or host OS. Install the Motorola Device Manager from this page and then switch drivers. No need to launch the utility.
TWRP must be at v2.7 or above for ADB support. If below 2.8.6.0 you should consider updating via fastboot assuming bootloader has been unlocked. See: https://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-3-0-0-0-t3322547
If still no joy you will have to erase/replace aboot and rebuild the device from scratch. Data loss is likely.
hmm yeah, the main problem seems to be the tablet never shows up in device manager as any device... thanks for the hints though, will try the motorola device manager drivers...
cq_ said:
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
Click to expand...
Click to collapse
Where'd you get the drivers from? Can you share a link to the ones you installed on your PC? In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled? What version of Windows?
I haven't tried this yet personally yet but I'm wondering if a live Linux (e.g. Mint) booted on USB thumb drive might be an option. I don't know enough about using a Mac to access the Kindle to offer much in detail there. Have you tried different USB ports on each of these computers? Do other USB devices show up okay?
fufu508 said:
Where'd you get the drivers from? Can you share a link to the ones you installed on your PC? In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled? What version of Windows?
I haven't tried this yet personally yet but I'm wondering if a live Linux (e.g. Mint) booted on USB thumb drive might be an option. I don't know enough about using a Mac to access the Kindle to offer much in detail there. Have you tried different USB ports on each of these computers? Do other USB devices show up okay?
Click to expand...
Click to collapse
Read here literally two posts above yours. Where was Linux/Mac ever mentioned? Connectivity on Windows almost always boils down to procedures, drivers and/or USB cable integrity. Assuming the device itself is not toast.
fufu508 said:
In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled?
Click to expand...
Click to collapse
Oh snap, this is a good idea - will try when I get home.
TWRP 3.1.1-1, Win 10 64bit - yeah tested several usb ports on my computer - I originally rooted the HDX with this computer and windows 10 install about 2 years ago [side note do you guys remember reformatting every 6 months because windows was such a pos, I'm really glad those days are long gone!]
LOL yep Windows 10 nowadays does seem a lot more stable than the earlier stuff.
---------- Post added at 06:14 PM ---------- Previous post was at 05:50 PM ----------
Davey126 said:
Read here literally two posts above yours. Where was Linux/Mac ever mentioned? Connectivity on Windows almost always boils down to procedures, drivers and/or USB cable integrity. Assuming the device itself is not toast.
Click to expand...
Click to collapse
Hi Davey oops somehow I missed that you had already replied a few days ago . cq_ did mention a Mac computer. I suggested testing with a live Linux thumb drive boot in case they have an extra thumb drive kicking around to find out what that OS sees as compared to the Windows and Mac already tried. When reviving my Thor, part of the process I tried was draxie's 1-click, which required Linux and access to the device to do its work, so it seemed like a good to me to try to boot the PC that cq_ is using into Linux. In my case I have Linux Mint installed on a separate SATA hard drive but not everybody has that type of rig, hence the live Linux USB thumb drive boot suggestion.
fufu508 said:
Hi Davey oops somehow I missed that you had already replied a few days ago . cq_ did mention a Mac computer. I suggested testing with a live Linux thumb drive boot in case they have an extra thumb drive kicking around to find out what that OS sees as compared to the Windows and Mac already tried. When reviving my Thor, part of the process I tried was draxie's 1-click, which required Linux and access to the device to do its work, so it seemed like a good to me to try to boot the PC that cq_ is using into Linux. In my case I have Linux Mint installed on a separate SATA hard drive but not everybody has that type of rig, hence the live Linux USB thumb drive boot suggestion.
Click to expand...
Click to collapse
Fair enough; I may have been a bit harsh in my response. I now see the passing reference to an Apple rig and appreciate the unfiltered perspective often obtained via Linux. That said, there is new info on the table that suggests the OP has access to a Win10x64 box which should connect effortlessly/reliably with Moto drivers and a quality USB cable. Mucking with drivers can be a PiTA on Windows; the Moto variants remove much of the pain - although you still have to select the proper driver after tethering in the target mode (adb or fastboot) as Windows will typically default to Microsoft/stock variants which rarely work with HDX devices.