Has anyone managed to get ABD sideload working from stock recovery?
I'm trying to sideload the latest OTA.
I have ADB up and running fine when the N9 is fully booted, but when I drop into recovery and select the option to sideload via ADB, I get the Windows "chime" for a new device, and unknown device (Volantis) appears in the device manager, for which I can find no driver.
No driver means no ADB and thus no sideload.
Thanks,
Hi, replace the original android_winusb.inf file with this modified one in your google usb drivers folder. Right click on it and select install.
Modified it for myself right now, because I had exactly the same problem like you.
Please let me know if it was successful...
daniii88 said:
Hi, replace the original android_winusb.inf file with this modified one in your google usb drivers folder. Right click on it and select install.
Modified it for myself right now, because I had exactly the same problem like you.
Please let me know if it was successful...
Click to expand...
Click to collapse
Thanks for trying but it doesn't work for me, when I try to install I get an error dialog :-
"The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tampered with"
I'm also getting this problem. Any solution?
I have same problem... waiting for solution....
bobjbain said:
Thanks for trying but it doesn't work for me, when I try to install I get an error dialog :-
"The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tampered with"
Click to expand...
Click to collapse
I had the same issue and have now successfully been able to sideload (Windows 8.1).
The original issue seems to be that the latest google driver I downloaded did not have the correct device id in the android_winusb.inf for the nexus 9 when in recovery mode (though the driver did work for issuing adb commands to unlock the bootloader; I guess the hardware id is different when connected in adb recovery mode?). The file daniii88 provided presumably fixes this in the same way I did, by adding the device id reported under device manager to the generic nexus devices listed in the android_winusb.inf file as follows:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
I did this under both the 32 and 64 bit headers just in case. I made an account just to post this solution, so I can't post links, but searching for "nexus 7 adb recovery driver" shows the same thing happened with the nexus 7 at one point.
Now, with the modified version of the android_winusb.inf file windows won't let the driver install because the driver signature does not match since it's been altered. The trick to forcing windows to use the driver anyways is to reboot windows in "disable driver signature verification" mode. Search for "how to disable driver signature verification on 64 bit windows 8.1 so that you can install unsigned drivers". Once rebooted, reinstall the altered driver under device manager (I did this while the device was in recovery mode waiting for adb sideload). Windows will warn you along the lines of the driver has been tampered with, but will allow you to use it. The driver should successfully install and the device should appear under "adb devices" from the command line. Furthermore, sideload should now work.
Hopefully this helps anyone else encountering this.
ManBearBull said:
I had the same issue and have now successfully been able to sideload (Windows 8.1).
The original issue seems to be that the latest google driver I downloaded did not have the correct device id in the android_winusb.inf for the nexus 9 when in recovery mode (though the driver did work for issuing adb commands to unlock the bootloader; I guess the hardware id is different when connected in adb recovery mode?). The file daniii88 provided presumably fixes this in the same way I did, by adding the device id reported under device manager to the generic nexus devices listed in the android_winusb.inf file as follows:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
I did this under both the 32 and 64 bit headers just in case. I made an account just to post this solution, so I can't post links, but searching for "nexus 7 adb recovery driver" shows the same thing happened with the nexus 7 at one point.
Now, with the modified version of the android_winusb.inf file windows won't let the driver install because the driver signature does not match since it's been altered. The trick to forcing windows to use the driver anyways is to reboot windows in "disable driver signature verification" mode. Search for "how to disable driver signature verification on 64 bit windows 8.1 so that you can install unsigned drivers". Once rebooted, reinstall the altered driver under device manager (I did this while the device was in recovery mode waiting for adb sideload). Windows will warn you along the lines of the driver has been tampered with, but will allow you to use it. The driver should successfully install and the device should appear under "adb devices" from the command line. Furthermore, sideload should now work.
Hopefully this helps anyone else encountering this.
Click to expand...
Click to collapse
After you did this. You were able to side load the OTA even with the non upgraded recovery?
Sent from my Nexus 7
109
ram130 said:
After you did this. You were able to side load the OTA even with the non upgraded recovery?
Click to expand...
Click to collapse
Sorry, should have said I was already on the upgraded (LRX21Q) recovery before going through these steps. The unaltered driver i initially used worked to communicate with the nexus 9 when booted or at the bootloader screen, but not when I was in recovery. Therefore i was able to unlock my bootloader and update the recovery with unaltered drivers, but had to change the driver to get adb to work when in recovery.
ManBearBull said:
I had the same issue and have now successfully been able to sideload (Windows 8.1).
The original issue seems to be that the latest google driver I downloaded did not have the correct device id in the android_winusb.inf for the nexus 9 when in recovery mode (though the driver did work for issuing adb commands to unlock the bootloader; I guess the hardware id is different when connected in adb recovery mode?). The file daniii88 provided presumably fixes this in the same way I did, by adding the device id reported under device manager to the generic nexus devices listed in the android_winusb.inf file as follows:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
I did this under both the 32 and 64 bit headers just in case. I made an account just to post this solution, so I can't post links, but searching for "nexus 7 adb recovery driver" shows the same thing happened with the nexus 7 at one point.
Now, with the modified version of the android_winusb.inf file windows won't let the driver install because the driver signature does not match since it's been altered. The trick to forcing windows to use the driver anyways is to reboot windows in "disable driver signature verification" mode. Search for "how to disable driver signature verification on 64 bit windows 8.1 so that you can install unsigned drivers". Once rebooted, reinstall the altered driver under device manager (I did this while the device was in recovery mode waiting for adb sideload). Windows will warn you along the lines of the driver has been tampered with, but will allow you to use it. The driver should successfully install and the device should appear under "adb devices" from the command line. Furthermore, sideload should now work.
Hopefully this helps anyone else encountering this.
Click to expand...
Click to collapse
So, the original attachment works properly, it was unsigned driver verification that was stopping it being installed, should have realised that from the start, thanks for pointing me in the right direction.
ram130 said:
After you did this. You were able to side load the OTA even with the non upgraded recovery?
Sent from my Nexus 7
Click to expand...
Click to collapse
No, it was telling me my old version isn't what it was expecting. I must be suffering from the recovery not being updated properly "bug".
My build.prop definitely has the right release keys in it.
Once question for those that know, in the update package there is a metadata file which contains :-
Code:
post-build=google/volantis/flounder:5.0/LRX21Q/1573789:user/release-keys
post-timestamp=1415397802
pre-build=google/volantis/flounder:5.0/LRX21L/1546449:user/release-keys
pre-device=flounder
Can we just not change the pre-build to that that is in the error message? (flounder:L/LFW73W/1491895:user/release-keys)??
So I replaced the android_winusb with the file provided and rebooted without driver verification mode. But it is still not working.
Under device manager it still shows the exclamation mark on Volantis. Did I miss a step?
ForcedZucchini said:
So I replaced the android_winusb with the file provided and rebooted without driver verification mode. But it is still not working.
Under device manager it still shows the exclamation mark on Volantis. Did I miss a step?
Click to expand...
Click to collapse
Maybe you have another Device ID... try to follow this procedure http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
This is Googles fault:
You remember the very first update you received during setup?
Yeah, and Google made a mistake with this update: They updated the system, but not the recovery, which means, there is now a version conflict between the recovery and the system, which prevents OTAs from installing.
You can't do anything about it until Google fixes this with another Update, except flashing the new recovery from the image.
ForcedZucchini said:
So I replaced the android_winusb with the file provided and rebooted without driver verification mode. But it is still not working.
Under device manager it still shows the exclamation mark on Volantis. Did I miss a step?
Click to expand...
Click to collapse
Have you tried updating the driver in device manager?
ForcedZucchini said:
So I replaced the android_winusb with the file provided and rebooted without driver verification mode. But it is still not working.
Under device manager it still shows the exclamation mark on Volantis. Did I miss a step?
Click to expand...
Click to collapse
After replacing the android_winusb file and rebooting the PC without driver verification mode, did you go back into Device Manager and update the driver using the modified driver version for ADB? I manually entered the device ID info into the winusb file instead of using the provided file, so I'm not entirely sure that the process is the same, but it seems like it should work.
1. Replace the android_winusb file with the attached version. If that doesn't work, open the file in notepad and manually enter the device id IAW ManBearBull's post;
2. Reboot without driver verification mode; and
3. Go into device manager and update the ADB driver with the modified driver file.
Finally worked, running "R" firmware now. There is not even een factory image available, just this OTA upgrade R-from-Q.
Cannot imagine why the device in recoverymode is not recognised ( unknown device Volantis ) and we need to play "dirty" to install the driver.
Seems so "immature" from Google.
Different Hardware ID?
So I replaced the android_winusb and it's still not letting me see the device in adb in fastboot. I can see it when it boots up normally. However, I am seeing that when I boot into fastboot, it gives me a hardware id of USB\VID_18D1&PID_4EE0 and not USB\VID_18D1&PID_D001 that was said in previous posts. Right now in Device Manager it's seeing the tablet as an "Android Bootloader Interface" instead of the CompositeAdbInterface I want. Should I change the inf file to put that hardware id as a CompositeAdbInterface instead of a SingleBootLoaderInterface like it currently is?
lotrfan18 said:
So I replaced the android_winusb and it's still not letting me see the device in adb in fastboot. I can see it when it boots up normally. However, I am seeing that when I boot into fastboot, it gives me a hardware id of USB\VID_18D1&PID_4EE0 and not USB\VID_18D1&PID_D001 that was said in previous posts. Right now in Device Manager it's seeing the tablet as an "Android Bootloader Interface" instead of the CompositeAdbInterface I want. Should I change the inf file to put that hardware id as a CompositeAdbInterface instead of a SingleBootLoaderInterface like it currently is?
Click to expand...
Click to collapse
That's because you're in bootloader not recovery, when you go into recovery and then do the "adb sideload" option that is when you get the D001 device ID.
I was able to resolve my problem, thanks for everyone's help.
I simply went into device manager>update driver software>browse my computer for driver software>let me pick>select "ADB Android Device"
After this I downloaded Minimal ADB and Fastboot from here http://forum.xda-developers.com/showthread.php?t=2317790 and it was able to work successfully.
Related
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Have you reviewed the jmztaylor method?
Have you reviewed this method?
http://forum.xda-developers.com/showthread.php?t=1905674
Worked for me after I grabbed the drivers from PDAnet.
I have one issue of Android is Updating stuck in loop that some others in that thread have sorted out but I can't quite get working yet!
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
same problem.
I am having the same exact problem. I have reviewed the jmz method and keep getting stuck in cmd saying path not specified. Any solutions. All steps have been followed to the letter.
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
cruise350 said:
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
This thread goes through doing it manually, it is written for Ubuntu(linux) but it can be used in windows as well, you just don't use sudo for the commands. Also the package in the following thread already has the updated gapps package that does away with the "android upgrading" on every boot.
http://forum.xda-developers.com/showthread.php?t=2016463
fast boot won't install
Had ''path not specified'' it gets to the if stuck here drivers aren't installed. A window pops up saying ''installing fast boot'' but then says it failed. Thats where im stuck.
4.1.1 OS
2.4 product version
Thinking the 2.4 update is a problem.
Any suggestions?
I know i'm years late here but I really HATE adb and esp. BAT files that are just suppose to do their thing........I'm hitting a wall with this Nabi 2 Bat file for TWRP / ROOT. I've used PDAnet plenty in the past for internet but never for the purpose of just getting drivers so I have no idea I hate that program too. ANYWHO , I'm getting "cannot find specified path" which I probably could fix if I ****ing knew which ****ing path it was looking for. SO if anyone could please enlighten me here , I've installed and uninstalled PDA net some 10 times now , with Samsung selected , with LG selected with OTHER selected , I cannot get this to work. I can do FASTBOOT devices , and poof it shows up , adb works fine all that , show the device but I cannot get this ****ing BAT all in one installion to work. I'm really just about to flash it all manually through ADB but I'd rather use the installer to make sure I get the random WINGS files removed or whatever. Any help would be great , thanks.
I have a HTC Google Nexus 9 tablet. I recently received the update to Android 6.0.1 via the normal push notification. The update got stuck on ‘optimizing your apps 1 of 74’. It normally moves up in the numbers within minutes but it remained on ‘1 of 74’ for an entire night. So, the next morning I switched off by holding the power button.
The system still booted but soon enough I received error messages like ‘there is an internal error, contact the manufacturer’ and during the boot it says that my system was corrupted.
I decided on a factory reset. It went through with it. But when setting up the cleaned system, there is another problem: I can pick my language and connect to my WIFi without problem. But then it goes to a screen where it says ‘checking connection. This may take a while.’ It gets stuck there for several hours - so it is clearly faulty as I don’t think ‘a while’ means 12 hours and more. I also don’t think that the factory reset solved the problem anyway as I still receive error messages, hinting at a corrupted system, during and after the boot.
So, I decided to try to flash a system image.
I got the Minimal Android Debugging Bridge ADB and Fastboot on Windows 7 and Ubuntu,
Then I followed the Google developers instructions and downloaded Volantis MOB30D from there.
I also got Android drivers for Windows, but I’m not entirely certain if they are right.
When I connect the Nexus 9 to the Windows computer, I now see in Device manager: ASUS Android Devices -> Android ADB Interface
It’s not an ASUS tablet though and I can’t see the Nexus 9 in ‘Computer’ (it used to show up there as ‘Portable Media player’
Is it possible that I got the wronger drivers and if so, how would I install the correct ones?
Then I start the Nexus 9 and hold power and volume up down to get to the bootloader.
It says ‘Fastboot USB’
I also says ‘device state - locked’ . I can’t get to the system settings to do the OEM unlock as I’m stuck on ‘checking connection’ when I boot normally.
Then I opened ‘Minimal ADB and Fastboot’ on Windows and tried the following commands:
Fastboot flashing unlock
… and it says:
FAILED (remote not allowed)
Then …
Fastboot oem unlock
… and it says:
(bootloader) ability is 0
(bootloader) permission denied for this command
Then I tried the same on Ubuntu. The device doesn’t show in the left hand side panel. When I try the above commands it just says
waiting for device
So, I guess Ubuntu doesn’t even recognize the Nexus 9
I then opened ‘Additional Drivers’ but it just says searching for available drivers and then no proprietary drivers are in use on this system
Any advice for Nexus 9 drivers on Ubuntu?
I also tried from the bootloader: Hboot → Recovery → Apply update from ADB
In Ubuntu I went to the directory where the ZIp file of the system image is located
Then I typed in the terminal:
adb sideload image-volantis-mob30d.zip
And it says …
Error: insufficient permission for device
I’m running out of ideas. Can anyone help?
1. You don't have correct drivers for Nexus 9. The Nexus Root Toolkit has a driver instillation guide.
2. You can not sideload factory images.
Try sideloading the failed ota available here
Code:
April 2016 Nexus OTA Updates - Security Level 2016-04-02
Nexus 9 (LTE) [URL="https://android.googleapis.com/packages/ota/google_flounderlte_volantisg/9ae7d85d6433d055a9e4f3049ac86eb0e562bbf1.signed-signed-volantisg-MOB30D-from-MMB29V.zip"]MOB30D from MMB29V[/URL]
Nexus 9 (Wi-Fi) [URL="https://android.googleapis.com/packages/ota/google_flounder_volantis/6a2119f2077022c1ba852f2c613b8ce942c33836.signed-signed-volantis-MOB30D-from-MMB29V.zip"]MOB30D from MMB29V[/URL]
If that doesn't work try sideloading Android N OTA
aeglyss said:
Any advice for Nexus 9 drivers on Ubuntu?
Error: insufficient permission for device
I’m running out of ideas. Can anyone help?
Click to expand...
Click to collapse
I don't know specifically about Ubuntu, but I've done several updates to usb-connected android devices using Debian linux, and I've never needed to add a device-specific driver.
Some additional ideas on the permissions:
(1) Did you enable "USB Debugging" in Settings->Developer Options?
(2) From your Linux machine, did you try to run adb as the root user or use sudo? I have to do this for both adb and fastboot. (Example command line: '$sudo adb devices', without the quotes.)
(3) Finally on the Linux side, did you try to connect first via adb? And, if so, did you look on your Nexus for an "Enable..." approval notification?
Good luck!
cheers,
john
Thanks everyone. I managed to fix it
aeglyss said:
Thanks everyone. I managed to fix it
Click to expand...
Click to collapse
Hi, I am at a similar point, my Google Nexus 9 failed doing the update, I then tried to factory re-set it and now it is trying to check connections...
I have downloaded the bootloader and my Windws 10 pc can see the tablet via explorer. I believe I have also switched the tablet to Fastboot but bootloader doesn't sem to be able to make the connection.
I was wondering if you are able to provide me with instruction as to how to rescue this tablet. I am not an expert, so I would appreciate any instructions to be as simple as possible.
Thank you for your help,
Mike
Hello XDA,
I just got a v10 and while i'm new to the phone, I'm not new to rooting/ installing custom roms etc. But for the life of me I cant unlock to bootloader of this phone which if im not mistaken, is the only way to get root. I just installed adb on my windows 10 laptop and I'm trying to enter fastboot on my devices by plugging in the power cable and pressing the volume down and I'm greeted with a screen that says"*welcome to fastboot mode for bootloader unlock: *quick Guidance...etc" I cant exit out of this mode so I assume this is fastboot mode? It doesnt look like any fastboot mode Ive ever seen. Anyways when trying to run the fastboot oem unlock command, I am stuck on "waiting for device". I honestly dont know whats wrong with my setup but if someone could help that would be fantastic. I have tried installing the Lg united drivers and samsung drivers but they dont seem to work. Please advise if you could.
http://forum.xda-developers.com/showthread.php?t=3490604
gamin92 said:
http://forum.xda-developers.com/showthread.php?t=3490604
Click to expand...
Click to collapse
So to get it to work I have to install unbuntu software on my computer, boot into it and then install adb? I'm not getting this?
ayo234 said:
So to get it to work I have to install unbuntu software on my computer, boot into it and then install adb? I'm not getting this?
Click to expand...
Click to collapse
I looked online at some forums about this issue and I got it fixed Here what the post said
1. Connect your device while in fastboot mode.
2. open the device manager (ctrl + X on windows 10)
3. find your device "XXX ADB Device"(Mine was "Alcatel ADB Device" but it can be anything)
4. click on the arrow
5. right click on the Android Bootloader Interface
6. Click on "Properties"
7. Go to "Driver" Tab
8. Click "Uninstall"
9. Mark the "Delete the driver software for this device
10. Click OK
11. Disconnect and Reconnect your device from the cable
12. Windows device manager should show an item in the list that simply says Other devices, and will expand to "Android". Do those next steps quickly! (OR: just disconnect from the internet. Some people report it works). You have between 5-10 seconds until Windows changes it to another driver. If device manager changes the driver to "Kedacom USB device" (or something else, start over from step 8).
13. Right click and choose "Update driver software" -> Browse my computer for driver software -> Let me pick from a list...
14. Choose "Kedacom USB device" (or something else that seems logical)
15. Uncheck "Show compatible hardware"
16. Choose "Android bootloader interface version _" that is the latest (should be 28.8.2016).
17. Hopefully it will work for you
Extremely helpful and it solved my problem. Here the original thread, its post number 33
http://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
Acer Predator 8 GT-810 system\etc backup please!
Make a backup folder etc
Do you still need it? I can send it you tomorrow or something like that.
p8tgames said:
Do you still need it? I can send it you tomorrow or something like that.
Click to expand...
Click to collapse
hey man if u able to send me a back up. Will that solve my problem ?
I made mistake to wipe everything in my phone and now i dont have OS ( i cant start my phone) i can only enter TWRP and thats all. i can use pc to transfer files to my phone and then install the files from there , so i wonder if any1 send me back up will that save me ???
i cand find anywhere OS for acer predator gt 810
there is official avolo zip on acers' page. flash that zip and you're safe
Flash archive corrupted
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware.
dvijetrecine said:
there is official avolo zip on acers' page. flash that zip and you're safe
Click to expand...
Click to collapse
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware
Alex_merser54 said:
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware
Click to expand...
Click to collapse
Use fastboot to flash the stock ROM instead of Intel flash tool. (If you know what you're doing, just read the part in blue below.)
fastboot is for Android devices, whether they have Qualcomm or Intel processors. Using Intel Flash tool is more akin to using Qualcomm's QPST for flashing, which is also something that should only be attempted
after trying fastboot. The Intel flash tool expects the .zip file to be in a format such as a Chuwi ROM with Windows is. Intel Flash tool unfortunately doesn't expect the .zip to be in the Android format like Acer's stock
ROM "AV0L0-something.zip" is.
With the tablet off, and plugged into your computer, hold both volume buttons and power it on. (You probably already knew this step, but here just in case )
It will vibrate longer than it usually does when turning on.
The screen should indicate that the device is in download, or "dnx" mode.
Open a command prompt in administrator mode,(the title of the window should say "Administrator: Windows Command Prompt" or "Administrator: <current directory>")
Type:
Code:
fastboot
If command not found, then either copy fastboot.exe into System32, or add the path it is in to your PATH variable, or simply navigate to its directory within the command prompt.
If you're not familiar with the PATH variable, you can just shift+right-click on fastboot.exe, click "Copy Path" and then paste it into the command prompt to use it's full path in place of simply "fastboot".
Once you're able to type "fastboot" or paste the full path and press enter and it returns the fastboot help message, type:
Code:
fastboot devices
this will either return a single line containing your device's serial number, or it will return nothing at all
If you see a serial number, you're in business.
(make sure the tablet is not low on battery before you continue):
Type:
fastboot update <path to ROM .zip>
Click to expand...
Click to collapse
This should initiate a full reflashing of the stock ROM. The tablet will reboot a couple times, you should hear/feel an even longer vibration during the process, do not touch it or unplug it from the computer until it is at the initial Google device setup screen waiting for your input.
Note that this full reflashing will also overwrite TWRP with the stock recovery.
if "fastboot devices" returns nothing at all, and also doesn't say "command not found" then do the following:
open device manager on computer, find the tablet's driver (may be under portable devices, or COM ports. sometimes under USB.)
if you can't find it, look for an "unknown device" with a yellow exclamation mark on it. If you see that, then you may not have had the driver installed in the first place. To verify, unplug the tablet from the computer
and see if the unknown device disappears from device manager.
If you were able to find the tablet in device manager, then right click and "Uninstall Device" and be sure to check the box to uninstall the driver software as well before clicking OK.
Then, unplug the tablet from your computer if you haven't already.
Download the latest driver from the same place on Acer's website that you downloaded the stock ROM from. Install the driver and restart your computer if it says it needs to.
Afterward, ensure the tablet is off and try the steps above again.
biorpg said:
Use fastboot to flash the stock ROM instead of Intel flash tool. (If you know what you're doing, just read the part in blue below.)
fastboot is for Android devices, whether they have Qualcomm or Intel processors. Using Intel Flash tool is more akin to using Qualcomm's QPST for flashing, which is also something that should only be attempted
after trying fastboot. The Intel flash tool expects the .zip file to be in a format such as a Chuwi ROM with Windows is. Intel Flash tool unfortunately doesn't expect the .zip to be in the Android format like Acer's stock
ROM "AV0L0-something.zip" is.
With the tablet off, and plugged into your computer, hold both volume buttons and power it on. (You probably already knew this step, but here just in case )
It will vibrate longer than it usually does when turning on.
The screen should indicate that the device is in download, or "dnx" mode.
Open a command prompt in administrator mode,(the title of the window should say "Administrator: Windows Command Prompt" or "Administrator: <current directory>")
Type:
If command not found, then either copy fastboot.exe into System32, or add the path it is in to your PATH variable, or simply navigate to its directory within the command prompt.
If you're not familiar with the PATH variable, you can just shift+right-click on fastboot.exe, click "Copy Path" and then paste it into the command prompt to use it's full path in place of simply "fastboot".
Once you're able to type "fastboot" or paste the full path and press enter and it returns the fastboot help message, type:
this will either return a single line containing your device's serial number, or it will return nothing at all
If you see a serial number, you're in business.
(make sure the tablet is not low on battery before you continue):
Type:
This should initiate a full reflashing of the stock ROM. The tablet will reboot a couple times, you should hear/feel an even longer vibration during the process, do not touch it or unplug it from the computer until it is at the initial Google device setup screen waiting for your input.
Note that this full reflashing will also overwrite TWRP with the stock recovery.
if "fastboot devices" returns nothing at all, and also doesn't say "command not found" then do the following:
open device manager on computer, find the tablet's driver (may be under portable devices, or COM ports. sometimes under USB.)
if you can't find it, look for an "unknown device" with a yellow exclamation mark on it. If you see that, then you may not have had the driver installed in the first place. To verify, unplug the tablet from the computer
and see if the unknown device disappears from device manager.
If you were able to find the tablet in device manager, then right click and "Uninstall Device" and be sure to check the box to uninstall the driver software as well before clicking OK.
Then, unplug the tablet from your computer if you haven't already.
Download the latest driver from the same place on Acer's website that you downloaded the stock ROM from. Install the driver and restart your computer if it says it needs to.
Afterward, ensure the tablet is off and try the steps above again.
Click to expand...
Click to collapse
Thank you, but I just entered EFI and load android.efi file, also I autorun it and reflash via recovery
NOTE: I'm using Windows 10 64-bit on the latest update.
So for the past week I've been interested in unlocking the bootloader of my D6503 Xperia Z2 running 6.0.1 Marshmallow. I've taken all the necessary precautions to do so.
(Apparently I can't post links since this is my first post, sorry!)
Using the Sony "unlock the bootloader" page, I've been able to get into fastboot mode- however the driver for fastboot that Sony provides doesn't work (They give a link to the altered drivers in the tutorial). The "S1Boot Fastboot" comes up as not recognised on my computer. I've tried updating the driver using the device manager and pointing to the location where I have Sony's driver installed, then it says "installing" for a while before giving a warning that it was unable to install the driver because "the system cannot find the file specified". I have definitely followed every step that Sony has put on their unlock the bootloader page.
I've looked everywhere but cannot find a solution. It appears that many other Xperia users have had the same problem as me in the past but none of their solutions worked for me. So far I've tried:
Force updating the drivers
Downloading Sony's flashtool to manually install drivers, but the driver folder doesn't include the driver installer .exe file.
Manually setting the device driver to "Bootloader interface" and "Android ADB interface" in the device manager
Using the Android SDK manage to install the drivers
Downloaded third-party drivers from here by DoomLord (However there wasn't a driver available for my specifc device, the Z2)
The command "adb devices" recognises my phone when it is fully turned on, but the command "fastboot devices" never recognises my phone whether it is on or in the fastboot mode.
I'm thinking of just downloading a Linux VM and trying it on there, since apparently no extra drivers are needed, but that will mean downloading the Android SDK and Java JDK as well....
Can someone please help me out? I'm really interested in unlocking this bootloader... Thanks in advance
anaglyph said:
NOTE: I'm using Windows 10 64-bit on the latest update.
So for the past week I've been interested in unlocking the bootloader of my D6503 Xperia Z2 running 6.0.1 Marshmallow. I've taken all the necessary precautions to do so.
(Apparently I can't post links since this is my first post, sorry!)
Using the Sony "unlock the bootloader" page, I've been able to get into fastboot mode- however the driver for fastboot that Sony provides doesn't work (They give a link to the altered drivers in the tutorial). The "S1Boot Fastboot" comes up as not recognised on my computer. I've tried updating the driver using the device manager and pointing to the location where I have Sony's driver installed, then it says "installing" for a while before giving a warning that it was unable to install the driver because "the system cannot find the file specified". I have definitely followed every step that Sony has put on their unlock the bootloader page.
I've looked everywhere but cannot find a solution. It appears that many other Xperia users have had the same problem as me in the past but none of their solutions worked for me. So far I've tried:
Force updating the drivers
Downloading Sony's flashtool to manually install drivers, but the driver folder doesn't include the driver installer .exe file.
Manually setting the device driver to "Bootloader interface" and "Android ADB interface" in the device manager
Using the Android SDK manage to install the drivers
Downloaded third-party drivers from here by DoomLord (However there wasn't a driver available for my specifc device, the Z2)
The command "adb devices" recognises my phone when it is fully turned on, but the command "fastboot devices" never recognises my phone whether it is on or in the fastboot mode.
I'm thinking of just downloading a Linux VM and trying it on there, since apparently no extra drivers are needed, but that will mean downloading the Android SDK and Java JDK as well....
Can someone please help me out? I'm really interested in unlocking this bootloader... Thanks in advance
Click to expand...
Click to collapse
Download Sony AIO flashtool by androxyde and unlock bootloader with it, it reduces much effort and time you need to spend.
I am having the same exact problem. I have already tried a half dozen variants of android_winusb.inf to no avail. Either gets accepted but end up with a "cannot find the file specified" error, or simply doesn't get accepted. I am actually quite experienced with android modding (using both windows and linux) but I am on my new laptop now trying to set it up to fix my Xperia Z1 (flashed it with c6903 stock and now it has no baseband - because in reality it's a c6902) but windows10 (which I actually really like) is really giving me a hard time getting adb working!
cs982005 said:
I am having the same exact problem. I have already tried a half dozen variants of android_winusb.inf to no avail. Either gets accepted but end up with a "cannot find the file specified" error, or simply doesn't get accepted. I am actually quite experienced with android modding (using both windows and linux) but I am on my new laptop now trying to set it up to fix my Xperia Z1 (flashed it with c6903 stock and now it has no baseband - because in reality it's a c6902) but windows10 (which I actually really like) is really giving me a hard time getting adb working!
Click to expand...
Click to collapse
I also struggled with same issue trying to bootloader unlock my Xperia X F5121. I eventually succeeded in getting fastboot working on win10:
1. Download as zip: google search github androxyde flashtool (i am not allowed to post links) and extract zip.
2. Restart windows by holding shift down while clicking restart. Windows will boot into a mode where you can disable driver signature enforcement.
3. Run as administrator DPInst64.exe from the drivers folder of Flashtool. Press "install anyway" on every popup where it says drivers origin cannot be confirmed.
jotakinhan said:
I also struggled with same issue trying to bootloader unlock my Xperia X F5121. I eventually succeeded in getting fastboot working on win10:
1. Download as zip: google search github androxyde flashtool (i am not allowed to post links) and extract zip.
2. Restart windows by holding shift down while clicking restart. Windows will boot into a mode where you can disable driver signature enforcement.
3. Run as administrator DPInst64.exe from the drivers folder of Flashtool. Press "install anyway" on every popup where it says drivers origin cannot be confirmed.
Click to expand...
Click to collapse
Thankyou, Legend!