Hey everyone. Long time lurker, first time poster, and always grateful.
Okay, so I took a good look at some related threads. They all seem to have been resolved by using tools specific to their particular device. I have not had luck following their lines. So, here's what's up with me:
Asus Transformer Tf700 US edition
Had Cyanogen Mod. Wanted to sell my tablet, so I decided to wipe and go back to factory. Unfortunately, while fooling around in TWRP, I managed to putz it up and wipe the system and data. So no more OS, and apparently no more super user (whoops), although I may be wrong about that.
I can reboot the device into TWRP, but I can't mount the microsd card. When I plug my microsd card into my device, I just get an error that says cannot mount external sd card. So, since that isn't working, I've tried to sideload via adb.
I have the SDK but can't run ADB sideload because ADB on my computer does not recognize my device. I have tried to install updated drivers, though the drivers that I did find, when I point windows to the folder with them, it doesn't see a driver. SO maybe I'm doing that wrong.
I'm completely at my wit's end here. Can someone give me a little help?
Thanks everyone for your help in advance.
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
berndblb said:
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Hey there, thanks so much for replying!
I'm using TWRP v2.6.0.0.
Windows 7 x64 SP1
The CM version that I had, I actually don't recall now. I had flashed it back to stock though, before this, by using TWRP recovery. I noticed after that that I had not flashed my saved files properly. That's when I pooched it, hah.
I removed the existing USB drivers via device manager, restarted, used the installer that you linked to, restarted, and plugged in my device. It said installing drivers, and then failed to install drivers. ADB does not recognize a connected device. Merp.
I still haven't had any luck. Does anyone have any ideas?
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=2646279
berndblb said:
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
Click to expand...
Click to collapse
Hey, thanks for the reply. When I plug in the device, it tries to install drivers and almost immediately fails. It then shows in the device manager as shown in the attached file. When I right click, select update driver, and point it to the folder with the google naked drivers (or the asus drivers), it says that "Windows cannot find drivers for this device." This seems strange to me. It has no idea what the transformer is when it is plugged in. Is there a different manual method of installing drivers, or cuing windows to recognize that these are the correct drivers?
I had Asus Sync installed, and that didn't seem to do anything for me. Windows would not do anything differently than it had already done. Grrr. This hurts.
sbdags said:
http://forum.xda-developers.com/show....php?t=2646279
Click to expand...
Click to collapse
This method looks promising, but it requires one to go into Android and turn on USB debugging mode. Problem is: I have no OS to log in to in order to do so
Whoops, forgot screen shot
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
berndblb said:
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
Click to expand...
Click to collapse
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
hardshank said:
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
Click to expand...
Click to collapse
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
I do not understand your driver problems at all. I helped someone today with a lot of the same problems: The tablet only booted into recovery, TWRP would not mount the microSD, didn't see any files on the internal... The ADB tool I linked to earlier allowed him to adb reboot to the bootloader - the rest was a breeze... Something in your Windows setup is just effed up... Sorry - wish I had that magic wand...
berndblb said:
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
Click to expand...
Click to collapse
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
_that said:
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
Click to expand...
Click to collapse
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
berndblb said:
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
Click to expand...
Click to collapse
On some live distros you can install additional software to a ramdisk. For adb and fastboot, any live distro with 32 bit libraries should have the required libs so that you can just copy/download the binaries and run them.
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
hardshank said:
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
Click to expand...
Click to collapse
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
hardshank said:
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
Click to expand...
Click to collapse
Glad you got it working!
Out of curiosity: Was your tablet booted or completely off until you picked it up today? Did you reboot into the bootloader or did it do that by itself?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Hi All,
I've been wanting to create a Windows To Go Drive on my Android so that I can simply plug in my phone into any PC i want and voila, my own Windows 8.1!
I've only had limited success, so I wanted to ask the dev community what could be going wrong.
What I Used:
Sprint Galaxy Nexus (Rooted, 4.3)
DriveDroid
Sony Vaio Laptop running Windows 8 (Win7 and below dont have latest DISM or Diskpart) (Capable of UEFI booting)
What I Did:
1. Used DriveDroid to create a 10GB image file. It made the file, so i'm guessing that the internal sdcard of the Nexus is not FAT32. No Partition Table and no File System (Yet)
2. Plugged in the phone. Recognized it as a USB Drive.
3. Used Diskpart to clean drive, create primary partition, format as ntfs and set active
4. Extracted install.wim from Windows 8.1 Disc
5. Used DISM to copy image onto Blank USB Drive (Took around 2 hours)
**It's better to use DISM in comparison to ImageX, since ImageX is older and has mixed results
6. Used BCDBoot to copy boot files onto USB Drive
7. Rebooted. UEFI Boot Failed (Didnt even attempt to recognize the drive)
8. Legacy Boot WORKED! Reached Windows Boot Manager
From here though, the Boot Manager simply refuses to recognize the existence of a Bootable OS. (Screenshot uploaded) :crying:
I've been using EasyBCD to change the configuration to make it work. No results yet.
I dunno how close I am to making this work - Maybe really close or probably a gazillion miles away. But I've put a lot of thought and effort into this and was really hoping it would work. :laugh:
Any advice as to where i could be going wrong?
Hi all!
I managed to get to make it boot!
It reaches the windows 8 boot logo and the spinning circle just keeps spinning on and on and on.....doesn't stop spinning but doesn't go further than that either.
When it does that, there is
a) No HDD activity
b) No response from Num Lock and Caps Lock key lights
c) No BSOD or response when the phone is unplugged
It's like it doesn't care. Just keeps spinning
Any ideas to what could be wrong The drive is definitely NTFS, with extra space present. I've tried this on multiple PCs
I think I'll try making it again
Regards,
Xyan
I tried to install android 7.1 86x firstly for BIOS(legacy) mode because i like to keep the second OS hidden then I can boot directly to Windows 8.1 on EFI, then I selected to install grub however my stock bootloader was still starting and nothing of grub and therefore I cannot boot into android. Then I decided to install for EFI because I was a whole day trying to work that out and couldn't find any answer on Internet, however seems like the stock bootloader starts instead of grub after I restart the pc.
Extra information:
My pc has an E1-2000 AMD processor, it is 64 bits (and yes, i downloaded the right iso file).
Windows boots from EFI, and I had Kali Linux previously installed with grub and worked fine.After I removed kali I also removed grub with "bootrec /fixmbr" and "/fixboot" on command prompt.
Windows is working fine.
Try downloading the easyUEFI tool (check google) and on windows set a partition for Grub + setting it as the default over MBR
LilAnt530 said:
Try downloading the easyUEFI tool (check google) and on windows set a partition for Grub + setting it as the default over MBR
Click to expand...
Click to collapse
What if I don't have windows there anymore? Is there a similar solution, inside a command line maybe?
I think I'm in a similar situation where I can install and run Androidx86 from my USB, but if I restart the laptop it won't find any boot option.
Hello. I have installed BlissOS 10.1 nightly build on a Dell Venue 11 Pro 7139. The iso used was Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso. The installer completed succeffuly and I installed to my C: partition as an image partition, not as a separate partition. When I try to boot the OS, it starts as usual saying android found at sda sth, then after a very quick dump of echoes I don't know how to capture, the boot logo animation appears and stays there forever. After a number of attempts, I realized that the console is active and I can type commands like logcat. Unfortunately they only appear as they scroll because apparently the boot animation refreshes the screen, so I can't see the output and don't know if there is any command to stop the animation or redirect the output of the command to a log file that I can read through Windows. I had successfully installed BlissOS in the past in the same notebook, but had to resort to PhoenixOS, because touchscreen input didn't work. In PhoenixOS everything worked, but now I need Widevine DRM support and read that BlissOS currently supports it.
Any help would be appreciated.
slazaris said:
Hello. I have installed BlissOS 10.1 nightly build on a Dell Venue 11 Pro 7139. The iso used was Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso. …… Any help would be appreciated.
Click to expand...
Click to collapse
I have never installed BLISS; but, I had the same thing happened with Android X 86 install. I did a quick reinstall And when prompted to run Android or reboot I chose the reboot option. The operating system booted up just fine after that.
I met the similar probem on Qemu
It's very strange. It does work at the begining, and i used it for some days, but suddendly can not boot into the desktop, just stuck at the boot logo.
And i met this problem on three different PCs with Qemu.
BTW: I am using Bliss-v11.10--OFFICIAL-20191214-2253_x86_64_k-k4.19.50-ax86-ga_m-18.3.5-pie-x86-llvm80_ld-2.4.99-ma-p_dg-pie-x86_dh-undefined_gms.iso
i have same (lingeageos) on virtualbox
So it has been a hectic few days for me as I had alas managed to wipe my system reserved partition thinking that installing android x86 as multi-boot would actually boot windows for me. Wrong!!! My first poor encounter was the fact that when I had installed windows it had created the system reserved partition as ntfs... I had not realized this when attempting to install android x-86 as multi-boot. I will tell you the result, when booting it would appear to go to grub, however instead it just booted the first menu on the list without hesitation and gave no menu at all. To remedy this I had to use the windows 10 usb i had created for my initial install. I am still not sure how i managed to get it to boot the first time I think it may have just been dumb luck. When windows booted up i went to Disk Management (right click the windows menu and select from the drop down) where I then proceeded to delete the system reserved partition and reformat it fat32. At this point I was satisfied that android would point the out the windows boot, boy was I wrong. After installing Android x86 (_64 8.1 r3) I finally achieved the grub menu boot correctly. I also noted that when installing android x86 the only way it gave me option to add windows to grub was if i had installed without formatting first. (this can be done a few ways including just reinstalling much the same way you would dirty flash a rom on a phone) or you could use a tool to format the partition such as gparted or a linux live cd/usb. I suggest ext4. Oh wait my nightmare hadn't finished yet... Android x86 install had no problems at all (select partition to install(ext4)... do not format... install grub... yes to windows... yes read write... and then reboot) on reboot windows was in the grub menu and I selected it... oops there is no operating system!!! Well that is unsettling... ( I managed to get back into windows using the install media) and not so sure how. At this point i notice that my system reserved partition was now sda 3) So my next objective was to create a boot record for windows which could have been done easily from windows had I considered using bcdedit tool for windows. But since i knew that the partition was sda 3 I figured I could just point the grub menu to the correct drive... again wrong (there was still no boot mbr on that partition *sigh) Well I found that when i went into command line from the windows repair tool it would say I do not have permission to fixboot... wow nice job microsoft... after doing a bit more research I learned that the newer builds give this error when attempting to fix boot. I found a video on youtube which helped me alot but took quite a while to download the older working repair tool(installation media) but his video was fairly well put together. link here (https://www.youtube.com/watch?v=lRCyb7FzWFY). I followed his guide and this time with the repair tool that he shared in the description of his video, I was able to perform the fixboot (bootrec /fixboot) however one of his commands required the copying of bcd to the system reserved partition. The copy failed, however at this time running all the other bootrec commands seemed to go fine. So I exited command and went to the automatic startup repair, which to my surprise worked perfectly... (after a whopping 30 some hours of pulling my hair out of my head over this mess) And windows began to boot. At this point I gave my thanks to the poster of the video and shared my experience with his video in the comments below.) Now When windows booted up I downloaded the bcdedit tool. Personally I used the multi boot tool from this site (https://www.boyans.net/dual-boot-repair-windows-10.html) and selected repair mbr and boot record. This fixed my boot issue windows would boot normal at reset. However now my android was gone but thats okay.
At this point I just reinstalled the android x86 again over the same ext4 partition without formatting and added the windows to grub. This was perfect however when selecting windows did not boot. To fix this I had to edit the grub menu.lst and change the drive from hd(0,0) to hd(0,2) to point to the fat32 partition which had been somehow displaced to sda3. In order to do this I ran android in debug... when debug is running just hit enter and it give you a prompt... from prompt type without quotes "cd /mbr/grub" when the next prompt comes up you should be in the grub directory where the menu.lst is. Now type without quotes "vi menu.lst" this will take you into a text editor (note you can also change your monitors and resolution permanently in grub menu this way) using the arrow keys navigate to the line you want to edit, in my case the last entry which was windows entry when you get to where you need to edit hit the "i" key this will allow you to now enter and edit the text. After making changes hit "esc" to save changes type ":w!" then hit enter. To exit type ":q!" this will take you back to prompt. Now reboot your system and finally the results I had originally hoped for a multi-boot system with windows 10 and android. Now if you are attempting to do this and are looking for a guide to install I will make this just a little longer to make sure you dontt make the same mistakes I made.
1a) before you attempt to install a dual boot with grub... make sure your system reserved partition is fat32 if it is not you need to change it to fat32. as grub will not boot on ntfs partitions.
1b)you will need to have a blank partition, if you have spare room on the drive you can shrink your volume and create a new one. There are plenty of tools out there to format ext4 even from windows. Make sure you format it before installing. (if you are lazy like me you can format ext 4 from the installation, but there is a chance that you would need to reinstall again and choose not format to get the windows entry in grub)
1c)once your partitions looks the way you need and you have a working fat32 system reserved partition you are ready to move on. ( If you have to change a ntfs partition to fat32 I highly suggest you dont install anything until you have repaired the boot menu and tested it first to make sure it works)
2)create your install media... I prefer to use rufus as it is quick and easy, and I prefer the official android x86 as the 8.1 r3 is stable and works great, you can use whatever image you want though, lord knows i test newer versions as they come out. when you have rufus and the android x86 iso of your choice load rufus select your usb drive and select the iso with the browse button. then just hit start allow it to format and when it is done you can boot into your usb
3)To boot into your usb you may actually need to edit your bios and enable virtualization and make sure safeboot is not enabled, also you need a uefi system for x64 distros so if you have an older legacy bios you will need the x86 version instead or the system wont boot
4)When you finally get it to boot you will find the menu to use it as a live cd or install, select the install.
5a) You will now be asked where to install to. Pick the ext 4 partition you created for it.
5b) Now it will ask you to format choose do not format (again if you hadn't formatted the partition ext4 you may do it now, but you may have to reinstall and not format the next time to add windows to the grub menu)
6) You will now be asked to install grub answer yes, if you do not answer yes you wont be able to get back into your android partition again until you do.
7) Now it will tell you that it found a windows partition and asks you if you want to add an entry, select yes... if you do not you will have to make your own grub entry to get back into windows later or completely delete grub from the partition later.
8) Finally it will ask you if you want to make the system read write... select yes, if you select no i can not guarantee you will be able to install anything inside of the system.
10) The end... Installation finishes but do not click launch... instead click reboot. The reason for this is that I have noticed if you launch at the end of installation the grub somehow manages to disappear and you end up having to completely start over.
Enjoy your android x86 / windows multi-boot system.
make sure your system reserved partition is fat32
Click to expand...
Click to collapse
There is no system reserved partition on my laptop since I have a UEFI laptop.
Should I proceed ?