So, my phone's bricked - it won't boot, just brings up fastboot. As the solution to this problem appears to be to use the MSM tool to do an "actual" factory reset, I downloaded the MSM tool, and the decrypted ROM from this link: https://androidfilehost.com/?fid=8889791610682918291.
First I tried this on a Windows 7 VirtualBox VM (I use Ubuntu on my actual computer). The drivers didn't even install right it seems, and the device (in EDL mode) wasn't even recognized. Then I tried it on my mom's Windows 10 laptop. MSM never showed the device as connected. I think possibly the lack of a USB 2 port could be the cause.
Finally I set up a basic VM with Windows 10 and a USB 2 controller, and it worked-ish. MSM recognized the device, showed it as connected and started doing its thing, but stopped at "Sahara Communication failed". What is preventing it from getting past this? I'm using the cable provided in the box. Everything is recognized correctly. I've retried multiple times but still the same result.
SUCCESS!
I had a spare laptop lying around, and it has USB 2 ports. I loaded WIndows 10 onto it and tried the MSM from there -- AND IT WORKED!
As much as I hate Qualcomm for their monopolistic business practices, I thank them for EDL mode. I also thank OnePlus for somehow failing to prevent the MSM tool from entering the hands of the public every time, and @Some_Random_Username for trafficking this good. Yeet!
Glad you got it sorted and left some feedback! cheers
crispy-cat said:
So, my phone's bricked - it won't boot, just brings up fastboot. As the solution to this problem appears to be to use the MSM tool to do an "actual" factory reset, I downloaded the MSM tool, and the decrypted ROM from this link: https://androidfilehost.com/?fid=8889791610682918291.
First I tried this on a Windows 7 VirtualBox VM (I use Ubuntu on my actual computer). The drivers didn't even install right it seems, and the device (in EDL mode) wasn't even recognized. Then I tried it on my mom's Windows 10 laptop. MSM never showed the device as connected. I think possibly the lack of a USB 2 port could be the cause.
Finally I set up a basic VM with Windows 10 and a USB 2 controller, and it worked-ish. MSM recognized the device, showed it as connected and started doing its thing, but stopped at "Sahara Communication failed". What is preventing it from getting past this? I'm using the cable provided in the box. Everything is recognized correctly. I've retried multiple times but still the same result.
SUCCESS!
I had a spare laptop lying around, and it has USB 2 ports. I loaded WIndows 10 onto it and tried the MSM from there -- AND IT WORKED!
As much as I hate Qualcomm for their monopolistic business practices, I thank them for EDL mode. I also thank OnePlus for somehow failing to prevent the MSM tool from entering the hands of the public every time, and @Some_Random_Username for trafficking this good. Yeet!
Click to expand...
Click to collapse
Hi crispy-cat,
Looks I have the same problem as you did. Using Kubuntu and Windows10 in VirtualBox.
My device is not recognized when I boot into edl-mode so I can't use MSM to unbrick my device. It does not pop up in devicemanager when I connect it with the original usb cable.
Can you explain the set up of a USB 2 controller? What is it hardware or software? I am not familiar to this and don't understand what you did. I think this can help me figuring out how to get the MSM tool working for me and flash the original OS back to the device.
Unfortunately I don't have access to a windows computer.
The USB controller is part of VirtualBox. I think you need to download and install the extensions pack for the USB 2.0 version. The problem is that the controller is not capable of the absolute direct communication that the software needs to work, or it just doesn't connect fast enough. This would be a great example of why Windows on a USB would be great, since you could just boot it. But then MS wouldn't be able to make its billions. So we lose.
I'd try VMWare and KVM to see if they do any better. I'm not sure if WINE supports USB passthrough or not. Otherwise try to find a Windows box you can use.
crispy-cat said:
The USB controller is part of VirtualBox. I think you need to download and install the extensions pack for the USB 2.0 version. The problem is that the controller is not capable of the absolute direct communication that the software needs to work, or it just doesn't connect fast enough. This would be a great example of why Windows on a USB would be great, since you could just boot it. But then MS wouldn't be able to make its billions. So we lose.
I'd try VMWare and KVM to see if they do any better. I'm not sure if WINE supports USB passthrough or not. Otherwise try to find a Windows box you can use.
Click to expand...
Click to collapse
Thanx crispy-cat,
I now understand what you mean. My V-Box is broken and won't start up anymore so it's time to try out the alternatives or install V-Box again ;-)
If those options won't work I think the best solution is to buy Windows10 and install this on the computer. What are your ideas about the last option crispy-cat?
SakasakaHeyhey said:
Thanx crispy-cat,
I now understand what you mean. My V-Box is broken and won't start up anymore so it's time to try out the alternatives or install V-Box again ;-)
If those options won't work I think the best solution is to buy Windows10 and install this on the computer. What are your ideas about the last option crispy-cat?
Click to expand...
Click to collapse
Don't waste your money. Just download the ISO from here:
Download Windows 10 Disc Image (ISO File)
If your computer supports multiple SSDs, find one that works in it, and install it in the second slot. Otherwise, find the cheapest SSD you can that works and install it on there.
The reason I say to install on a separate disk is because resizing partitions can corrupt your data and make your computer unbootable, and Windows doesn't provide an option to install alongside your existing OS. By all means do not get rid of your existing OS.
crispy-cat said:
Don't waste your money. Just download the ISO from here:
Download Windows 10 Disc Image (ISO File)
If your computer supports multiple SSDs, find one that works in it, and install it in the second slot. Otherwise, find the cheapest SSD you can that works and install it on there.
The reason I say to install on a separate disk is because resizing partitions can corrupt your data and make your computer unbootable, and Windows doesn't provide an option to install alongside your existing OS. By all means do not get rid of your existing OS.
Click to expand...
Click to collapse
Hi crispy-cat,
Thanx for your advise and the link. I have a laptop with one SSD in it and there is no room for a second SSD.
I have external harddisks I use for storage (no SSD) and was thinking what is the best option for me:
1) Buy an external SSD for Windows. I am wondering if and how this will work. The OS on the laptop is Kubuntu. I can change the boot option in the Bios and select the SSD. Because the OS is on the SSD and not on the laptop do I have access to the USB ports on the laptop via Windows which runs on the SSD? The purpose is to connect the bricked phone to one of the USB ports and use the MSM tool to unbrick my device.
2) Buy a USB flash drive and write the ISO from your link to the flashdrive. Install Windows on the laptop via the flashdrive. This will overwrite the current OS. When I can unlock my phone in Windows with the MSM tool I can install Kubuntu back again on the laptop.
It is no problem for me to change the OS because I don't lose any files. Everything I need is on the external harddisks.
What are your ideas about this and is there another option available that could work for me?
Dualboot with Windows/Kubuntu is a alternatieve but can also be tricky.
SakasakaHeyhey said:
Hi crispy-cat,
Thanx for your advise and the link. I have a laptop with one SSD in it and there is no room for a second SSD.
I have external harddisks I use for storage (no SSD) and was thinking what is the best option for me:
1) Buy an external SSD for Windows. I am wondering if and how this will work. The OS on the laptop is Kubuntu. I can change the boot option in the Bios and select the SSD. Because the OS is on the SSD and not on the laptop do I have access to the USB ports on the laptop via Windows which runs on the SSD? The purpose is to connect the bricked phone to one of the USB ports and use the MSM tool to unbrick my device.
2) Buy a USB flash drive and write the ISO from your link to the flashdrive. Install Windows on the laptop via the flashdrive. This will overwrite the current OS. When I can unlock my phone in Windows with the MSM tool I can install Kubuntu back again on the laptop.
It is no problem for me to change the OS because I don't lose any files. Everything I need is on the external harddisks.
What are your ideas about this and is there another option available that could work for me?
Dualboot with Windows/Kubuntu is a alternatieve but can also be tricky.
Click to expand...
Click to collapse
External SSDs are generally rejected by Windows and you'd have to do some very complicated setup. If it's no big deal to reinstall Kubuntu, go with option 2. Just disconnect the drives your files are on before you install Windows.
crispy-cat said:
External SSDs are generally rejected by Windows and you'd have to do some very complicated setup. If it's no big deal to reinstall Kubuntu, go with option 2. Just disconnect the drives your files are on before you install Windows.
Click to expand...
Click to collapse
Thanks for your help friend.
crispy-cat said:
So, my phone's bricked - it won't boot, just brings up fastboot. As the solution to this problem appears to be to use the MSM tool to do an "actual" factory reset, I downloaded the MSM tool, and the decrypted ROM from this link: https://androidfilehost.com/?fid=8889791610682918291.
First I tried this on a Windows 7 VirtualBox VM (I use Ubuntu on my actual computer). The drivers didn't even install right it seems, and the device (in EDL mode) wasn't even recognized. Then I tried it on my mom's Windows 10 laptop. MSM never showed the device as connected. I think possibly the lack of a USB 2 port could be the cause.
Finally I set up a basic VM with Windows 10 and a USB 2 controller, and it worked-ish. MSM recognized the device, showed it as connected and started doing its thing, but stopped at "Sahara Communication failed". What is preventing it from getting past this? I'm using the cable provided in the box. Everything is recognized correctly. I've retried multiple times but still the same result.
SUCCESS!
I had a spare laptop lying around, and it has USB 2 ports. I loaded WIndows 10 onto it and tried the MSM from there -- AND IT WORKED!
As much as I hate Qualcomm for their monopolistic business practices, I thank them for EDL mode. I also thank OnePlus for somehow failing to prevent the MSM tool from entering the hands of the public every time, and @Some_Random_Username for trafficking this good. Yeet!
Click to expand...
Click to collapse
In msm tool its showing sahara communication problom..
Please help me
Nafih424 said:
In msm tool its showing sahara communication problom..
Please help me
Click to expand...
Click to collapse
Are you using the cable that came with the phone?
crispy-cat said:
Are you using the cable that came with the phone?
Click to expand...
Click to collapse
Yes same cable.
I'm not sure what's wrong then, sorry. Maybe someone who knows more about this can help.
Hello, having same problem here.
I have a Op 6T and after trying to install twrp as a system app, it kept me boot-failing twrp over and over again with screen flashing then immediately shutting down, now my phone is unable to boot with volume and power button, and I can't even see it with fastboot command, even though my desktop sees it..
Same issue. was someone able to resolve this?
I got my OnePlus 7 to be seen on virtualbox but driver shows exclamation mark on guest windows 10 OS.
crispy-cat said:
So, my phone's bricked - it won't boot, just brings up fastboot. As the solution to this problem appears to be to use the MSM tool to do an "actual" factory reset, I downloaded the MSM tool, and the decrypted ROM from this link: https://androidfilehost.com/?fid=8889791610682918291.
First I tried this on a Windows 7 VirtualBox VM (I use Ubuntu on my actual computer). The drivers didn't even install right it seems, and the device (in EDL mode) wasn't even recognized. Then I tried it on my mom's Windows 10 laptop. MSM never showed the device as connected. I think possibly the lack of a USB 2 port could be the cause.
Finally I set up a basic VM with Windows 10 and a USB 2 controller, and it worked-ish. MSM recognized the device, showed it as connected and started doing its thing, but stopped at "Sahara Communication failed". What is preventing it from getting past this? I'm using the cable provided in the box. Everything is recognized correctly. I've retried multiple times but still the same result.
SUCCESS!
I had a spare laptop lying around, and it has USB 2 ports. I loaded WIndows 10 onto it and tried the MSM from there -- AND IT WORKED!
As much as I hate Qualcomm for their monopolistic business practices, I thank them for EDL mode. I also thank OnePlus for somehow failing to prevent the MSM tool from entering the hands of the public every time, and @Some_Random_Username for trafficking this good. Yeet!
Click to expand...
Click to collapse
Hello
I had the same issue now and don't have alternative laptop.
any solution to fix within the same laptop?
Thanks
Ak24607 said:
Hello
I had the same issue now and don't have alternative laptop.
any solution to fix within the same laptop?
Thanks
Click to expand...
Click to collapse
I had this issue before. You need to try a different cable/USB port.
FIX - PRESS (VOLUME+) + (VOLUME -) and connect the phone in EDL mode.
When you get the error, DONT DISCONNECT!!!!!!!!
Just PRess (VOLUME+) + Power Button and hold for few seconds.
IT DOES THE WORK!!!!!
yash.raj022 said:
FIX - PRESS (VOLUME+) + (VOLUME -) and connect the phone in EDL mode.
When you get the error, DONT DISCONNECT!!!!!!!!
Just PRess (VOLUME+) + Power Button and hold for few seconds.
IT DOES THE WORK!!!!!
Click to expand...
Click to collapse
I am using my Mac, and having windows using parallers. My device is getting detected in EDL. MSM shows that it's connected. But after 16s it says Sahara connection Failed. I was on siberia OS 12, wanted to revert back, and messed it up. Now the device doesn't boot up, can't access the fastboot as well - FASTBOOT is frozen.
Any help here would be great, else I might have to get a new phone
Related
I'm running OTA 4.0.3 (Acer_AV041_A500_1.033.00_PA_CUS1) rooted with I don't know what tool, but rooted after upgrading to 4.0.3, and using one of the tools found here which was the latest (at the time of rooting). The tablet has an "A500 Root Tools" app which has options to enter APX mode amongst other things.
I'm unable to get my Acer to connect to my PC via USB. I tried using both a mini(?)-usb cable and an A-A cable. My acer makes no notification, and there's no visible, or audible, evidence that anything was connected. USB Debugging enabled and disabled makes no difference. The tablet shows absolutely no sign that anything was plugged in. Nothing in notifications, nothing in any file managers.
Likewise on both a Windows 7 PC, and a Windows Vista machine. No little sound saying I plugged something in. Nothing listed in device manager. Nothing anywhere. The Win7 machine has the Acer drivers installed, as it is the machine I used to root it a few months ago.
Is there some weird ICS toggle that I need to perform to get this working? I know my USB ports are working as I've plugged in USB sticks and it mounts them without issue.
At the end of the day, I'm just wanting to flash my bootloader so that I can install CWM and a custom ROM. If there's a way to do that without needing my PC connected, that would make me equally happy.
Drivers
Anthony820 said:
I'm running OTA 4.0.3 (Acer_AV041_A500_1.033.00_PA_CUS1) rooted with I don't know what tool, but rooted after upgrading to 4.0.3, and using one of the tools found here which was the latest (at the time of rooting). The tablet has an "A500 Root Tools" app which has options to enter APX mode amongst other things.
I'm unable to get my Acer to connect to my PC via USB. I tried using both a mini(?)-usb cable and an A-A cable. My acer makes no notification, and there's no visible, or audible, evidence that anything was connected. USB Debugging enabled and disabled makes no difference. The tablet shows absolutely no sign that anything was plugged in. Nothing in notifications, nothing in any file managers.
Likewise on both a Windows 7 PC, and a Windows Vista machine. No little sound saying I plugged something in. Nothing listed in device manager. Nothing anywhere. The Win7 machine has the Acer drivers installed, as it is the machine I used to root it a few months ago.
Is there some weird ICS toggle that I need to perform to get this working? I know my USB ports are working as I've plugged in USB sticks and it mounts them without issue.
At the end of the day, I'm just wanting to flash my bootloader so that I can install CWM and a custom ROM. If there's a way to do that without needing my PC connected, that would make me equally happy.
Click to expand...
Click to collapse
Reinstall the Acer Drivers and also the Google drivers from the android sdk if u have that installed, if not use the adb_fast.zip attached. For you to successfully flash the BL do not underestimate the importance of having the drivers correctly installed - its the cause of 90% of the problems folks have had - my advice is to keep Device Manager open the whole time so you can see what is or isn't installing - dont proceed with the flash until you are sure they are - else you'll be looking at a downgrade to HC to fix things
you can also use Acer Recovery Installer from the market to install a custom recovery
While I appreciate your help, my issue is not drivers - Windows isn't loading the wrong drivers, or no drivers at all. Windows is showing no sign at all, at all, in device manger, any where, that a tablet has been plugged in. Like wise, the tablet gives ZERO notifications on being plugged in to a PC. Nothing. No sounds. No notification. Nothing.
I was originally using the micro(?) usb slot, and it was not working. I assumed that USB slot was dead. So I went and bought a USB A-A cable - after testing the normal USB slot and established it works - and it, too, does absolutely nothing when plugging the device into a PC.
I've since tested with an Ubuntu 12.04 machine as well. dmesg lists nothing.
Anthony820 said:
While I appreciate your help, my issue is not drivers - Windows isn't loading the wrong drivers, or no drivers at all. Windows is showing no sign at all, at all, in device manger, any where, that a tablet has been plugged in. Like wise, the tablet gives ZERO notifications on being plugged in to a PC. Nothing. No sounds. No notification. Nothing.
I was originally using the micro(?) usb slot, and it was not working. I assumed that USB slot was dead. So I went and bought a USB A-A cable - after testing the normal USB slot and established it works - and it, too, does absolutely nothing when plugging the device into a PC.
I've since tested with an Ubuntu 12.04 machine as well. dmesg lists nothing.
Click to expand...
Click to collapse
open a command prompt on yr adb folder and run "adb devices" what do u see?
List of devices attached.. then nothing but my prompt.
Anthony820 said:
List of devices attached.. then nothing but my prompt.
Click to expand...
Click to collapse
and the adb interface driver thats not showing in device manager?? and you have the acer drivers installed??
All the signs are pointing to no drivers, failing that its sounding like a hardware issue either yr tab or cable - can u try on another pc/laptop?
Tested it on a Win 7 Dell, on a Vista Dell, and on an Ubuntu 12.04 Compaq. None show any sign of the device being connected.
I know my *two* micro USB cords work as my Nooks (color and tablet) have no problem with them. I know the large USB slot works as I've plugged in a keyboard and a USB memory stick and both are immediately detected by android.
I've also done a factory reset on the tab. Problem persists, obviously.
I'm actually setting up stock Win7 on another laptop right now. When it's complete I'll install acer drivers and plug in the tablet. It will be the only USB device, let alone android, to ever be plugged in to it.
Anthony820 said:
Tested it on a Win 7 Dell, on a Vista Dell, and on an Ubuntu 12.04 Compaq. None show any sign of the device being connected.
I know my *two* micro USB cords work as my Nooks (color and tablet) have no problem with them. I know the large USB slot works as I've plugged in a keyboard and a USB memory stick and both are immediately detected by android.
I've also done a factory reset on the tab. Problem persists, obviously.
I'm actually setting up stock Win7 on another laptop right now. When it's complete I'll install acer drivers and plug in the tablet. It will be the only USB device, let alone android, to ever be plugged in to it.
Click to expand...
Click to collapse
cool let us know how u go....oh dont forget the adb drivers too
Same. I feel like it's something on the tablet rather than the PCs. But I don't know how to get 100% stock again without being able to have a PC connection.
Anthony820 said:
Same. I feel like it's something on the tablet rather than the PCs. But I don't know how to get 100% stock again without being able to have a PC connection.
Click to expand...
Click to collapse
The tool you used to root it (icsRoot) also has an unroot tool, which you could have used...I have tried to unroot manually which wasnt easy as I had a pre-rooted rom and I had real trouble getting rid of superuser, but in your case it may be a bit different....Sorry can't give you much help in the unrooting ics dept. Maybe try flashing acer stock rom??? or starting a new thread??
Did you ever solve this problem, I'm pulling my hair out with the same thing.
irishmoe said:
Did you ever solve this problem, I'm pulling my hair out with the same thing.
Click to expand...
Click to collapse
are you trying to flash something or do you mean when you connect yr tab
windowz explorer doesnt show your int/ext storage??
more info needed, what rom and bootloader, what OS on yr pc can u try on a different one, try a different cable and usb port..
have you run the acer drivers setup.exe
did u install the android usb ones
have u opened a command prompt from the folder where adb.exe is and run "adb devices"...does a number show??
when u have device manager open and connect yr cable do you see the drivers install. If they are there then uninstall them, disconnect yr cable and clean boot and reconnect.
If they do not install then manually install by pointing them to the folder you extracted the zip to...for the acer ones, just point it to your c: drive
If windows trys to install them, stop the hardware wizard from searching windows update and manually install them yourself.
If you've tried to flash the bootloader and it hasnt completed for what ever reason - you can strike issues such as yours - again, uninstall, clean boot, reconnect, manual install
I have my own thread here
http://forum.xda-developers.com/showthread.php?t=1776448
but came across this one and thought I'd ask if there was any solution found.
irishmoe said:
I have my own thread here
http://forum.xda-developers.com/showthread.php?t=1776448
but came across this one and thought I'd ask if there was any solution found.
Click to expand...
Click to collapse
ok m8, i havng a look at it now....when u connect to yr pc does win explorer show u yr internal/external storage ok??
Have you tried an app like USB host controller to check the connection on the tablets side?
a.child said:
Have you tried an app like USB host controller to check the connection on the tablets side?
Click to expand...
Click to collapse
I regularly use a memory stick in the usb port so I reckon it's fine
what about the micro-usb port?
a.child said:
what about the micro-usb port?
Click to expand...
Click to collapse
Lost the cable so using the regular port
irishmoe said:
Lost the cable so using the regular port
Click to expand...
Click to collapse
I replied earlier in the other thread m8
U must use the micro USB
irishmoe said:
Lost the cable so using the regular port
Click to expand...
Click to collapse
dibb_nz said:
I replied earlier in the other thread m8
U must use the micro USB
Click to expand...
Click to collapse
That's correct, a straight USB "A to A" won't work. Further, I discovered something else; not all micro-usb cables are created equally! I was using a cable that worked fine on my Thunderbolt phone, would not work at all on my A500. Turned out there's some enhancements to the pinouts on the newer micro-usb devices. So the lesson here is go with the cable that came with the device if at all possible.
Seriously though, give a different micro-usb cable a shot; they're pretty cheap around the interwebz.
So after flashing the new lollipop update I found myself stuck in a bootloop unable to get into the android operating system at all. I used flashboot and the intel flash tool to try and restore to an older ROM. It forze at 91% with an "error:unable to mount /data" I then used the root tool to try and sideload and install the update.zip from adb shell. No luck. When I rebooted I got to a strange efi menu. Looked around, and it gives me the option to install with with windows?
Anyone have any ideas. I'm waiting for radio shack to open, its the only local place that sells USB otg cables locally.
Here are the photos
njking25 said:
Here are the photos
Click to expand...
Click to collapse
njking25 said:
So after flashing the new lollipop update I found myself stuck in a bootloop unable to get into the android operating system at all. I used flashboot and the intel flash tool to try and restore to an older ROM. It forze at 91% with an "error:unable to mount /data" I then used the root tool to try and sideload and install the update.zip from adb shell. No luck. When I rebooted I got to a strange efi menu. Looked around, and it gives me the option to install with with windows?
Anyone have any ideas. I'm waiting for radio shack to open, its the only local place that sells USB otg cables locally.
Click to expand...
Click to collapse
That is something interesting. It is asking which os to boot to, not install.
I'd like to know how you got into the bios? I am looking for a way to install Linux....
Sent from my YOGA Tablet 2-1050F using Tapatalk
njking25 said:
Here are the photos
Click to expand...
Click to collapse
Did you get this figured out?
I can see "fast boot" enabled. Have You tried to switch it off? any other menu is displayed?
Have You tried to "power+vol down" on it?
I've tried a few ways to get into the BIOS shown... all failed.
Maybe the only way to trigger the BIOS to show is to fully wipe/format the internal storage so the BIOS can't pick up droidboot or anything else. Quite risky though if it isn't the way.
I'm in no way telling anyone to do this and I have not tried it myself. I'd be curious to hear from any advanced users if they have ever completely wiped the internal memory and what options would be available to restore if things did go wrong.
zach181 said:
I've tried a few ways to get into the BIOS shown... all failed.
Maybe the only way to trigger the BIOS to show is to fully wipe/format the internal storage so the BIOS can't pick up droidboot or anything else. Quite risky though if it isn't the way.
I'm in no way telling anyone to do this and I have not tried it myself. I'd be curious to hear from any advanced users if they have ever completely wiped the internal memory and what options would be available to restore if things did go wrong.
Click to expand...
Click to collapse
This guy seems to have stumbled on it also. I flashed the stock kk firmware and I am trying to do it but can't get Lollipop update to work. But it won't boot after it fails so I am reflashing KK again.
http://forum.xda-developers.com/showpost.php?p=60490907&postcount=578
Thanks for the link workdowg,
I'm still trying to work out how they did it. Could do with a step by step and whatever files needed uploaded and linked to. Also the bit about not using windows startup programs.
zach181 said:
Thanks for the link workdowg,
I'm still trying to work out how they did it. Could do with a step by step and whatever files needed uploaded and linked to. Also the bit about not using windows startup programs.
Click to expand...
Click to collapse
If you try it do let me know. I need to get into the bios to get started on a dual boot to Linux on this bad boy...
I will let you know.
I just asked for the OP to clarify a few things before I go ahead. I may try Linux first with Windows 8/10 being the final install.
So... conclusion. we have to damage firmware to boot efi...
If we could swap img file before upload to tab (during this 25 second wait) we could make windows installation possible. Am i right?
zach181 said:
I will let you know.
I just asked for the OP to clarify a few things before I go ahead. I may try Linux first with Windows 8/10 being the final install.
Click to expand...
Click to collapse
@social-design-concepts suggested we should try to change the boot order using efibootmgr. I've been communicating with him. Here is the post in the Venue thread... http://forum.xda-developers.com/show...postcount=2083
Links giving 404
zach181 said:
Links giving 404
Click to expand...
Click to collapse
here it is again... http://forum.xda-developers.com/showpost.php?p=61108700&postcount=2083 it got truncated.
Thanks workdowg.
It seems it's not as clear cut as first thought. Mind you, I didn't expect it to be. I did try a HP keyboard with OTG in Android and that got picked up ok (No lights on keyboard)
I'm a bit in the same mind as Social-Design. I'd rather have a definite way to restore Android from a totally blank internal drive before I have a go. Just up to page 214 in the thread so it may be covered later.
UEFI soft brick?
Hi guys,
I accidentely tried to use the firmware on my 1050 as described in this thread. I can indeed load the UEFI BIOS with all its settings (even though most don't do anything). But unfortunately, I cannot load any OS. I always get the error "EFI Harddrive failed" - meaning it cannot boot fomr hardrive.
I have used an externally powered USB-HUB with mouse, keyboard and USB-Stick and connected to the 1050 via OTG-cable. If the stick is bootabnle with GPT x64 then it will boot from that stick. All 64bit windows versions that I tried failed to install with "ACPI_BIOS_ERROR". 32bit windows would not start, because the GPT is 32bit and the BIOS does not recognise it.
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Unfortunately, I am running a bit out of ideas of what to do in order to get a normal system (or firmware) back. ADB-drivers obviously don't work (the Intel SoC driver is installed as well), so I cannot use the Phone Flash Tool.
Any ideas would be greatly appreciated.
Yosha1 said:
Hi guys,
I accidentely tried to use the firmware on my 1050 as described in this thread. I can indeed load the UEFI BIOS with all its settings (even though most don't do anything). But unfortunately, I cannot load any OS. I always get the error "EFI Harddrive failed" - meaning it cannot boot fomr hardrive.
I have used an externally powered USB-HUB with mouse, keyboard and USB-Stick and connected to the 1050 via OTG-cable. If the stick is bootabnle with GPT x64 then it will boot from that stick. All 64bit windows versions that I tried failed to install with "ACPI_BIOS_ERROR". 32bit windows would not start, because the GPT is 32bit and the BIOS does not recognise it.
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Unfortunately, I am running a bit out of ideas of what to do in order to get a normal system (or firmware) back. ADB-drivers obviously don't work (the Intel SoC driver is installed as well), so I cannot use the Phone Flash Tool.
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
You can get it to boot from USB? Get someone with to use tethered twrp and get a backup of the esp and fastboot partitions.
I have 2 things you can try if the goal is getting back to booting stock Android.
Yosha1 said:
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
Have You tried booting any x64 linux iso from flash drive?
dreamnewbie said:
Have You tried booting any x64 linux iso from flash drive?
Click to expand...
Click to collapse
Thank you for your fast reply.
I just tried that with an Ubuntu Desktop Distro. It boots up from teh USB drive, keyboard and mouse are present. Wifi, sound, touch don't work but I can see the internal Harddrive and the sdcard in the file exsplorer.
Yosha1 said:
Thank you for your fast reply.
I just tried that with an Ubuntu Desktop Distro. It boots up from teh USB drive, keyboard and mouse are present. Wifi, sound, touch don't work but I can see the internal Harddrive and the sdcard in the file exsplorer.
Click to expand...
Click to collapse
extract and dd this to a usb drive and see if it is able to boot it View attachment 3415895 if it successfully boots replace the fastboot.img thats on the thumbrive with one for your devices and see if it boots. if your fastboot.img is named droidboot.img rename it to fastboot.img.
If you can successfully get your devices droidboot/fastboot.img to load you can then disconnect the usb-otg cable and reconnect it to your PC and use the phone flash tools to restore your device completely.
So, I know I botched the upgrade from Windows 8.1 to Windows 10 and when I boot the Trio PRO-8 it automatically goes to a Windows error screen with "press the Windows key to enter UEFI firmware settings. Error Code: 0x0000225"
There are several places to go, that tell you how to factory reset, enter boot mode on the Trio Stealth, but I have yet to find anything for the Trio PRO-8
Has anyone used or modified this device? I've contacted Trio, but I keep getting the run around because I mentioned Windows 10, they think I am still trying to install Windows 10 and keep telling me to call Microsoft. Microsoft can't help me with this issue, or I would have already known about it. There is no "Windows Key" on this tablet. All I want to do is figure out how to re-load either the Factory installed OS and start from the beginning, or install a fresh copy from the SD card.
The tablet itself, before I botched the upgrade WAS a decent little table especially getting it on sale on top of it being low cost, up until this point I had been using it regularly for the last 6 or 7 months without issue, maybe longer, can't remember how long I've had it now.
At any rate, I appreciate your time for reading this, and would be grateful to any help to get this thing back up and running before my Grandson comes up to visit next month, when he's here to visit, it is his movie player
With an adapter, I was able to hook up a USB keyboard, even pressing the Windows key did nothing. However, after trying every F key at boot, and a few others, I found that the [Esc] will get you in to the system's UEFI bios. I've been experimenting with settings. I left my card reader at work, but tomorrow I'm going to make the SD card bootable and put a LiNUX distro on it and install that over Windows. Since I don't know what my Windows 8.1 key was for this device.
Going this route because the keyboard has to be hooked up with an adapter and there is only one port. I may try a powered USB hub and see if I can boot from USB with the keyboard installed and a flash drive.
Das Faust said:
With an adapter, I was able to hook up a USB keyboard, even pressing the Windows key did nothing. However, after trying every F key at boot, and a few others, I found that the [Esc] will get you in to the system's UEFI bios. I've been experimenting with settings. I left my card reader at work, but tomorrow I'm going to make the SD card bootable and put a LiNUX distro on it and install that over Windows. Since I don't know what my Windows 8.1 key was for this device.
Going this route because the keyboard has to be hooked up with an adapter and there is only one port. I may try a powered USB hub and see if I can boot from USB with the keyboard installed and a flash drive.
Click to expand...
Click to collapse
This post is probably no longer in the right forum now, especially if I outline the procedure I used to get LiNUX on to this Intel based tablet.
Das Faust said:
This post is probably no longer in the right forum now, especially if I outline the procedure I used to get LiNUX on to this Intel based tablet.
Click to expand...
Click to collapse
No luck as of yet:
- Can't get it to boot off of USB
- Can't get it to boot of the Micro SD card
- Will only boot to the Windows error message
- will keep trying
hi
Amigo gets a multi USB otg, a mini keyboard with pad and usb wireless connector. I have the same tablet trio pro 8 upgrade to windows 10 as well. I have another problem with the various touch screen controllers. I can not make it work. I am using it with the keyboard but I would like to use it free without loading keyboard.
Already solved your problem?
My nexus 4 went crazy last week. I was trying out Lucky Patcher on one of my apps (I wanted to develop something against it). But since then, my phone can't connect to my computer: According to the computer, "The last connected device malfunctioned." I went to recovery and wiped EVERYTHING(including internal storage). It worked a little and I got another ROM on, but now its happened again and I can't connect it to the computer AT ALL. I have no ROM and my phone is now literally, a(n almost) useless brick. Recovery works, but without a ROM on it I can't do anything. I haven't been able to use it and it's driving me crazy. Can anybody please help?My computer first gave me error code
Using: twrp-3.0.0-0, Windows 10.0.10586(You can check it out in a terminal: Just type in "cmd")
Was using: CataclysmMod-Marshmallow-Dec_08_2015-MAKO-MMB29K_Stable, Click here for details
Lucky Patcher v6.0.8, Layers, Titanium Backup (Among other things)
Uninstall your nexus drivers from Windows, reboot, and install them again. Also try a different USB port and a USB cable, and if nothing helps, a different computer. I remember that one day I wasn't able to flash /system partition of a stock ROM from fastboot because it gave me a strange error. Since then, everyhing is ok.
When you manage to go in fastboot mode, flash a stock image (using erase command for each partition), and only then flash a custom ROM. In this way everything will be nice and clean.
I tried doing what you said, but:
Windows Explorer said:
"USB device not recognized:
The last USB device you connected to this computer malfunctioned, and Windows cannot recognize it."
This is when I uninstalled and reinstalled the drivers
Try a window 7 machine? Try different USB cables and USB ports?
audit13 said:
Try a window 7 machine? Try different USB cables and USB ports?
Click to expand...
Click to collapse
For some odd reason, the drivers I'm installing(different computer) for fastboot aren't working.
Problem is:
When I try 'installing legacy hardware':
The driver error code: 'The device cannot start(code 10)'
When I try Updating device driver software:
With the 'Have disk' method:
Error: The driver is not correct. Please check if the driver is for windows x64 operating systems.
With the direct 'browse for folders on my computer' method:
Windows has 'determined' that your driver is up to date
Can anybody help? I was using the Google USB driver (click here for link)
Windows x64 10.0.10586
Are you using a win 7 machine? I have never had problems with fastboot on a win7 machine, only win8 and 10.
Maybe these will work: http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339 ?
This is win10
AANNDD I'm having problems with the Universal naked drivers: check it out (Click here)
THANK YOU EVERYBODY for your help and assistance, my phone is now fixed, reverted to its unrooted form. I'm just so relived it's fixed!!!
How did you fix the phone? Share your solution as it may help other XDA members with a similar issue.
Use the Qualcomm HUSB method, I fixed my phone same way too.
Sent from my Nexus 4 using XDA-Developers mobile app
I'm trying to use LG PC Suite and LG Bridge on a laptop running Windows 7 x64 Pro. I have updated the chipset with the latest driver, but every time I try to install the LG drivers, the SM Bus Controller fails to install. The PC cannot see the device, even though I have switched USB mode to file transfer. I have a Mac as well, and the same thing happens there (not recognizing the device is connected via USB). Is the software just way out of date and not yet compatible with the V20, or is there a fix that needs to happen. I'm perfectly comfortable using the command line/terminal or hacking the registry, if that's what it takes...
Thanks to anyone that can help!
I did remove the SM Bus Controller from device manager and then re-installed the LG device driver. It did not attempt to reinstall SM Bus drivers, but instead installed MTP drivers successfully. I had high hopes after that, but it's still not working. Sigh.
bgibson72 said:
I'm trying to use LG PC Suite and LG Bridge on a laptop running Windows 7 x64 Pro. I have updated the chipset with the latest driver, but every time I try to install the LG drivers, the SM Bus Controller fails to install. The PC cannot see the device, even though I have switched USB mode to file transfer. I have a Mac as well, and the same thing happens there (not recognizing the device is connected via USB). Is the software just way out of date and not yet compatible with the V20, or is there a fix that needs to happen. I'm perfectly comfortable using the command line/terminal or hacking the registry, if that's what it takes...
Thanks to anyone that can help!
Click to expand...
Click to collapse
What are you trying to accomplish?
Have you installed minimal adb\fastboot?
Frankly, I don't use Windows or Mac so I am next to no help there.
'Sudo pkg install android-tools-adb android-tools-fastboot' was all I've needed to do.
Is your usb a known good cord? Verify this first. Then, Windows device manager, plug in your phone, watch for something to show on device manager. Click on device, double check there that everything shows as working properly?
If phone is not showing up on a number of computers, make sure USB cable is good.
elijah420 said:
What are you trying to accomplish?
Have you installed minimal adb\fastboot?
Frankly, I don't use Windows or Mac so I am next to no help there.
'Sudo pkg install android-tools-adb android-tools-fastboot' was all I've needed to do.
Is your usb a known good cord? Verify this first. Then, Windows device manager, plug in your phone, watch for something to show on device manager. Click on device, double check there that everything shows as working properly?
If phone is not showing up on a number of computers, make sure USB cable is good.
Click to expand...
Click to collapse
I have adb and fastboot both. I want to connect to the PC/Mac for purposes of synching/sharing music, photos, etc. I could use linux too, but I don't have an VM's or a box spun up with anything atm. Yes, the cord I'm using is a good cord. I can see the internal and SD card when I connect, just can't use the LG apps. Oddly enough, there wasn't anything showing with the yellow sign under Device Manager. I'm guessing it's just a compatibility issue and I should just forget about it and just push files to my device with adb. Oh well--I thought it was worth a shot.
bgibson72 said:
I have adb and fastboot both. I want to connect to the PC/Mac for purposes of synching/sharing music, photos, etc. I could use linux too, but I don't have an VM's or a box spun up with anything atm. Yes, the cord I'm using is a good cord. I can see the internal and SD card when I connect, just can't use the LG apps. Oddly enough, there wasn't anything showing with the yellow sign under Device Manager. I'm guessing it's just a compatibility issue and I should just forget about it and just push files to my device with adb. Oh well--I thought it was worth a shot.
Click to expand...
Click to collapse
I understand now. I don't think I can help you there. I run an owncloud instance, and just back all my hooey up there.. manually tho. Sorry dude.
elijah420 said:
I understand now. I don't think I can help you there. I run an owncloud instance, and just back all my hooey up there.. manually tho. Sorry dude.
Click to expand...
Click to collapse
It's cool, thanks anyway. Just trying to simplify things. Don't ask why I thought the OEM's software was gonna solve that, lol.
Well, tbf, even though I don't use it (simply because I dislike vendor lock in - owncloud or a sftp session is mostly hardware agnostic.) I do understand the idea that one should expect the **** that come on the phone to work properly. It *should* be a selling point - 'our apps work for their stated purpose!'