Database Info

[Q] Problem while flashing Android 5.0 Stock Image on Nexus 5

Got this error while flashing Android Lollipop final factory image that released hours ago.
Help please!
OKAY [ 30.945s]
writing 'system'...
OKAY [ 66.316s]
erasing 'userdata'...
OKAY [ 12.928s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
malloc: Not enough space
Cannot generate image.
FAILED ()
finished. total time: 116.020s
Press any key to exit...

HeyIamSmiley said:
Got this error while flashing Android Lollipop final factory image that released hours ago.
Help please!
OKAY [ 30.945s]
writing 'system'...
OKAY [ 66.316s]
erasing 'userdata'...
OKAY [ 12.928s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
malloc: Not enough space
Cannot generate image.
FAILED ()
finished. total time: 116.020s
Press any key to exit...
Click to expand...
Click to collapse
What method are you using to flash the stock image? Seen lots of different methods, but what worked for me was easy .. Nexus Root Toolkit. Looked like it hung for 5 minutes during install, then everything went smoothly. No issues. Give that a try?

Hi,
first: Wrong section
second: did you try the Work-around (flash file for file)

[Help] Nexus 5 stuck at "Google" Logo

I'm going to post here to see if i can get any feedback.
mpgrimm2 said:
Well as I always say, I am not a developer or play one on TV...
My N5 locked up on me the other day after a call. I was on 5.1.1. LMY48B, basic stock with root going on a month or so since the 5.1.1 update which I did via full flash Method 2 originally (as all my updates).
- Phone stops at the "Google" screen.
- I can get to Fastboot, and I can get to factory recovery.
- I am lucky if I can get it to turn on at all so I can get to Fastboot screen; and when it locks, it takes a bit of a miracle to get it to turn off.
- I have been able to reflash the factory images from Post 1 with LMY48B 2x and went back and tried LMY47D for giggles. Same results.
It seems like something is corrupt with my /boot perhaps. Not sure if I should try a fastboot erase on all the partitions (EDIT: Tried that from post 2, no change) or if anyone has any other suggestions.
Click to expand...
Click to collapse
Edit:
As a last ditch i even tried WugFresh's N5 Toolkit just to see if it would somehow do something different on a stock reload. (LMY48B now)
Nope. No change.
Comes to a dead stop at the Google logo and just gets hot if i leave it there.
Really hoping someone knows something else to try so i can tuck the LG G4 away as a spare and get my N5 back.
Sent from my LG G4 on Tapatalk.

Bump.
Sent from my LG G4 on Tapatalk.

You have wiped data haven't you while trying this?
Sent from my Nexus 5 using Tapatalk

Ben36 said:
You have wiped data haven't you while trying this?
Click to expand...
Click to collapse
Yes. (I left out some of the details for C:/ .... boot.img etc below)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ...
fastboot reboot-bootloader ...
fastboot flash radio ...
fastboot reboot-bootloader ...
fastboot flash system ...
fastboot flash userdata ...
fastboot flash boot ...
fastboot flash recovery ...

Do you have a working nandroid backup to restore?
Did you try to format /cache instead of erasing it?

Primokorn said:
Do you have a working nandroid backup to restore?
Did you try to format /cache instead of erasing it?
Click to expand...
Click to collapse
I do have a backup on my pc. I can get to the bootloader, and run fastboot, load twrp but the backup still doesn't boot.
Tried flashing a zip of M preview2 someone put together with TWRP 2.8.7.1 . It hangs during install and phone shuts off.
* I don't think a format command has been done unless it was part of the factory image's script during during install.
I'm going to have to look up the syntax for a "fastboot format" after work unless you know it off hand? I assume its similar to the erase command.
Sent from my LG G4 on Tapatalk.

mpgrimm2 said:
I do have a backup on my pc. I can get to the bootloader, and run fastboot, load twrp but the backup still doesn't boot.
Tried flashing a zip of M preview2 someone put together with TWRP 2.8.7.1 . It hangs during install and phone shuts off.
* I don't think a format command has been done unless it was part of the factory image's script during during install.
I'm going to have to look up the syntax for a "fastboot format" after work unless you know it off hand? I assume its similar to the erase command.
Sent from my LG G4 on Tapatalk.
Click to expand...
Click to collapse
Yes, the same: fastboot format cache
Maybe you should add fastboot format userdata.

Primokorn said:
Yes, the same: fastboot format cache
Maybe you should add fastboot format userdata.
Click to expand...
Click to collapse
Well I did a format of: System, Userdata, & cache ... and an erase on the eMMC partitions (boot & recovery).
Code:
C:\Android\WorkingFlashFolder>fastboot format boot
Formatting is not supported for filesystem with type 'emmc'.
C:\Android\WorkingFlashFolder>fastboot format system
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'system'...
OKAY [ 1.320s]
finished. total time: 1.320s
C:\Android\WorkingFlashFolder>fastboot format cache
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'cache'...
OKAY [ 0.800s]
finished. total time: 0.800s
C:\Android\WorkingFlashFolder>fastboot format userdata
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'userdata'...
OKAY [ 7.970s]
finished. total time: 7.970s
C:\Android\WorkingFlashFolder>fastboot erase boot
erasing 'boot'...
OKAY [ 0.220s]
finished. total time: 0.230s
C:\Android\WorkingFlashFolder>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.230s]
finished. total time: 0.230s
Followed by a full load of the google factory images for LMY48B. Still hangs at the "Google" logo like something is corrupted in /boot or /aboot somehow? I'm not sure if there is anyway to actually delete/recreate the partitions on the N5 to get it to work. Still open to ideas.
Here is my "getvar" command output if its needed...
Code:
C:\Android\WorkingFlashFolder>fastboot getvar all
(bootloader) max-download-size: 0x40000000
(bootloader) version-hardware: rev_11
(bootloader) version-baseband: M8974A-2.0.50.2.26
(bootloader) version-bootloader: HHZ12h
(bootloader) version-cdma: N/A
(bootloader) variant: hammerhead D820(H) 16GB
(bootloader) serialno: EDITED
(bootloader) carrier: None
(bootloader) secure-boot: yes
(bootloader) unlocked: yes
(bootloader) product: hammerhead
(bootloader) partition-size:aboot: 80000
(bootloader) partition-type:aboot: emmc
(bootloader) partition-size:boot: 1600000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:recovery: 1600000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:system: 40000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:userdata: 3321fa800
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 2bc00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:persist: 1000000
(bootloader) partition-type:persist: ext4

I ran out of ideas mate... Almost everyone in a similar situation had to send their device to Google.
I keep searching and come back to you if I find something useful.
Best of luck!

Bump. Tried latest LMY48i, still mostly dead.
It's clear to me that something is missing B/w the bootloader and the OS loader.
Open to ideas from some more knowledgeable folks, especially since I have had a few PM's from others in the same situation.
Sent from my LG G4 on Tapatalk.

Look here http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632 you might have a corrupt persist partition.
Do you have usb debugging on?
Can you reach the phone with adb? (try "adb devices" command and see if it recognizes your phone).
Are you rooted?

I have the same problem, i have tried the persist solution but it does not work. it keep rebooting and its not the power button. thx for your help in adavnce.

eross said:
Look here http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632 you might have a corrupt persist partition.
Do you have usb debugging on?
Can you reach the phone with adb? (try "adb devices" command and see if it recognizes your phone).
Are you rooted?
Click to expand...
Click to collapse
Thanks for taking a look and sorry for the delay, my PC died Friday.
Yes I have taken a look at that thread hoping it would help. Unfortunately, no version of android back to the original release for my Nexus 5 will boot properly (req'd for the Persist T/S) to get past the Google logo which also prevents the use of ADB commands.
Fastboot/bootloader can be accessed (with difficulty) to reload the OS from the factory images, but always with the same result. No Go.

Nexus 5 [D820] sudden black screen

For some reason my Nexus 5 suddenly stopped working. There was no trauma, it hasn't been dropped or anything, the screen just stopped working one day. The screen was already a replacement screen from when I did drop it about a year ago, and it had a bad bleed problem at the bottom of the screen so I didn't mind so much replacing it. While I was at it I also got a new USB charging port/dock connector, as the USB was beginning to be a bit dodgy, and a new battery as I was having it open anyway.
I'm no stranger to replacing parts in phones, laptops and other electronic equipment, and don't generally mess up, but this time, after having replaced all the bits, I'm no further. I've already taken everything apart several times and tried the old parts in all sorts of combinations. I'm sure all the connectors are clicked in good and none missing, but still nothing. When I hit power it gives a short buzz, and the screen gets very slightly lit up, so slightly it's hard to see, but by holding the phone at an angle it can be seen clearly. Nothing else on the screen, no text, graphics, animation, anything. I've also tried all sorts of combinations of up/down/power, also no cigar.
If I boot it in recovery (down+power), connect it to my pc, and do an adb devices it comes up blank. If I do an fastboot devices it comes up with what appears to be the right line.
H:\owncloud\Software\adb-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
H:\owncloud\Software\adb-tools>fastboot devices
02b58059d0217f13 fastboot
Why the difference? The fact that it comes up with anything at all kinda suggest to me that the mainboard probably is ok, no? So in that case, what's left to try/replace?
I was thinking perhaps the boot partition somehow got corrupted, so I thought I'd try loading a fresh boot partition, but that throws an error:
H:\owncloud\Software\adb-tools>fastboot flash bootloader bootloader-hammerhead-hhz12h.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.073s
So again at a dead end.
Any ideas?

Also tried a reflash of the latest stock, but still no cigar...
H:\owncloud\Software\adb-tools>fastboot -w update image-hammerhead-lmy48m.zip
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
Cannot read image.
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: 02b58059d0217f13
--------------------------------------------
checking product...
OKAY [ 0.113s]
checking version-bootloader...
OKAY [ 0.098s]
checking version-baseband...
OKAY [ 0.098s]
sending 'boot' (8916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.758s

No suggestions?

NVidia K1: flashboot fails on InvalidSize error when flashing 'system'

Hi, Following the recent problems with battery life and the latest version of android for NVidia K1 tablets, a friend of mine tried to restore the stock image. Sadly, we're encountering some issue with fastboot, and I haven't been able to find anything on internet that could explain what is happening.
Following the instructions from (hxxp://nvidiashieldzone.com/index.php/shield-tablet/shield-tablet-k1/shield-tablet-restore-to-stock-recovery) we are stuck when flashing the system.img:
Code:
$ fastboot flash system system.img
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.549s]
sending sparse 'system' (545106 KB)...
OKAY [ 21.143s]
writing 'system'...
OKAY [ 19.928s]
sending sparse 'system' (552714 KB)...
OKAY [ 21.482s]
writing 'system'...
OKAY [ 20.861s]
sending sparse 'system' (118407 KB)...
OKAY [ 4.622s]
writing 'system'...
FAILED (remote: (InvalidSize))
finished. total time: 93.270s
When doing a 'fastboot erase system', we don't have any issue:
Code:
fastboot erase system -w
Creating filesystem with parameters:
Size: 13176406016
Block size: 4096
Blocks per group: 32768
Inodes per group: 8128
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3216896
Block groups: 99
Reserved block group size: 791
Created filesystem with 11/804672 inodes and 91191/3216896 blocks
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
******** Did you mean to fastboot format this partition?
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.252s]
erasing 'userdata'...
OKAY [ 1.720s]
sending 'userdata' (137154 KB)...
OKAY [ 5.025s]
writing 'userdata'...
OKAY [ 4.666s]
erasing 'cache'...
OKAY [ 0.208s]
sending 'cache' (18800 KB)...
OKAY [ 0.696s]
writing 'cache'...
OKAY [ 0.710s]
finished. total time: 13.278s
Note that when doing 'fastboot format system', it seems to be returning something a little different (bigger partition, more nodes?), and I don't know if this is expected:
Code:
$ fastboot format system
Creating filesystem with parameters:
Size: 1342177280
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 5120
Label:
Blocks: 327680
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/81920 inodes and 10749/327680 blocks
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.204s]
sending 'system' (22984 KB)...
OKAY [ 0.847s]
writing 'system'...
OKAY [ 0.873s]
finished. total time: 1.924s
I did check that the image had the proper md5, so I'm really stuck at why it doesn't work. The stock image is the same one as on (hxxps://developer.nvidia.com/shield-open-source#tablet-k1)
Interestingly (or worryingly), if I try to erase system too many times in a row, the command will fail with TimeOut, but restarting the tablet fixes it everytime, and I'm able to erase / format / write again, until I get the InvalidSize error.
The tablet is currently stuck on the NVidia logo startup screen (although we can get the bootloader to start everytime).
Do you have any idea what could be happening?
Thanks!
-- tanyiachaos

I'm having this same 'InvalidSize' problem with every recovery image I can lay my hands on, including the original factory full image. The error happens equally using fastboot for Ununtu 16.04 and Windows 10.
Device: Nvidia Shield K1
Has anybody seen this 'InvalidSize' error before? If it didn't work for most people I would say there is a bug in fastboot calculating the last data chunk size. Could this be a hardware problem?

Hi I had the same issue with my shield tablet K1. I finally got my tablet working again by flashing the last TWRP and installing lineage os 14.1.
I can't post the link as i am a newbie but you can google : "How to install LineageOS on the Nvidia Shield Tablet ".
Hope that can help someone.

tf700 softbreak or hardbreak?

hello dear members.
i force restarted my tf700 in the middle of twrp formatting internal memory.after reboot twrp showed 0mb memory so i rebooted again and twrp just started to loop.i erased recovery, boot,misc,cach,system,user with fastboot.
i have no twrp to use adb command for getting partition blob file.
my device can go to bootloader but when ever i try to flash twrp recovery.img or stock blob file i get these errors:
most of all this one comes:
FAILED (command write failed (No such device or address))
other errors:time out or data transfer error(unknown error)
fastboot devices shows my device in the list but i get the errors.
i also had to rewire my data cable to a new usb2 connector head because i can't find new cable for my tablet in my country.as i have seen in the diagram tf700 only uses usb2 for data connection.
is my device hard broken or can it be repaired?
is it the cable?
please help me.
thank you

sx57 said:
hello dear members.
i force restarted my tf700 in the middle of twrp formatting internal memory.after reboot twrp showed 0mb memory so i rebooted again and twrp just started to loop.i erased recovery, boot,misc,cach,system,user with fastboot.
i have no twrp to use adb command for getting partition blob file.
my device can go to bootloader but when ever i try to flash twrp recovery.img or stock blob file i get these errors:
most of all this one comes:
FAILED (command write failed (No such device or address))
other errors:time out or data transfer error(unknown error)
fastboot devices shows my device in the list but i get the errors.
i also had to rewire my data cable to a new usb2 connector head because i can't find new cable for my tablet in my country.as i have seen in the diagram tf700 only uses usb2 for data connection.
is my device hard broken or can it be repaired?
is it the cable?
please help me.
thank you
Click to expand...
Click to collapse
I don't think that your device is hardbrick?
Maybe not the cable either.
Do you know the difference between "erase" and "format"? The answer may fix your device. Good lucks.......:fingers-crossed:

The tablet us not hard bricked, but the cable could be a problem. Do all fastboot commands fail? Including: fastboot reboot, fastboot format userdata?
If yes either the cable is bad or you hot wrong drivers....
If you can fix the fastboot problem you can get the tablet back.

berndblb said:
The tablet us not hard bricked, but the cable could be a problem. Do all fastboot commands fail? Including: fastboot reboot, fastboot format userdata?
If yes either the cable is bad or you hot wrong drivers....
If you can fix the fastboot problem you can get the tablet back.
Click to expand...
Click to collapse
If you interrupted the format process, your partition tables are screwed so you need to fix the partitions before trying to flash new blobs.... It is just my guesses for this issue. I hope that the user above has the latest bootloader so he can use the format cmd in fastboot. I believed that some older bootloader did not support the format cmd in fastboot and forgot started fromm what version that it added the format cmd...
Cheers,
LMK

Thank you all for kindly helping me.
Not all fastboot command fail.for example it cheerfully erased my recovery! And other partitions.
Take a look at this log when I tried to format system:
Creating filesystem with parameters:
Size: 805306368
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 3072
Label:
Blocks: 196608
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/49152 inodes and 6355/196608 b
erasing 'system'...
OKAY [ 2.317s]
sending 'system' (14616 KB)...
OKAY [ 4.666s]
writing 'system'...
OKAY [ 1.373s]
finished. total time: 8.379s
C:\Program Files (x86)\Android\android-sdk\platform-tools
sh system blob
sending 'system' (800927 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.007s
C:\Program Files (x86)\Android\android-sdk\platform-tools
As you see after system format I still can’t flash stock blob or recovery.if format user data fails at sending user data (second step after erase)but formar system completes successfully.
Any ideas what to do or how repartition the my tablet.

update: i also noticed that after every successful format system my device hangs at bootloader an d becomes unknown device so i have to reboot into bootloader again.every try at system blob flash comes with the mentioned errors in my original post.
C:\Program Files (x86)\Android\an
ta
Creating filesystem with paramete
Size: 61415620608
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14994048
Block groups: 458
Reserved block group size: 10
Created filesystem with 11/375193
erasing 'userdata'...
OKAY [ 38.151s]
sending 'userdata' (141163 KB)...
FAILED (data transfer failure (Un
finished. total time: 43.192s
C:\Program Files (x86)\Android\an
ta
Creating filesystem with paramete
Size: 61415620608
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14994048
Block groups: 458
Reserved block group size: 10
Created filesystem with 11/375193
erasing 'userdata'...
OKAY [ 38.392s]
sending 'userdata' (141163 KB)...
FAILED (data transfer failure (Un
finished. total time: 43.436s
every format userdata fails but format system succeeds.cache partition can be formatted too.

fastboot getvar all reports my bootloader locked! it's wiered.
ootloader) version-bootloader: 1.0
ootloader) version-baseband: 2.0
ootloader) version: 0.4
ootloader) serialno: 015d29955b43f613
ootloader) mid: 001
ootloader) product: Cardhu
ootloader) secure: yes
ootloader) unlocked: no
ootloader) uart-on: yes
ootloader) partition-size:bootloader: 0x0000
ootloader) partition-type:bootloader: basic
ootloader) partition-size:recovery: 0x000000
ootloader) partition-type:recovery: basic
ootloader) partition-size:boot: 0x0000000000
ootloader) partition-type:boot: basic
ootloader) partition-size:system: 0x00000000
ootloader) partition-type:system: ext4
ootloader) partition-size:cache: 0x000000001
ootloader) partition-type:cache: ext4
ootloader) partition-size:userdata: 0x000000
ootloader) partition-type:userdata: ext4
l:
nished. total time: 0.237s

sx57 said:
fastboot getvar all reports my bootloader locked! it's wiered.
ootloader) version-bootloader: 1.0
ootloader) version-baseband: 2.0
ootloader) version: 0.4
ootloader) serialno: 015d29955b43f613
ootloader) mid: 001
ootloader) product: Cardhu
ootloader) secure: yes
ootloader) unlocked: no
ootloader) uart-on: yes
ootloader) partition-size:bootloader: 0x0000
ootloader) partition-type:bootloader: basic
ootloader) partition-size:recovery: 0x000000
ootloader) partition-type:recovery: basic
ootloader) partition-size:boot: 0x0000000000
ootloader) partition-type:boot: basic
ootloader) partition-size:system: 0x00000000
ootloader) partition-type:system: ext4
ootloader) partition-size:cache: 0x000000001
ootloader) partition-type:cache: ext4
ootloader) partition-size:userdata: 0x000000
ootloader) partition-type:userdata: ext4
l:
nished. total time: 0.237s
Click to expand...
Click to collapse
It is the first time that I hear that the bootloader is relocked.... Obviously, it is reported that your bootloader is still locked.
You are using the "erase" and "format" interchangeable in your posts above so I am confused which cmd that you used in the fastboot mode. Did you use this cmd in fastboot?
Code:
fastboot format userdata
If not, then you can give it a try to see what is going on after that, good luck....:fingers-crossed:

LetMeKnow said:
It is the first time that I hear that the bootloader is relocked.... Obviously, it is reported that your bootloader is still locked.
You are using the "erase" and "format" interchangeable in your posts above so I am confused which cmd that you used in the fastboot mode. Did you use this cmd in fastboot?
Code:
fastboot format userdata
If not, then you can give it a try to see what is going on after that, good luck....:fingers-crossed:
Click to expand...
Click to collapse
thanks for answering.yes i used format userdata and i sent the log for it.it always finished in these 3 errors
1-no such device or address.
2-data transfer error
3-timeout
format system works well
top left of my tf700screen us written key driver not found..booting os and the some version information.
if i select rck or android i get unrecoverable bootloader error (0x0000000)in red color.i have no system or recover so the error is related to that i believe.before erasing recover it worked go into twrp which started looping.
i use erase when i use erase command and i use format when i use format command.sorry for causing confusion mate.

LetMeKnow said:
It is the first time that I hear that the bootloader is relocked.... Obviously, it is reported that your bootloader is still locked.
Click to expand...
Click to collapse
No, I get the same return with getvar all. And I guarantee you - my bootloader is unlocked
We have to remember that fastboot is a very generic Android tool... doesn't work the same on all platforms..
Probably
Code:
(bootloader) uart-on: yes
is the more relevant entry here. "Unlocking the bootloader" on this device is nothing more than gaining the ability to flash partitions with files not signed by Asus. The BL is still encrypted and proprietary....
sx57 said:
thanks for answering.yes i used format userdata and i sent the log for it.it always finished in these 3 errors
1-no such device or address.
2-data transfer error
3-timeout
format system works well
top left of my tf700screen us written key driver not found..booting os and the some version information.
if i select rck or android i get unrecoverable bootloader error (0x0000000)in red color.i have no system or recover so the error is related to that i believe.before erasing recover it worked go into twrp which started looping.
i use erase when i use erase command and i use format when i use format command.sorry for causing confusion mate.
Click to expand...
Click to collapse
Sigh...
Unfortunately you cannot really rely on fastboot return messages. Especially if you're trying this on Win10!!!!!!!
I'm getting totally frustrated with this OS. I get a positive return for "fastboot devices" and then it does nothing for any subsequent command. Gives me a "finished" for "fastboot reboot" but the tablet never reboots. Basically it does not respond to any fastboot commands.
Until I boot the tablet into recovery. Try a few adb commands - everything works. Go "adb reboot-bootloader" to get into fastboot mode and all the sudden all fastboot commands work???????????????
So that together with your patched cable introduces enough ????? that it's almost impossible to isolate the cause.
But the only way I have seen people (many, many people) recover from an "unrecoverable bootloader error" is by flashing the stock blob in fastboot. You gotta get that working.....
If you've tried this on a USB 3.0 port, try a USB 2.0. Reboot the PC, reboot the tablet when switching ports.
If you can get your hands on Linux machine, try that. Or try this live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Good luck!

berndblb said:
No, I get the same return with getvar all. And I guarantee you - my bootloader is unlocked
We have to remember that fastboot is a very generic Android tool... doesn't work the same on all platforms..
Probably
Code:
(bootloader) uart-on: yes
is the more relevant entry here. "Unlocking the bootloader" on this device is nothing more than gaining the ability to flash partitions with files not signed by Asus. The BL is still encrypted and proprietary....
Sigh...
Unfortunately you cannot really rely on fastboot return messages. Especially if you're trying this on Win10!!!!!!!
I'm getting totally frustrated with this OS. I get a positive return for "fastboot devices" and then it does nothing for any subsequent command. Gives me a "finished" for "fastboot reboot" but the tablet never reboots. Basically it does not respond to any fastboot commands.
Until I boot the tablet into recovery. Try a few adb commands - everything works. Go "adb reboot-bootloader" to get into fastboot mode and all the sudden all fastboot commands work???????????????
So that together with your patched cable introduces enough ????? that it's almost impossible to isolate the cause.
But the only way I have seen people (many, many people) recover from an "unrecoverable bootloader error" is by flashing the stock blob in fastboot. You gotta get that working.....
If you've tried this on a USB 3.0 port, try a USB 2.0. Reboot the PC, reboot the tablet when switching ports.
If you can get your hands on Linux machine, try that. Or try this live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Good luck!
Click to expand...
Click to collapse
thank you very much for helping me.i am using win7 my frirnd.
I am gonna do what you kindly suggested to see if i get it working.i will try to get another cable from someone if any of my friends have one by chance.is there a command to see if bootloader is really still unlocked?
I will post the results but getting a cable is gonna take a few days if possible at all.in the meantime i will try other solutions.thank you all my friends.please post if any othetr solution comes to your mind.

Don't worry. There's no way to lock the tablet again unless through Asus.
Watch the screen when you turn it on. Even in this state it should say: The device is unlocked

hellooooooooooooooooo.my tablet is alive and the problem is finally solved.thank you all my friends specially berndblb. i finlally found and bought a new cable and after some problems with different PCs(errors same as i mentioned in my original post) i succeeded.
here are some points that i think need to be emphasized upon:
a direct usb port was necessary for me.it worked when the device was connected directly to my Iconia (windows pc tablet) w700's only usb 3 port.(usb 2 works but a direct port is needed,hubs make more problems.)
in windows XP fastboot was completely useless and didn't work and would just stuck on commands.(most probably needed another driver)
look here please :http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Buster99's excellent solution needed to be done step by step.i had to erase the mentioned partitions and only after that,blob file was flashed successfully.
thank you all for your help.