I was trying to flash stock rom in my Pixel 2 which had the march update and I am getting the error
ERROR: LoadImageAndAuth Failed: Load Error
Click to expand...
Click to collapse
Here's what happened:
I unpacked my phone, updated it to the latest OTA version available (the March version) using the OS update function. Then I followed a tutorial in YouTube to root the phone using Magisk (https://www.youtube.com/watch?v=M-0NIUUvYI4). It worked well, I had root access and I could boot into the phone as normal. All this was done using the latest platform tools, image and usb drivers
I then decided to recheck for updates. A new update appeared, the one from April. I tried to install it and I couldn't. I figured out it was because of the root. I tried to uninstall Magisk using the restore stock image (or similar, can't remember the name of the option) but said "Stock backup does not exist" So I decided to flash the factory image of this April update (I verified it was the correct one for my device. Maybe it could have been the March update, but it has been a wild ride and I can't think clearly anymore) and after that my phone won't boot back up, it is stuck in the bootloader. Sometimes if I use the flash-all of the factory image or modify the script to change the order of the flashing of images I can get to the screen with the Google words in a white background and an open padlock, but that's it. The bootloader is still unlocked
How could I troubleshoot if it is a hardware issue? How could it had damaged itself so quickly, literally I used it only for 30 min before attempting the root process. Sometimes I also do get ERROR: Slot Unbootable, but if I reflash with the script I usually end with the above error
I tried following the instruction to run the deuce script modifying the script such that:
Commented out the unlock_critical as
Code:
::fastboot flashing unlock_critical
the boot slots are as follows: https://pastebin.com/NTapvzXV
I ran getvar all if it is useful: https://pastebin.com/bKA20Jvy
But I am still getting the same error. I am desperate to fix since I haven't even used the phone at all and it is completely new.
Please, I need your help urgently
Here is the output from the flashing process: https://pastebin.com/AwiAyrWh
I think the problem seems that I am unable to mount the vendor partition:
When I try sending the command manually I get this:
Code:
fastboot flash vendor_a vendor.img
target reported max download size of 536870912 bytes
erasing 'vendor_a'...
OKAY [ 0.130s]
sending 'vendor_a' (354100 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 8.012s
When I try wiping or something along those lines with TWRP it says
Failed to mount '/vendor' (Invalid argument)
Click to expand...
Click to collapse
Thank you
Be sure you have the very latest platform tools for your OS and try again. https://developer.android.com/studio/releases/platform-tools.html
westhaking said:
Be sure you have the very latest platform tools for your OS and try again. https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Unfortunately when I started all this process that was the first I did, download everything anew from the official sites.
Download the April factory image and try again. I had this same issue due to not using the most up to date platform tools and not placing the unzipped contents of the april update in the platform tools folder.
smokie75 said:
Download the April factory image and try again. I had this same issue due to not using the most up to date platform tools and not placing the unzipped contents of the april update in the platform tools folder.
Click to expand...
Click to collapse
That's exactly what I did unfortunately. The thing is I am unable to flash the vendor image.
Try a different USB port on your computer, preferably a USB 2 port instead of a USB 3 port.
Telperion said:
Try a different USB port on your computer, preferably a USB 2 port instead of a USB 3 port.
Click to expand...
Click to collapse
Would that help with problem of being unable to mount the vendor partition? I tried but the same problem persists
damnrecoverymode said:
Would that help with problem of being unable to mount the vendor partition? I tried but the same problem persists
Click to expand...
Click to collapse
Potentially, there are reports of sporadic issues with USB ports and USB cables around the forums.
Flashback the March firmware. Its gives you error because your not using the right firmware that was installed in your pixel.
Sent from my [device_name] using XDA-Developers Legacy app
Mangtas_666 said:
Flashback the March firmware. Its gives you error because your not using the right firmware that was installed in your pixel.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
By firmware do you mean the factory image? If so already tried to do that with Deuces script, that is: Download latest platforms tools and the correct factory image, then extract the first .zip and try the flash-all.bat, then when that doesn't work unzip the internal zip and try the script but to no avail. In both cases, as I said, I am unable to mount the vendor partition.
But if by firmware you mean something different, could you please point me in the right direction to download and install it?
I have seen this (https://developers.google.com/android/drivers#walleye), what is that vendor image in there?
Thank you for your help
I didn't use the deuces tool i just copy the necessary files direct to the platform tools folder then edit flashall.bat delete the -w if you dont want to wipe your device. Grab the march firmware at google site then unzip it copy all at the platform tools folder go to fastboot then click flashall.bat
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 06:18 PM ---------- Previous post was at 05:56 PM ----------
Grab it here...https://developers.google.com/android/images
Sent from my [device_name] using XDA-Developers Legacy app
Mangtas_666 said:
I didn't use the deuces tool i just copy the necessary files direct to the platform tools folder then edit flashall.bat delete the -w if you dont want to wipe your device. Grab the march firmware at google site then unzip it copy all at the platform tools folder go to fastboot then click flashall.bat
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 06:18 PM ---------- Previous post was at 05:56 PM ----------
Grab it here...https://developers.google.com/android/images
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes that's what I've been doing to no avail :crying:
damnrecoverymode said:
Yes that's what I've been doing to no avail :crying:
Click to expand...
Click to collapse
Can you go to fastboot? What does it say when you try to flash back to stock?
Sent from my [device_name] using XDA-Developers Legacy app
Mangtas_666 said:
Can you go to fastboot? What does it say when you try to flash back to stock?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
What it says is what is in the first post. You can check all the information I've been able to recompile. But I think the key problem is here:
fastboot flash vendor_a vendor.img
target reported max download size of 536870912 bytes
erasing 'vendor_a'...
OKAY [ 0.130s]
sending 'vendor_a' (354100 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 8.012s
Click to expand...
Click to collapse
damnrecoverymode said:
What it says is what is in the first post. You can check all the information I've been able to recompile. But I think the key problem is here:
Click to expand...
Click to collapse
Try different pc and cable
Sent from my [device_name] using XDA-Developers Legacy app
Try switching to system B? Could also try uninstalling your usb driver and rebooting, then reinstalling it. Also if youre using something like LibUsb, that can mess with adb sometimes.
Do not use toolkits or whatnot. Download everything yourself, from official google links.
Platform tools: https://developer.android.com/studio/releases/platform-tools.html
Firmware: https://dl.google.com/dl/android/aosp/walleye-opm2.171019.029-factory-41296266.zip
I, personally would NOT try flashing an older firmware as these phones have rollback protection. The newest firmware should work, I just used it to return to stock to get the newest security updates.
I'm 99% sure this is a port / cable / driver issue, try all of this on a different computer with USB 2 ports and a fresh driver setup.
Telperion said:
I'm 99% sure this is a port / cable / driver issue, try all of this on a different computer with USB 2 ports and a fresh driver setup.
Click to expand...
Click to collapse
Sure it was. Had to ask to a neighbor his computer and cable to test and it really worked! Thank you for your help mate!
Telperion said:
I'm 99% sure this is a port / cable / driver issue, try all of this on a different computer with USB 2 ports and a fresh driver setup.
Click to expand...
Click to collapse
I've also experienced fastboot issues with the Pixel 2.
After a few successful flashes using my laptop, I started to hit errors when flashing the system partition.
I now check for fastboot broken-ness by repeatedly running "fastboot getvar all" (say, 10 times).
If "getvar" fails, then it is time to try flashing using another machine.
Possible solution
Has the OP ever found a solution to his problems? I stumbled upon this thread with similar issues, by searching for "FAILED (Write to device failed (Unknown error))". My problem looks like this:
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 12.198s]
Writing sparse 'system_a' 1/5 OKAY [ 0.000s]
Sending sparse 'system_a' 2/5 (524284 KB) OKAY [ 14.210s]
Writing sparse 'system_a' 2/5 OKAY [ 0.000s]
Sending sparse 'system_a' 3/5 (524284 KB) OKAY [ 14.160s]
Writing sparse 'system_a' 3/5 OKAY [ 0.000s]
Sending sparse 'system_a' 4/5 (521176 KB) FAILED (Write to device failed (Unknown error))
Click to expand...
Click to collapse
After a few shots in the dark, I managed to resolve the issue by reducing the sparse file size, specifically this fastboot option:
-S SIZE[K|M|G] Break into sparse files no larger than SIZE.
Click to expand...
Click to collapse
Using -S 256M did it for me (the default was just short of 512MB). So the last line in my flash-all.sh looked like this in the end:
fastboot -S 256M update image-walleye-pq2a.190205.002.zip
Click to expand...
Click to collapse
Related
G'day guys, I won't go into too much detail but as I lost root by updating OTA to JB I have been successfully able to downgrade the firmware to 0.30 (and bootloader evidentially)
WARNING: YOU WILL LOSE ALL DATA ON INTERNAL STORAGE, IM NOT RESPONSIBLE FOR BRICKS, TRY AT OWN RISK!
WARNING: DO NOT TRY TO WIPE DATA FROM THE BOOTLOADER WHILST A CUSTOM RECOVERY IS INSTALLED, YOU WILL BRICK YOUR TABLET MAKE SURE YOU ARE RUNNING THE STOCK JB/ICS BOOTLOADER BY FLASHING THE ASUS BLOB PACKAGE FIRST!
You must have unlocked bootloader and be running the latest firmware 10.4.4.16
Procedure
1) Download 0.30 update from Asus website: http://www.asus.com.au/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
2) extract the blob file from inside the second zip, put in your ADB/FASTBOOT directory
If you don't have fastboot download it here http://www.mediafire.com/?nbw2ofv3xd5s35l
3) Reboot tablet into bootloader (ON + VOLDOWN) then select fastboot mode
4) type command: fastboot -i 0x0b05 flash system blob
5) wait for ages....
6) the install will hang on the spinning asus diagram
7) reboot into bootloader and select the "wipe data" (same menu as where fastboot is)
8) should reboot automatically and you should have sucessfully downgraded to ICS 0.30
Hope it also works for you.
http://forum.xda-developers.com/showthread.php?t=1492887
Does it work with above method?
No idea, but you're welcome to try
Sent from my GT-I9100 using xda app-developers app
Has anyone tried this method to downgrade to .26 from .30?
Ok, confirmed, it doesn't work to revert to .26. You get signature mismatch. I gave it a shot
Now, if I upgrade to JB and downgrade can I go to .26? Hmmm, might give it a whirl.
tbtaf said:
Has anyone tried this method to downgrade to .26 from .30?
Click to expand...
Click to collapse
It won't work. You will get a signature mismatch. It seems to work between JB & 0.30
b3z said:
It won't work. You will get a signature mismatch. It seems to work between JB & 0.30
Click to expand...
Click to collapse
I can confirm this does work and does revert the bootloader.
Guys, can we move this to development? I personally believe it would be a great help to many over there. It saved my backside. I can tell you that! Great threat here!:laugh:
Uh, I can't access fastboot anymore with the JB update. It comes up as unknown device. I have installed the Naked Drivers and have had it installed for awhile with no problems.
The cmd sticks to < waiting for device >.
Can you create a zip with the right ADB/FASTBOOT drivers? I have try many but my tablet is not showing when i do FASTBOOT DEVICES
---------- Post added at 06:06 AM ---------- Previous post was at 05:58 AM ----------
androidxen said:
Uh, I can't access fastboot anymore with the JB update. It comes up as unknown device. I have installed the Naked Drivers and have had it installed for awhile with no problems.
The cmd sticks to < waiting for device >.
Click to expand...
Click to collapse
same here
2) extract the blob file from inside the second zip, put in your ADB/FASTBOOT directory
Click to expand...
Click to collapse
ADB/FASTBOOT folder? Sorry, haven't really fooled around much with my TF700, except for getting root. (and then loosing it like an idiot when I rushed to upgrade to JB)
Accophox said:
ADB/FASTBOOT folder? Sorry, haven't really fooled around much with my TF700, except for getting root. (and then loosing it like an idiot when I rushed to upgrade to JB)
Click to expand...
Click to collapse
1) To be able to use this fastboot method you need to have installed the android-sdk (google it) with the platform-tools package and also the Google USB drivers (i think it is in the extras package)
1A) Alternatively download this package, it contains the ADB/FASTBOOT application... not sure about the correct drivershttp://www.mediafire.com/?nbw2ofv3xd5s35l
2) Inside this package are two executables called adb and fastboot. Using windows command prompt you will have to navigate to the folder that contains these two executables and type "fastboot devices" if you have your TF700 plugged in and in fastboot mode you should see a few numbers and you're ready to go!
b3z said:
1) To be able to use this fastboot method you need to have installed the android-sdk (google it) with the platform-tools package and also the Google USB drivers (i think it is in the extras package)
1A) Alternatively download this package, it contains the ADB/FASTBOOT application... not sure about the correct drivershttp://www.mediafire.com/?nbw2ofv3xd5s35l
2) Inside this package are two executables called adb and fastboot. Using windows command prompt you will have to navigate to the folder that contains these two executables and type "fastboot devices" if you have your TF700 plugged in and in fastboot mode you should see a few numbers and you're ready to go!
Click to expand...
Click to collapse
Oh, well, then I'm an idiot. I thought it was a /system/fastboot or something silly that asus decided to do. Simple enough.
I get a:
C:\platform-tools>fastboot -i 0x0b05 flash system WW_9.4.5.30.zip (this is the unpacked update from the asus site)
sending 'system' (375245 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s
Should I have unlocked bootloader to downgrade?
does the "wipe data" feature of the stock recovery really delete the whole internal storage or does it leave the internal sdcard partition intact? i forgot to make a backup of this part (only my apps through titanium) and now my JB upgrade failed and i don't want to lose all my pictures and stuff
0x000 said:
does the "wipe data" feature of the stock recovery really delete the whole internal storage or does it leave the internal sdcard partition intact? i forgot to make a backup of this part (only my apps through titanium) and now my JB upgrade failed and i don't want to lose all my pictures and stuff
Click to expand...
Click to collapse
It does. I made that mistake too, lost my notes for the year so far... :banghead:
Sent from my Incredible 2 using xda app-developers app
How long might 'ages' be?
Been at sending 'system' (798394 KB) ...
for over 15 mins
Sent from my HTC PH39100 using xda premium
kyrtap10 said:
Should I have unlocked bootloader to downgrade?
Click to expand...
Click to collapse
You do need to unlock your bootloader to down grade.
buhohitr said:
You do need to unlock your bootloader to down grade.
Click to expand...
Click to collapse
Ok, now I know to make sure that I have backup of my root before updating
160bpm said:
I get a:
C:\platform-tools>fastboot -i 0x0b05 flash system WW_9.4.5.30.zip (this is the unpacked update from the asus site)
sending 'system' (375245 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s
Click to expand...
Click to collapse
you can't just flash the zip, you have to extract the "blob" file inside the zip and flash that
I had the can't mount sdcard issue on my tablet
I read somewhere that you can - erase the command system -. and so on. The boot-related files would be preserved
Unfortunately I have now only the acer logo and the boot loader on the screen.
When I press power and volume, nothing happens. Is there any possibility to rescue the Tablet?
I can just connecting and sending commands via usb and aio toolbox.
Please help me, my records from the study are in this tablet.
OK, lets summerize:
Tablet Acer 510
something happen - what does you've done?
I can just connecting and sending commands via usb and aio toolbox.
Click to expand...
Click to collapse
What is the AIO Toolbox? I didn't know....
If you've connect the Tablet on the PC, could the PC know the Tablet? Does you've access to the Tablett via adb ? Does the Tablett stopped at this point or it is in a reboot loop?
If you've an access via adb, you have the possibility
a) safe you work on PC
b) restore the 3 *.img on your tablett
If you need the 3 img files, I can give you a link of my 3 files (after root and NO-AD installation)
I tried this
Yes i can connect to pc by manipulating the lock screen button while starting with volume and power button.
Then i can send commands like this "fastboot oem unlock" or this "fastboot flash recovery recovery_nothrills.img"
I tried to send the nothrills image again, and it accepts the image and says image receyved but doesn't help.
Please can you mention what i have to do now.
Did you get my private message
Isn't it possible to mount the sdcard in ADB, and then pull the files you need?
In that way you have your records back and you can flash stuff without the fear of losing your files.
farris said:
Isn't it possible to mount the sdcard in ADB, and then pull the files you need?
In that way you have your records back and you can flash stuff without the fear of losing your files.
Click to expand...
Click to collapse
I can connecting via acer fastboot interface
Please can you tell me how is the command to connect sdcard in adb mode and where cani get the files and where have i need to drop it
Sorry, iam a very beginner
Can i push files in acer fastboot interface mode
I think i'd erased the bootfiles for the bootloader of nothrills boot image
i can just connect in fastboot interface mode and can sending commands
From what I have gathered on your thread on the other board you have erased your /sdcard partition
I believe CWM needs /sdcard (If I remember right, it says something to this effect when booting to CWM)
1) Try to flash the stock recovery from NoThrill's thread http://forum.xda-developers.com/showthread.php?t=1866378
2) put a stock ROM on an external SD card (rename to update.zip) http://forum.xda-developers.com/showthread.php?t=1897791
3) boot into recovery
4) keep your fingers crossed that it will install
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot flash recovery boot.img
sending 'recovery' (3970 KB)... OKAY [ 1.275s]
writing 'recovery'... OKAY [ 1.410s]
finished. total time: 2.686s
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot reboot
rebooting...
finished. total time: 0.427s
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
i tried what you mentioned, unfortunately no success.
ercuem said:
Can i push files in acer fastboot interface mode
I think i'd erased the bootfiles for the bootloader of nothrills boot image
i can just connect in fastboot interface mode and can sending commands
Click to expand...
Click to collapse
Should be:
fastboot flash boot [file]
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
ercuem said:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot flash recovery boot.img
sending 'recovery' (3970 KB)... OKAY [ 1.275s]
writing 'recovery'... OKAY [ 1.410s]
finished. total time: 2.686s
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot reboot
rebooting...
finished. total time: 0.427s
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
i tried what you mentioned, unfortunately no success.
Click to expand...
Click to collapse
Where did it go wrong?
Did you boot to recovery? (Vol- + power)
YEAH
a little success
I put updare.zip on external sd
Used this command "fastboot flash boot boot.img "This is the stock kernel of nothrill"
And now i got:
erasing cache before sd update...
sd update command: recovery
update package=sdcard: update.zip
Booting recovery kernel image
Now it stays on this state until 7 minutes an nothing happens
What boot.img did you flash?
Randomwalker said:
What boot.img did you flash?
Click to expand...
Click to collapse
This one
http://forum.xda-developers.com/showpost.php?p=31137321&postcount=1
Are you having issues with the ThrillsKernel (freezes, reboots, etc.)? Download the Acer kernel below:
Acer original kernel (mirror) (mirror)
(MD5 for the .ZIP file: b6e4f3fed3c96468ee25a0c3a8925433)
Flash this from the Recovery and wipe dalvik-cache. Note: This Acer kernel will only work with the ROM in this thread, do not attempt to use it on other ROMs!
In this zip is a boot.img and a directory called Meta.inf
OK, so that would be a stock kernel.
Can you try to flash the whole ROM via fastboot?
- copy the update.zip to your fastboot directory
- fastboot update update.zip
Randomwalker said:
OK, so that would be a stock kernel.
Can you try to flash the whole ROM via fastboot?
- copy the update.zip to your fastboot directory
- fastboot update update.zip
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
I USED THIS STOCK ROM
OS_Acer_RV28.RC04.EMEA.DE_A40I_A.zip
But you did unzip it first, right? Not just renamed the download to update.zip?
Randomwalker said:
But you did unzip it first, right? Not just renamed the download to update.zip?
Click to expand...
Click to collapse
Yes unfortunately i'm getting the mentioned message.
Thank you for helping me
Yes unfortunately i'm getting the mentioned message.
Thank you for helping me
shall i try "fastboot boot recovery_nothrill.img?"
No worries, maybe someone more knowledgeable will come around . Unfortunately I no longer have an A510.
So, you currently are on stock recovery and it hangs after: "Booting recovery kernel image", right?
Maybe we really need to reconstruct /sdcard... but I have no idea how.
EDIT:
shall i try "fastboot boot recovery_nothrill.img"
Click to expand...
Click to collapse
Definitely, give it a go! I thought you already tried that.
Randomwalker said:
No worries, maybe someone more knowledgeable will come around . Unfortunately I no longer have an A510.
So, you currently are on stock recovery and it hangs after: "Booting recovery kernel image", right?
Maybe we really need to reconstruct /sdcard... but I have no idea how.
EDIT:
Definitely, give it a go! I thought you already tried that.
Click to expand...
Click to collapse
unfortunately no success, i got the same message:
erasing cache before sd update...
sd update command: recovery
update package=sdcard: update.zip
Booting recovery kernel image
Where can i get an update zip, which it will accept for update?
I got the exactly the same message as attached as jpg and pdf.
Ive about lost my mind trying to restore my nexus 5 to stock .Img . I have tried Wugfresh toolkit v1.8.2 i have adb installed i have google drivers installed.. I have tried to manually flash everything via cmd prompt. I have checked in device manager to make sure everything looks good
I am assumingmy device is being recognized based on that fact it is stating these errors ....I keep getting boot sig error and out of memory error.
I have rebooted into twrp done a data wipe factory reset wipe tried it all as mentioned to try in some topics ive read... I cant find any fix or any relevant topic in regards to these errors on a google search people just say try this and that..
When i try to run the toolkit again same errors.
This is more difficult than even htc ever was for me.
Any help anyone have any ideas?
Could you post a screen shot or a log of what is printed out?
heres what the toolkit says after errors
sending 'bootloader' (2508 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.099s
rebooting into bootloader...
FAILED (unknown status code)
finished. total time: 1.052s
sending 'radio' (42049 KB)...
FAILED (command write failed (Invalid argument)
finished. total time: -0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
Try a different usb port. Make sure it's a usb 2.0. If that doesn't work, try another usb cable.
Errors such as: "out of memory" - "too many links" - "data transfer failure" are usually USB problems.
heres what the toolkit says after errors
sending 'bootloader' (2508 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.099s
rebooting into bootloader...
FAILED (unknown status code)
finished. total time: 1.052s
sending 'radio' (42049 KB)...
FAILED (command write failed (Invalid argument)
finished. total time: -0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
I have tried other usb ports.. and cords..
I have tried my other USB port I'm on windows 8 gateway PC.
It recognizes USB debugging and all that cause the script reboots my phone into bootloader
Cf auto root worked fine for me yesterday and that was in the bootloader mode I could swear I have the correct connections and drivers ... It seems like its something else ... Why would I get a out of memory error and no Boot SIG..
I googled that error and others have mentioned it but Never mentioned what caused it .
lojak29 said:
I have tried my other USB port I'm on windows 8 gateway PC.
It recognizes USB debugging and all that cause the script reboots my phone into bootloader
Cf auto root worked fine for me yesterday and that was in the bootloader mode I could swear I have the correct connections and drivers ... It seems like its something else ... Why would I get a out of memory error and no Boot SIG..
I googled that error and others have mentioned it but Never mentioned what caused it .
Click to expand...
Click to collapse
what happens when you do this way?http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Yet another reason not to use toolkits. Since you're using toolkits (for all intents and purposes CF Auto Root is a toolkit), you obviously don't have the SDK installed and the error messages indicate that the USB drivers aren't properly installed. You can't trust toolkits to properly install the USB drivers, and without the drivers the toolkit is worthless, you can't do anything.
Do it the right way, and make sure you install the drivers through the SDK manager, not through plug and play... [GUIDE] Nexus 5 - How to Unlock Bootloader, Install Custom Recovery and Root
Download USB drivers.
Extract the drivers.
Connect phone in fastboot mode.
Open device manager.
In "Android Device" topic right click on "Android Bootloader Interface" and select "Update Driver software..." (depending on what drivers are already installed on your pc this "Android Bootloader Interface" could be "Samsung Galaxy Bootloader Interface" or something similar.)
Install the new drivers.
Download adb+fastboot.
Extract it, and place the adb folder to an obvious place, like C:\ or C:\Users\<Your user name>
Open Control Panel.
If the view settings is set to "Cathegories" then click on "System and Security" then select "System".
If the view settigns is set to anything but "Cathegories" then just click on "System".
In "System" window select "Advanced system settings".
Select "Environment Varaibles..." in "System Proerties" window.
At "System variables" section in the "Environment Variables" window look for "Path".
Select it then click on "Edit...".
Place a semicolon (this ===> ; <=== this) at the end of the "Variable value:" line in the "Edit System Varaible" window.
Right after the semicolon type the path to the adb folder. If you placed your adb folder to C:\ then it should look like something like this: ...blablablabla;C:\adb
Then click on "OK" in every window.
Download stock firmware from google.
Extract it (you may need winrar).
Connect phone in fastboot mode.
Double click on flash-all.bat in the previously extracted folder.
Andere dont forget to disable driver signature authentication in Win 8/8.1.
Sent from my Nexus 10 using xda app-developers app
gee2012 said:
Andere dont forget to disable driver signature authentication in Win 8/8.1.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Don't need to do that (or I didn't anyway)
EddyOS said:
Don't need to do that (or I didn't anyway)
Click to expand...
Click to collapse
My USB driver didn't installatll at first before i did that ? ?
Verstuurd vanaf mijn Nexus 5 met Tapatalk
gee2012 said:
My USB driver didn't installatll at first before i did that ? ?
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Click to expand...
Click to collapse
So long as you have the latest drivers from the SDK you should be fine
EddyOS said:
So long as you have the latest drivers from the SDK you should be fine
Click to expand...
Click to collapse
I always use the Google USB drivers and never had an issue.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
gee2012 said:
I always use the Google USB drivers and never had an issue.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Click to expand...
Click to collapse
Strange, it's always worked fine on my Windows 8.1 laptop - even with USB3
Tried to flash stock firmware with fastboot. It didnt seemed to finish, so i tried rebooting. But now it wont boot. Just vibrates but when i plug in the usb cable, windows tries to install a driver for it. In device manager it says "APX"
Motawa88 said:
Tried to flash stock firmware with fastboot. It didnt seemed to finish, so i tried rebooting. But now it wont boot. Just vibrates but when i plug in the usb cable, windows tries to install a driver for it. In device manager it says "APX"
Click to expand...
Click to collapse
Do you have nvflash backups? If not you've killed it interrupting a low level nand flash.... I don't know what you were expecting to happen?
If you only have APX I'm sorry to say there are only 2 ways to recover.
1. NVFLash restore
2. New mother board
sbdags said:
Do you have nvflash backups? If not you've killed it interrupting a low level nand flash.... I don't know what you were expecting to happen?
If you only have APX I'm sorry to say there are only 2 ways to recover.
1. NVFLash restore
2. New mother board
Click to expand...
Click to collapse
I dont know. This is like my 70th android device and this is the first time i messed something up while flashing
I just bought the tablet so i do have a 60 days refund in my country. will asus still see if the bootloader is unlocked?
Motawa88 said:
I dont know. This is like my 70th android device and this is the first time i messed something up while flashing
I just bought the tablet so i do have a 60 days refund in my country. will asus still see if the bootloader is unlocked?
Click to expand...
Click to collapse
They'll know you unlocked it as you had to use their unlock tool which dialled home and got the unlock keys....... so yes it is in their database so you warranty is now void I'm afraid.
Asus TF700T Tablet fix
Motawa88 said:
Tried to flash stock firmware with fastboot. It didnt seemed to finish, so i tried rebooting. But now it wont boot. Just vibrates but when i plug in the usb cable, windows tries to install a driver for it. In device manager it says "APX"
Click to expand...
Click to collapse
I had similar issues and spent many a day trying to fix my TF700, almost resigned to the fact that the motherboard was stuffed, but then came across a method that I hadn't tried and now I am back up and running with a stock Rom. Here is the record of what I did, maybe it will help:
Asus TF700T Tablet fix - And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
Ok, so I think that I may have lost power during an upgrade (can’t think of any other reason for it!!) and ended up soft bricking my Asus TF700T tablet and recovery attempts would just lead to the dead Android with a red triangle with an exclamation point in the middle. My warranty having expired with Asus and any attempt for their assistance proved fruitless.
Well I researched and tried absolutely everything out there – (Hard Reset, installing TWRP, used a tool called Motochopper and flashing a custom ROM, downloaded and renaming .zip files, putting it onto a Micro SDcard is formatted Fat32, Scotts Tf700t Recovery etc.etc. etc.)
I even took it to the local shops and paid to have one of the Mobile Technician pop-up stores take a look at it, then a friendly techno geek………all with the same suggestions most likely a motherboard/hard drive problem.
My Asus TF700T tablet eventually ended up with just the plain white ASUS logo in the middle of the screen, some small print in the top left corner followed by the dreaded words “Unrecoverable Bootloader Error (0x00000000)”.
During all of my research I was led to believe that if you can still get to the recovery screen, where you see the 4 icons, all is not lost so I persisted.
Here is the instructions that I followed that restored my TF700T:
Download and install ADB, Fastboot and the required drivers - Download and run this cool little tool which has it all packed into one: [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
NOTE: at the moment Fastboot seems to have issues with Windows 8
This awesome tool installs the ADB and Fastboot.exe to a folder on your C:\ drive (look for a file titled “adb”) as well as the corresponding drivers. This takes about 15 seconds to install following the prompts.
I installed the device drivers - if you have already tried to connect the tablet to your PC and it's recognised as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it.
Download the latest firmware from Asus (Always make sure that you download the correct SKU version -WW, US etc.) and extract the zip twice so you access the blob file (a blob is a collection of binary data stored as a single entity) – copy and paste this blob file into the previously mentioned “adb” folder on your C:\ drive.
Reset the device with a paperclip/needle (about 2 cm down of the SDcard slot)
Power down the tablet and disconnect it from the keyboard dock.
Connect it to your computer via the original USB cable.
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in Fastboot mode and you will see three or 4 icons (depending on the bootloader version). Select the USB icon to get into the Fastboot mode.
Your PC should acknowledge that a USB device has been connected (an audible indication) Don’t panic if the device does not appear under “My Computer” (as mine did not either – Fastboot will still communicate with it), you can go into Control Panel/Hardware and Sound/ Device Manager and you may see “Fastboot” icon, expand this and the device will be represented again by the “Fastboot” icon. Right click, select “Properties”, Driver tab and then select “Update Driver” and allow it to search automatically and update from the internet. This should then update and change to Asus icons. You now can be certain that you have the current device drivers.
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7 press Shift + right click and select "Open command window here".
In the resulting command prompt screen type the following codes (those in bold):
C:\adb\ (or whatever the path to your fastboot folder is..)
fastboot devices (If that command returns a string of numbers and letters, you are good as gold. If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot)
Followed by each in turn of the below, selecting Yes as required and allowing each to complete the process:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
The resulting screen should look something like this below – NOTE, I did make a couple of typos while I was attempting this which returned some multiple choice garble if this happens recheck you input instructions:
E:\asus>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.979s]
finished. total time: 1.980s
E:\asus>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.023s]
finished. total time: 1.025s
E:\asus>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 39.623s]
finished. total time: 39.624s
E:\asus>fastboot erase boot
erasing 'boot'...
OKAY [ 0.303s]
finished. total time: 0.304s
E:\asus>fastboot erase misc
erasing 'misc'...
OKAY [ 0.602s]
finished. total time: 0.603s
E:\asus>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.459s]
finished. total time: 1.460s
fastboot -i 0x0B05 flash system c:\adb\TF700T\blob - depending where you stored your blob, also this was the first time that I saw the loading bar appear on my tablet.
It will now go through the process of reinstalling your Android stock ROM and you should see the something similar to the following:
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.731s]
sending 'system' (800935 KB)...
OKAY [134.276s]
writing 'system'...
OKAY [131.640s]
finished. total time: 267.649s
fastboot -i 0x0B05 reboot
E:\asus>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
E:\asus>
I disconnected and rebooted My Asus TF700T and I now have a fully functioning Tablet with a stock ROM.
It has been reported that after completing this you may have some issues getting back get into recovery, hitting RCK and getting the dreaded dead Android (with a red triangle with an exclamation point in the middle). I have not attempted this but have been led to believe that flashing TWRP 2.7.0.1 via Fastboot works.
All acknowledgement and appreciation for this method should go to Buster99, a Senior Member of XDA Developers
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
And to Snoop05, also a Senior Member of XDA Developers for the awesome ADB/Fastboot/Driver tool.
http://forum.xda- developers.com/showthread.php?t=2588979
To whom I am most grateful for the return of my tablet to a working state, I hope this works for you. Good Luck.
A big big thanks. This instructions worked for my Asus tf700t. It was hard bricked.
Browndog181 said:
I had similar issues and spent many a day trying to fix my TF700, almost resigned to the fact that the motherboard was stuffed, but then came across a method that I hadn't tried and now I am back up and running with a stock Rom. Here is the record of what I did, maybe it will help:
Asus TF700T Tablet fix - And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
Ok, so I think that I may have lost power during an upgrade (can’t think of any other reason for it!!) and ended up soft bricking my Asus TF700T tablet and recovery attempts would just lead to the dead Android with a red triangle with an exclamation point in the middle. My warranty having expired with Asus and any attempt for their assistance proved fruitless.
Well I researched and tried absolutely everything out there – (Hard Reset, installing TWRP, used a tool called Motochopper and flashing a custom ROM, downloaded and renaming .zip files, putting it onto a Micro SDcard is formatted Fat32, Scotts Tf700t Recovery etc.etc. etc.)
I even took it to the local shops and paid to have one of the Mobile Technician pop-up stores take a look at it, then a friendly techno geek………all with the same suggestions most likely a motherboard/hard drive problem.
My Asus TF700T tablet eventually ended up with just the plain white ASUS logo in the middle of the screen, some small print in the top left corner followed by the dreaded words “Unrecoverable Bootloader Error (0x00000000)”.
During all of my research I was led to believe that if you can still get to the recovery screen, where you see the 4 icons, all is not lost so I persisted.
Here is the instructions that I followed that restored my TF700T:
Download and install ADB, Fastboot and the required drivers - Download and run this cool little tool which has it all packed into one: [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
NOTE: at the moment Fastboot seems to have issues with Windows 8
This awesome tool installs the ADB and Fastboot.exe to a folder on your C:\ drive (look for a file titled “adb”) as well as the corresponding drivers. This takes about 15 seconds to install following the prompts.
I installed the device drivers - if you have already tried to connect the tablet to your PC and it's recognised as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it.
Download the latest firmware from Asus (Always make sure that you download the correct SKU version -WW, US etc.) and extract the zip twice so you access the blob file (a blob is a collection of binary data stored as a single entity) – copy and paste this blob file into the previously mentioned “adb” folder on your C:\ drive.
Reset the device with a paperclip/needle (about 2 cm down of the SDcard slot)
Power down the tablet and disconnect it from the keyboard dock.
Connect it to your computer via the original USB cable.
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in Fastboot mode and you will see three or 4 icons (depending on the bootloader version). Select the USB icon to get into the Fastboot mode.
Your PC should acknowledge that a USB device has been connected (an audible indication) Don’t panic if the device does not appear under “My Computer” (as mine did not either – Fastboot will still communicate with it), you can go into Control Panel/Hardware and Sound/ Device Manager and you may see “Fastboot” icon, expand this and the device will be represented again by the “Fastboot” icon. Right click, select “Properties”, Driver tab and then select “Update Driver” and allow it to search automatically and update from the internet. This should then update and change to Asus icons. You now can be certain that you have the current device drivers.
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7 press Shift + right click and select "Open command window here".
In the resulting command prompt screen type the following codes (those in bold):
C:\adb\ (or whatever the path to your fastboot folder is..)
fastboot devices (If that command returns a string of numbers and letters, you are good as gold. If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot)
Followed by each in turn of the below, selecting Yes as required and allowing each to complete the process:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
The resulting screen should look something like this below – NOTE, I did make a couple of typos while I was attempting this which returned some multiple choice garble if this happens recheck you input instructions:
E:\asus>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.979s]
finished. total time: 1.980s
E:\asus>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.023s]
finished. total time: 1.025s
E:\asus>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 39.623s]
finished. total time: 39.624s
E:\asus>fastboot erase boot
erasing 'boot'...
OKAY [ 0.303s]
finished. total time: 0.304s
E:\asus>fastboot erase misc
erasing 'misc'...
OKAY [ 0.602s]
finished. total time: 0.603s
E:\asus>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.459s]
finished. total time: 1.460s
fastboot -i 0x0B05 flash system c:\adb\TF700T\blob - depending where you stored your blob, also this was the first time that I saw the loading bar appear on my tablet.
It will now go through the process of reinstalling your Android stock ROM and you should see the something similar to the following:
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.731s]
sending 'system' (800935 KB)...
OKAY [134.276s]
writing 'system'...
OKAY [131.640s]
finished. total time: 267.649s
fastboot -i 0x0B05 reboot
E:\asus>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
E:\asus>
I disconnected and rebooted My Asus TF700T and I now have a fully functioning Tablet with a stock ROM.
It has been reported that after completing this you may have some issues getting back get into recovery, hitting RCK and getting the dreaded dead Android (with a red triangle with an exclamation point in the middle). I have not attempted this but have been led to believe that flashing TWRP 2.7.0.1 via Fastboot works.
All acknowledgement and appreciation for this method should go to Buster99, a Senior Member of XDA Developers
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
And to Snoop05, also a Senior Member of XDA Developers for the awesome ADB/Fastboot/Driver tool.
http://forum.xda- developers.com/showthread.php?t=2588979
To whom I am most grateful for the return of my tablet to a working state, I hope this works for you. Good Luck.
Click to expand...
Click to collapse
I am trying to fix my tf700. Trying to flash the blob..
Code:
D:\Desktop\TF700>fastboot -i 0x0B05 flash system d:\desktop\TF700\blob
erasing 'system'...
OKAY [ 0.702s]
sending 'system' (800927 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3.439s
Any idea?
Yeah. I Put the blob into your fastboot directory. Open cmd from there and flash it with fastboot - i 0x0b05 flash system blob
berndblb said:
Yeah. I Put the blob into your fastboot directory. Open cmd from there and flash it with fastboot - i 0x0b05 flash system blob
Click to expand...
Click to collapse
Same result. Fixed it by flashing a bootloader blob first.
Fastboot flash staging bootloader-blob
krugm0f0 said:
Same result. Fixed it by flashing a bootloader blob first.
Fastboot flash staging bootloader-blob
Click to expand...
Click to collapse
Are you up and running now?
You may want to try a different USB port. I had the same error when I tried to use a USB hub to connect to my CPU.
Hello everyone
i was running my pixel 2 with root on Oreo. after getting a notification on the new android 9 i updated OTA (which i thought isn't even possible when running root with Magisk)
somehow i wasn't satisfied with pie so i wanted to downgrade back to Oreo. i downloaded the previous Oreo factory Image and ran the flash-all.bat under minimal adb and fastboot.
apparently i got the following error :
Can't determine partition type. Failed (remote: GetVar Variable Not found)
Now my phone stuck on a white screen with the google logo. I can't enter fastboot and adb can't connect to my phone anymore
Can anyone please please help me to get it work
Sorry for my bad english! am from Germany
Hello everyone
i was able to enter the bootloader on my Pixel 2 by holding the powerbutton and volume down pressed for about 20sec.
i downloaded the lates android 9 factory file and ran the flash-all.bat again, but the same error came up like before.
archive does not contain. 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
and can't determine partition type. remote: GetVar Variable Not found...
I'm using the adb-setup-1.4.3 version
Can someone please help me
Go and get your platform tools from here https://developer.android.com/studio/releases/platform-tools then try again try different cables different computers as well but make sure your using the latest available android tools from google. Start there and let me know.
thanks so much for your answer. i downloaded a older version of adb fastboot tools and run a cmd
now its showing at sending sparse 'systemb' 1/4 (524284 KB) ... FAILED (remote: No such partition.)
so the problem is the adb tool?
I'll try and download the platform tools from your link
Kris38 said:
thanks so much for your answer. i downloaded a older version of adb fastboot tools and run a cmd
now its showing at sending sparse 'systemb' 1/4 (524284 KB) ... FAILED (remote: No such partition.)
so the problem is the adb tool?
I'll try and download the platform tools from your link
Click to expand...
Click to collapse
it worked with the latest plattform tool. am back on Oreo 8.1
thanks so much for your help
Kris38 said:
it worked with the latest plattform tool. am back on Oreo 8.1
thanks so much for your help
Click to expand...
Click to collapse
Happy to help!