Database Info

i screwed up :(

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.

dell venue 7 (retail) unbrick?

tried to post in the venue area but got a pop up saying i had to post here. so, heres the situation.
i have a retail dell venue 7, i dont know the model as i cant boot in to it (thus the problem) i did "not" try to root the device, 1.5 years old, checked some messages, locked it, came back later, it wouldnt unlock, did a hard shut down, went to start it up and it just sits at the dell logo. so heres what ive tried so far.
1. if i power on i get a quick USB logo flash.
2. if i power on with usb cable hooked to pc the USB logo stays on the screen.
3. if i go in to droid boot and try recovery it reboots to the dell logo and just sits there.
im legally blind and am having a bit of trouble getting around here but ive tried the "IntelAndroid-FBRL-07-24-2015"
using the above, if i boot in to droid boot it shows up as "android phone" i have to install the adb driver each and every time (windows 8.1) i dont mind that. the above sees the tablet and even issues commands. the tablet reboots and i get a logo with a hat, but it goes no further. if i hold power up and connect to the pc it shows up as a "CloverviewPlus Device" under intel Soc.
this is what "IntelAndroid-FBRL-07-24-2015" shows when i try to do a "5 cwm" then a "T3"
***********************************************************************
FASTBOOT TETHERED RECOVERY LAUNCHER 07-24-2015
***********************************************************************
=======================================================================
DEVICE STATUS: FASTBOOT-ONLINE
DEVICE INFORMATION: DellVenue7000143194 fastboot
=======================================================================
copy needed files to our device
target reported max download size of 1322942464 bytes
sending '/tmp/recovery.zip' (3623 KB)...
OKAY [ 0.887s]
writing '/tmp/recovery.zip'...
OKAY [ 0.686s]
finished. total time: 1.573s
target reported max download size of 1322942464 bytes
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.604s]
writing '/tmp/recovery.launcher'...
OKAY [ 0.686s]
finished. total time: 1.291s
target reported max download size of 1322942464 bytes
sending '/sbin/partlink' (349 KB)...
OKAY [ 0.571s]
writing '/sbin/partlink'...
OKAY [ 0.687s]
finished. total time: 1.259s
issue fastboot oem "stop_partitioning" command to start cwm recovery:
...
(bootloader) Stop partitioning
(bootloader) Stop partitioning
A
FAILED (unknown status code)
finished. total time: 0.635s
---------------------------------------
at which point the tablet reboots, but just sits there with that hat thing.
i dont care if i loose data, id just like to get this tablet back in working order. unfortunitly i have no idea how to do that. im comfortable with the command line but may need a bit of hand holding (i.e. step by steps, ive looked at the wiki but i cant figure it out sadly)

after digging through some emails and finding the service tag, i can now update this to say its a DELL venue 7 3770. and ive still had no luck.

so, i downloaded kernel.tar.gz from Venue_7_3730_CloverTrail_plus/ (yeah i fat fingered the model number above, my bad)
1st sign this wouldnt work? when i unzipped with 7zip i got an error about files all ready existing, not possible since it was an empty folder, but i went ahead any way. installed virtualbox, ubuntu, got that all set up. tried to run from in there and got a boat load of "read only" errors (even though other write/read tests worked fine)
so i figured, ok, lets just keep it "in the box" so to speak, made a folder with in ubuntu, redownloaded said file. used file manager to unpack it only to get an error about "no such file or directory" eh?
so i went over to terminal and tried to unzip it again, this time getting a "not a gunzip file" error, do what?
all of my googling seems to say im hosed any way as every thing i read says you need a good clean copy of /system from your "phone" (what , no one ever does this with a tablet?) to build the rom, kinda defeats the purpose of releasing the source dont it?
oh well, ive tried all i can try and with no one around here pointing me in the right direction, i guess i have a nice paper weight.

Xperia L stuck at recovery screen

Model - Sony xperia l - C 2014
I wanted to flash CM12 to my device. I followed the instructions on Cyanogenmod site.
I enabled USB debugging mode.
I unlocked the bootloader (as per the instructions on sony)
I'm using a linux machine. I've installed adb and fastboot tools.
I havent backed up my bootloader or system (but ive taken data backup before starting the process)
1) When i try to flash the CM ROM using adb sideload method, i get the error..
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
2) If i try to use fastboot method to flash new recovery, using the folowing command
#fastboot flash recovery cm-12-20150906-NIGHTLY-taoshan-recovery.img
i get the error..
sending 'recovery' (9702 KB)...
OKAY [ 0.308s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.310s
Now my phone is unable to boot normally. it gets stuck at recovery.
This is the first time i've tried to flash a new ROM. Any suggestion would be greatly appreciated.
Thank you

abhishek.karvi said:
Model - Sony xperia l - C 2014
I wanted to flash CM12 to my device. I followed the instructions on Cyanogenmod site.
I enabled USB debugging mode.
I unlocked the bootloader (as per the instructions on sony)
I'm using a linux machine. I've installed adb and fastboot tools.
I havent backed up my bootloader or system (but ive taken data backup before starting the process)
1) When i try to flash the CM ROM using adb sideload method, i get the error..
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
2) If i try to use fastboot method to flash new recovery, using the folowing command
#fastboot flash recovery cm-12-20150906-NIGHTLY-taoshan-recovery.img
i get the error..
sending 'recovery' (9702 KB)...
OKAY [ 0.308s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.310s
Now my phone is unable to boot normally. it gets stuck at recovery.
This is the first time i've tried to flash a new ROM. Any suggestion would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
1.boot to recovery
2.connect to pc
3. use this commands in adb:
adb shell
setprop ro.product.device taoshan
4. flash cm12 or any other rom for taoshan
do this all while in same session (dont reboot after the terminal command or it will be gone)
Sent from my mint using XDA Free mobile app

SdtBarbarossa said:
1.boot to recovery
2.connect to pc
3. use this commands in adb:
adb shell
setprop ro.product.device taoshan
4. flash cm12 or any other rom for taoshan
do this all while in same session (dont reboot after the terminal command or it will be gone)
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for the reply SdtBarbarossa .
I've done steps 1,2.
On 3rd step, when i give command #adb shell , im getting error....
error: device unauthorized. Please check the configuration dialog on your device.
Now since the device is stuck at recovery and does not boot, i cant re-authorize my computer from my phone.
I'd like to mention that i started fooling around with my ROM on a different workstation and im trying to fix this on a different workstation right now... having said that, do i need to retry the mentioned steps from the previous computer?
Thanks again.

abhishek.karvi said:
Thank you for the reply SdtBarbarossa .
I've done steps 1,2.
On 3rd step, when i give command #adb shell , im getting error....
error: device unauthorized. Please check the configuration dialog on your device.
Now since the device is stuck at recovery and does not boot, i cant re-authorize my computer from my phone.
I'd like to mention that i started fooling around with my ROM on a different workstation and im trying to fix this on a different workstation right now... having said that, do i need to retry the mentioned steps from the previous computer?
Thanks again.
Click to expand...
Click to collapse
Thats bad ;-( flash aromafm and use the inbuild terminal!
Then you need only the setprop command
Sent from my mint using XDA Free mobile app

SdtBarbarossa said:
Thats bad ;-( flash aromafm and use the inbuild terminal!
Then you need only the setprop command
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
ive downloaded aromafm. It says 1) copy the file to phones sdcard and 2) boot into recovery and select "install from zip"
The problem is :
1) I'm unable to copy anything to phone, since the phone is stuck at recovery and MTP is not working when i connect it to USB
2) My recovery doesnt have option "install from zip".... (recovery screen says - Cyanogen recovery)
Can i forcibly push the file to my sd card using flashtool or adb? or will keeping the file on external sd card work too? if so, how do i proceed?
Also i forgot to mention earlier that when i give the command # adb devices, it says unauthorised.
But im able to use the command #adb sideload *.zip (although it fails)
When i try the sideload method..flash starts but fails with the error..
On my computers terminal it says
Total xfer: 1.00x
On my phone the error is
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
E: Failed to install /sideload/package.zip
.
.
Installation aborted
I have downloaded the zip file from cyanogenmod official site, and im sure that ive taken the correct file for my device, and have checked that the hash mathces.
Thnx again.

abhishek.karvi said:
ive downloaded aromafm. It says 1) copy the file to phones sdcard and 2) boot into recovery and select "install from zip"
The problem is :
1) I'm unable to copy anything to phone, since the phone is stuck at recovery and MTP is not working when i connect it to USB
2) My recovery doesnt have option "install from zip".... (recovery screen says - Cyanogen recovery)
Can i forcibly push the file to my sd card using flashtool or adb? or will keeping the file on external sd card work too? if so, how do i proceed?
Also i forgot to mention earlier that when i give the command # adb devices, it says unauthorised.
But im able to use the command #adb sideload *.zip (although it fails)
When i try the sideload method..flash starts but fails with the error..
On my computers terminal it says
Total xfer: 1.00x
On my phone the error is
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
E: Failed to install /sideload/package.zip
.
.
Installation aborted
I have downloaded the zip file from cyanogenmod official site, and im sure that ive taken the correct file for my device, and have checked that the hash mathces.
Thnx again.
Click to expand...
Click to collapse
Copy the file to external sd
Sent from my mint using XDA Free mobile app

SdtBarbarossa said:
Copy the file to external sd
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
Even if I copy the file to external sd card, I'm unable to install it from there since I don't get a "install" option in recovery.
Its been too long so I went to the Sony store and got it fixed.
Anyways, Thanks for your help SdtBarbarossa, i appreciate it.
Once again, thank you

abhishek.karvi said:
Model - Sony xperia l - C 2014
I wanted to flash CM12 to my device. I followed the instructions on Cyanogenmod site.
I enabled USB debugging mode.
I unlocked the bootloader (as per the instructions on sony)
I'm using a linux machine. I've installed adb and fastboot tools.
I havent backed up my bootloader or system (but ive taken data backup before starting the process)
1) When i try to flash the CM ROM using adb sideload method, i get the error..
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
2) If i try to use fastboot method to flash new recovery, using the folowing command
#fastboot flash recovery cm-12-20150906-NIGHTLY-taoshan-recovery.img
i get the error..
sending 'recovery' (9702 KB)...
OKAY [ 0.308s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.310s
Now my phone is unable to boot normally. it gets stuck at recovery.
This is the first time i've tried to flash a new ROM. Any suggestion would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
Try this command for installing recovery: " fastboot flash boot recovery.img"
change "recovery" word with your downloaded recovery file name.

@SdtBarbarossa
Hi, I have run into the same problem as OP, and have been trying to install aromafm but get the following output:
Code:
E: Cannot load volume /misc!
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Installation aborted.
E: Cannot load volume /misc!
I have tried several aroma zips but its the same with all of them
I have checked and indeed the device ID is set to "".

Alhaj said:
Try this command for installing recovery: " fastboot flash boot recovery.img"
change "recovery" word with your downloaded recovery file name.
Click to expand...
Click to collapse
Ok, I was afraid to try this but finally dared, and it fixed my situation!
I ran it, and unlike trying to flash to recovery, flashing to boot proved successful (no "command not allowed" message). Then unplugged USB, and phone booted to recovery (I highly recommend TWRP), from where I installed the system and additional apps (surprisingly, without errors about device ID or incorrect signatures), and afterwards booted into system flawlessly.
Thanks!

severoraz said:
Ok, I was afraid to try this but finally dared, and it fixed my situation!
I ran it, and unlike trying to flash to recovery, flashing to boot proved successful (no "command not allowed" message). Then unplugged USB, and phone booted to recovery (I highly recommend TWRP), from where I installed the system and additional apps (surprisingly, without errors about device ID or incorrect signatures), and afterwards booted into system flawlessly.
Thanks!
Click to expand...
Click to collapse
Well its been a long time since i last had the time to pick up my XL ... but nice to hear that the fix still worked if you have any other question send me a pn since im no longer monitoring these threads ( due to missing time ;-( )

SdtBarbarossa said:
Well its been a long time since i last had the time to pick up my XL ... but nice to hear that the fix still worked if you have any other question send me a pn since im no longer monitoring these threads ( due to missing time ;-( )
Click to expand...
Click to collapse
Thanks! I picked mine up as a backup phone but this community has kept it running smooth

Ruined brand new Pixel 2 while rooting

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

did i brick my Phone by downgrading from Android Pie?

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!