Database Info

[Q] flashed to 4.04, bricked phone

A long time ago I rooted my phone and put CM9 on it. I decided I wanted to go back and try Jelly Bean (from factory then go outwards).
I had a difficult time with the CM flash and found one that worked, and thought I was good to go.
My phone: gt-i9020a nexus s
Product name: Herring
HW version 16
boot loader: i 9020xxkl
carrier att
fastboot enabled
unlocked state.
I can launch the official 2.3.6 (Build GRK39F), from google
then the OTA updated kicks in and the phone is stuck at 'boot' Google logo on the screen.
I have done the information below and the same keeps happening...
link: http://forum.xda-developers.com/showthread.php?t=1586845
first of all, the VQ8PQk is a patch file, not a full rom. So flashing that on something else than 2.3.6 will never work. Get into clockworkmod recovery wipe wverything from the mounts and storage menu, and then flash this file : http://android.clients.google.com/pa...o/ZD3PyN0t.zip and THEN this : http://android.clients.google.com/pa...o/hR7QFEtn.zip
and other steps I could try to work around, none of them seem to work.
Am I missing anything?
Thanks!

Use the full factory rom images (sojuaxxxx) from Google.
https://developers.google.com/android/nexus/images#sojua
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Edit: install CYGWIN to have linux-like commands (works with tar, adb, fastboot) in windows.

Do you have a backup (preferrably CWM backup) that you have prior to trying to get JB working? If so keep that handy, and preferrably store it on the PC. Titanium backup can ease migrating apps after a wipe and is highly recommended, so do one of these too if you havn't already.
After you make sure you have a solid backup with the information that you want/need on the phone, i would just start fresh. The best way to do this is to do a factory image flash (note: you want sojua if you have the 850MHz variant which is from AT&T). Flashing these will wipe all user data and the /system partition, the sdcard won't be touched. Basically you download it, extract it, then hook up your phone in fastboot mode and do the commands as written in the text file (or run it as a script if you know how). I've described it in more detail elsewhere as have others, doing a search should give results pretty quickly
This will become a factory install of android as given by google, in your chosen version. I'd go straight ot JB and then you can see how much you like it. CWM backup data can be extracted if you lost some crucial information in the flashing and all your apps and their data can be easily restored with titanium backup.

morning update
_android_ said:
Use the full factory rom images (sojuaxxxx) from Google.
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Click to expand...
Click to collapse
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..

lost_man said:
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
Click to expand...
Click to collapse
Make sure you use the sojua versions.
Do you mean you finish all the steps and upon reboot, it's stuck on Google boot screen?
What do you mean by you can only get 2.3.6 working? It went past Google boot screen?

** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****

lost_man said:
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
Click to expand...
Click to collapse
Some (quite a few) Nexus S seemed to be vulnerable to Jelly Bean/CM10 update in that the mainboard is toast. I think the only option is to send back for warranty repair. There are some threads on rigging some kind of adapter cable but that will definitely void your warranty (physical mod).

Doesn't sound good, there have been instances where the flash storage has given up and ends up needing a new SoC (the whole mainboard) and similar issues. Some more information would be good to diagnose this better though.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.

-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
Click to expand...
Click to collapse
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!

lost_man said:
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
Click to expand...
Click to collapse
How do i close this thread? It's done, the phone is dead...rma...

[Q] TWRP asking for password/can't mount E/ROM won't load

I'm still somewhat new to all this but after buying my tf700 last December I've been trying out a few things, unlocked/rooted and I have been happily using TWRP and various versions of Cromi X for months without any problem. Suddenly one day it didn't want to boot the ROM anymore and I have no idea the cuase (didn't just flash some kernel or drop the tablet, etc). I have TWRP 2.5.0.0 and CROMI-X 5.0.2.
I've dug through the forums and there doesn't seem to be anyone I can find who's having exactly the same problems. There was no special data I particuarlly needed on the tablet and I have backups on saved elsewhere so I am totally happy to wipe everything and start from scratch. I just want my tablet back. I'm just looking for the easist way to fix this (and I hope there is a way!) so any help is greatly appreciated.
Info is as follows:
Cromi x won't load stuck on ASUS logo. Same goes for cold booting
When I boot into recovery it says "Key driver not found.. Booting OS" at the top left
[when I enter TWRP it asks for password and says it can't mount E as below
when i "cancel" the password request i am taken to the usual home screen but installing from internal storage shows no files and a size of "0"
strangely I can get into the Micro SD card and load CROMI X from there which all goes through normally but at the finish when I'm going to reboot it says "No OS Installed!" and after restarting i'm back to same problem
I'm not getting the Fastboot USB logo I think I'm supposed to get in recovery when it is plugged it into my PC and ADB sideload in TWRP also not working (not so experienced with these though)
When I try to wipe data in TWRP I get "Failed" the message about being unable to mount E below
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/staging'
E: Unable to find partition size for '/data'
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E:TNFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E: Unable to set emmc bootloader message.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'​

strangestribu said:
E: Unable to mount '/system'
E: Unable to mount '/cache'
Click to expand...
Click to collapse
Looks like some issue with the internal eMMC. Reboot your tablet into TWRP, connect it to your PC and run on the PC:
Code:
adb shell dmesg > dmesg.txt
adb shell ls -l /dev/block/mmc* > mmc.txt
Post the 2 resulting files.

can't seem to connect through PC
_that said:
Looks like some issue with the internal eMMC. Reboot your tablet into TWRP, connect it to your PC and run on the PC:
Code:
adb shell dmesg > dmesg.txt
adb shell ls -l /dev/block/mmc* > mmc.txt
Post the 2 resulting files.
Click to expand...
Click to collapse
Thanks very much for this. The problem I am having is I can't past the "error: device not found" message I get in the CMD on my (windows 7) PC. (yes I am opening the command line window on my android ADB folder). In fact the tablet doesn't appear in the Device Manager either. I'll admit I'm not so experienced working on the tablet through the PC (though I'm guessing I'm about to learn a lot), but I think the fact I get "Failed" when trying to ADB sideload in TWRP and nothing in the Device Manager is a big part of my problem though I'm stumped how to fix it.
Any ideas?

strangestribu said:
In fact the tablet doesn't appear in the Device Manager either.
Click to expand...
Click to collapse
You may not have the correct drivers, but even then it should at least appear as unknown device.
I don't know which drivers you need for Windows (it's easier under Linux) but maybe someone else can help you here. I remember sbdags once posted which drivers worked for him, maybe you find it using the search function.

Try these drivers:

PC doesn't recognize tablet is plugged in
sbdags said:
Try these drivers:
Click to expand...
Click to collapse
_that said:
You may not have the correct drivers, but even then it should at least appear as unknown device.
I don't know which drivers you need for Windows (it's easier under Linux) but maybe someone else can help you here. I remember sbdags once posted which drivers worked for him, maybe you find it using the search function.
Click to expand...
Click to collapse
Thanks both for this, but the problem that I'm facing is I can't seem to get my PC to recognize the existence of the tablet (connected via USB with TWRP running) even as an unknown device. Because of this I'm not sure how to get the drivers loaded. Also have loaded Android SDK Build-Tools and Google USB Driver through the Android SDK Manager. That doesn't seem to solve it either.
Not surprisingly when I run fastboot from a cmd line window and look for adb devices the list is blank.
Not sure what else to do. Would be willing to create a second Ubuntu boot on my machine if using linux would help me get this fixed. Just at a loss about what to do.
Any further insights are welcome!!!

strangestribu said:
Thanks both for this, but the problem that I'm facing is I can't seem to get my PC to recognize the existence of the tablet (connected via USB with TWRP running) even as an unknown device.
Click to expand...
Click to collapse
Is the tablet connected directly to the PC? No dock, no USB hub?
To check if your USB cable works, you can boot your tablet into APX mode (hold volume-up while turning on). The screen will stay black but the backlight should be on. You can only do something useful in this mode if you have previously created your blob file for wheelie/nvflash, but at least your PC should recognize the Tegra APX device (vendor 0x0955, device 0x7030).
If that also doesn't work, boot any live Linux distribution and run "lsusb". If that also shows no trace of the tablet (vendor ID should be 0b05 for normal operation or recovery, or 0955 for APX mode), then either your cable or your tablet's USB connection is broken.

Am I bricked?
_that said:
Is the tablet connected directly to the PC? No dock, no USB hub?
To check if your USB cable works, you can boot your tablet into APX mode (hold volume-up while turning on). The screen will stay black but the backlight should be on. You can only do something useful in this mode if you have previously created your blob file for wheelie/nvflash, but at least your PC should recognize the Tegra APX device (vendor 0x0955, device 0x7030).
If that also doesn't work, boot any live Linux distribution and run "lsusb". If that also shows no trace of the tablet (vendor ID should be 0b05 for normal operation or recovery, or 0955 for APX mode), then either your cable or your tablet's USB connection is broken.
Click to expand...
Click to collapse
Well you gave some great advice...I hadn't thought that the cable (which charges the tablet perfectly) could be the issue. I borrowed a cable from a friend who has the same machine and voila, recognized and could get into fastboot.
...and then with that problem solved, things got really bad.
I attempted to reflash TWRP on the tablet by pushing via fastboot as described on TeamWin's website. All was going perfectly until the tablet froze partway through the flash. Now when i power on, whether or not I hold vol down, I get a brief .5 seconds of the "Asus Inspiring innovation..." logo with a blue bar that goes up to about 75%, with "The device is unlocked" in the corner. After this brief 1/2 second it goes directly into APX -- black screen (though possibly back-lit) but, with the working Asus cable, Windows 7 recognizes the tablet as "Unknown Device"
I fear the device is now bricked as all the forums I've read seem to imply this. No, I didn't really know about creating a blob file for wheelie/nvflash before so don't have one (sure have read plenty about it now).
So...is this the end? Can I create a working blob file from my friend's device (I'm guessing not or it would have been thought of before)? or any other solution?
Or if not I've heard you can replace the motherboard though this is really unknown territory for me...I'm a bit curious so would be up for having a go but don't want to sink money into a helpless situation. Plus I don't know why any of this has happened in the first place so i fear there may be other parts that are not working properly.
Any useful insights on how to solve this problem I've created for myself would be greatly appreciated.

Sounds like it is bricked if you can't get into the bootloader.
What was the exact command you used to 'push' TWRP and which file did you use?

strangestribu said:
Well you gave some great advice...I hadn't thought that the cable (which charges the tablet perfectly) could be the issue. I borrowed a cable from a friend who has the same machine and voila, recognized and could get into fastboot.
...and then with that problem solved, things got really bad.
I attempted to reflash TWRP on the tablet by pushing via fastboot as described on TeamWin's website. All was going perfectly until the tablet froze partway through the flash. Now when i power on, whether or not I hold vol down, I get a brief .5 seconds of the "Asus Inspiring innovation..." logo with a blue bar that goes up to about 75%, with "The device is unlocked" in the corner. After this brief 1/2 second it goes directly into APX -- black screen (though possibly back-lit) but, with the working Asus cable, Windows 7 recognizes the tablet as "Unknown Device"
I fear the device is now bricked as all the forums I've read seem to imply this. No, I didn't really know about creating a blob file for wheelie/nvflash before so don't have one (sure have read plenty about it now).
So...is this the end? Can I create a working blob file from my friend's device (I'm guessing not or it would have been thought of before)? or any other solution?
Or if not I've heard you can replace the motherboard though this is really unknown territory for me...I'm a bit curious so would be up for having a go but don't want to sink money into a helpless situation. Plus I don't know why any of this has happened in the first place so i fear there may be other parts that are not working properly.
Any useful insights on how to solve this problem I've created for myself would be greatly appreciated.
Click to expand...
Click to collapse
If you cannot get into the bootloader and APX mode is your only access .... without nvFlash - sorry, it's a brick :crying:
The blobs for nvFlash are device specific, so somebody elses would not help you.
Your only option is to sell it for parts or have the main board replaced.
I don't have experience with that (thank God), but there are tear-down videos and instructions on iFixit.com. Maybe that'll help you decide if it would be something you can do yourself.
Otherwise sending it to Asus and have them fix it would be your only option. It is expensive....
My condolences....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

TF300T help
I've worked on this now for about 12 hours. I cannot figure it out. I run into the same roadblocks. I know this is an old thread, hopefully by now there's a solution for this kind of issue.
Can this be fixed in Odin or platform tools or something?
I've got TF300T where I believe I bungled the process by format/wiping from bootloader menu instead of TWRP. It's technically not bricked at all. But it's screwed up in the following ways (I was trying to get it to be a Clean Rom tablet, and there were so many sets of instructions, had them all open, and was trying to be careful about this, I've rooted and ROMed so many times and this is the first time I haven't been able to solve the issue in a reasonable amount of time)
-TWRP 2.5.0.0 asks for password, no pw ever set anywhere, tried all possibles that could feasibly be, but nothing works. This TWRP issue causes all cards to be invisible, it wiped by external SD, shows internal SD as having nothing in it but this is false as the OS boots ok (see below).
-cold boot or reboot leads to going straight into TWRP 2.5.0.0
-issuing command 'adb reboot bootloader' while in TWRP does take me into (bootloader?) 3 iconed menu, this menu is the only way I can boot the tablet into the normal Android system
-cannot factory restore the tablet from normal Android as it goes straight into TWRP following this action
-in the bootloader 3 iconed screen it is not seen by issuing that 'devices' command,
-thus cannot do 'fastboot -i 0x0b05 flash staging blob', TWRP disallows this also as the damn thing is locked down by a non-existent password.
I issued your commands:
DMESG.TXT (output too long to post here, exceeds xda allowable) &
MMC.TXT
brw------- 1 root root 179, 0 Jul 12 00:32 /dev/block/mmcblk0
brw------- 1 root root 179, 1 Jul 12 00:32 /dev/block/mmcblk0p1

Without a working fastboot connection you are one or two steps away from a hard brick. Proceed with caution!
chickenmusket said:
Can this be fixed in Odin or platform tools or something?
Click to expand...
Click to collapse
Odin is for Samsung devices only, the platform tools give you adb and fastboot, see below
TWRP 2.5.0.0 asks for password, no pw ever set anywhere, tried all possibles that could feasibly be, but nothing works. This TWRP issue causes all cards to be invisible, it wiped by external SD, shows internal SD as having nothing in it but this is false as the OS boots ok (see below).
Click to expand...
Click to collapse
Usually the reason if TWRP is asking for a password is a corrupted data partition. The recovery cannot read /data, so it assumes that it's encrypted and it asks for the password. Surprising is that you can boot into Android if your data partition is corrupted!!
-cold boot or reboot leads to going straight into TWRP 2.5.0.0
-issuing command 'adb reboot bootloader' while in TWRP does take me into (bootloader?) 3 iconed menu, this menu is the only way I can boot the tablet into the normal Android system
Click to expand...
Click to collapse
That's what stumps me... Most of the time, if you use the "Wipe Data" option in the bootloader or do a factory reset from within the stock rom with TWRP installed, you end up in a forced reboot to recovery loop - no boot to rom, no boot into the bootloader. So you are saying a normal boot goes straight into TWRP, but you can adb reboot into the bootloader and from there, by selecting the Android icon, boot into the rom??
cannot factory restore the tablet from normal Android as it goes straight into TWRP following this action
Click to expand...
Click to collapse
That's totally normal because the factory reset command calls the recovery to perform a wipe of data. Since you don't have the stock recovery it calls TWRP - but TWRP cannot resolve the command. Read this for background, but you probably don't need bootit.ko since you can boot into the bootloader anyway.. http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
in the bootloader 3 iconed screen it is not seen by issuing that 'devices' command,
-thus cannot do 'fastboot -i 0x0b05 flash staging blob', TWRP disallows this also as the damn thing is locked down by a non-existent password.
Click to expand...
Click to collapse
This is the part that worries me. Without a fastboot connection you could be dead in the water pretty quickly. And that's the problem you should tackle first.
How did you get TWRP installed on the tablet? Not in fastboot? Most often fastboot not working is a PC driver problem. Read this to get fastboot working:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
There's also one very important information missing from your post: What bootloader are you on? your bootloader and recovery have to match and the rom you flash has to match both.
You COULD try to just format data in TWRP which should take care of the "missing password" problem and then flash the rom you want to run, but you better make sure the bootloader supports the rom!
And again - if that goes wrong and you don't have fastboot working, you could end up with a paperweight. Be careful!

Thanks for taking the time to answer. Understanding more of this is helpful (doesn't drive me as mad when I know that I don't need to keep trying passwords in TWRP). I'd like to be in a position where I knew knew all this stuff & could be helping others instead.
I thought the reason for all the lock ups was my wiping data from the 3 iconed menu rather than from twrp (the latter was supposed to do)
YES >>>So you are saying a normal boot goes straight into TWRP, but you can adb reboot into the bootloader and from there, by selecting the Android icon, boot into the rom?? >>>YES
How did you get TWRP installed on the tablet? Not in fastboot? Most often fastboot not working is a PC driver problem.
>>I got TWRP into the tablet by issuing this command
fastboot -i 0x0b05 flash recovery twrp.blob
>>Tablet is already unlocked via the Asus way. Am I supposed to go through a procedure to re-do fastboot somehow?
There's also one very important information missing from your post: What bootloader are you on? your bootloader and recovery have to match and the rom you flash has to match both.
>>Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
and when I boot into this OS,
>>Android version 4.2.1
Kernel 3.1.10-g215ae8bf / [email protected]#1
Build: JOP40D.US_epad-10.6.1.27.5-20130902
Pad EC version PAD-EC20T-0216 (too much info?)
You COULD try to just format data in TWRP which should take care of the "missing password" problem and then flash the rom you want to run, but you better make sure the bootloader supports the rom!
>>Cannot format data in TWRP, after entering yes to confirm
E: unable to find partition size for '/misc'
E: ...a bunch of unable to finds, unable to mount, unable to wipe, unable to cache
everything unable to ...
I had tried that already.
Do you think I should try this:
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495/page7

chickenmusket said:
Thanks for taking the time to answer. Understanding more of this is helpful (doesn't drive me as mad when I know that I don't need to keep trying passwords in TWRP). I'd like to be in a position where I knew knew all this stuff & could be helping others instead.
Click to expand...
Click to collapse
Stick around enough long enough, read a ton and you will be
I thought the reason for all the lock ups was my wiping data from the 3 iconed menu rather than from twrp (the latter was supposed to do)
Click to expand...
Click to collapse
It probably was. Although with a different effect than usual...
YES >>>So you are saying a normal boot goes straight into TWRP, but you can adb reboot into the bootloader and from there, by selecting the Android icon, boot into the rom?? >>>YES
How did you get TWRP installed on the tablet? Not in fastboot? Most often fastboot not working is a PC driver problem.
>>I got TWRP into the tablet by issuing this command
fastboot -i 0x0b05 flash recovery twrp.blob
>>Tablet is already unlocked via the Asus way. Am I supposed to go through a procedure to re-do fastboot somehow?
There's also one very important information missing from your post: What bootloader are you on? your bootloader and recovery have to match and the rom you flash has to match both.
>>Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
and when I boot into this OS,
>>Android version 4.2.1
Kernel 3.1.10-g215ae8bf / [email protected]#1
Build: JOP40D.US_epad-10.6.1.27.5-20130902
Pad EC version PAD-EC20T-0216 (too much info?)
You COULD try to just format data in TWRP which should take care of the "missing password" problem and then flash the rom you want to run, but you better make sure the bootloader supports the rom!
>>Cannot format data in TWRP, after entering yes to confirm
E: unable to find partition size for '/misc'
E: ...a bunch of unable to finds, unable to mount, unable to wipe, unable to cache
everything unable to ...
I had tried that already.
Do you think I should try this:
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495/page7
Click to expand...
Click to collapse
Yes. That would be the safest way to go, but you need fastboot for it. I thought you don't get the device ID returned when issuing 'fastboot devices' while in the bootloader??
As long as you can boot into the BL you don't need bootit.ko so follow that guide from the "fastboot devices" input

Correct, I do not have a fastboot ID.

chickenmusket said:
Correct, I do not have a fastboot ID.
Click to expand...
Click to collapse
That's what i mean: Probably a driver problem. Open Device Manager on the PC. then connect/disconnect the tablet while in the bootloader. Check if anything changes, check for yellow triangle next to the driver if it shows as Fastboot interface.
You can also try this in adb shell in recovery since you do have that working. This will also format your data partition:
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10

The issue was resolved with the help of Joshua Lynch. He saw my post and PMed me. For those that are losing hope like I was, if you're coming back to this old tablet, all is not lost. I will post how this resolved as soon as I have time. Thanks for the answers. Bounty has been claimed.
the issue was a driver. the computer would only have one driver installed at a time and installing fastboot driver again fixed the not seen issue. I had installed another driver (as part of this process, and it eliminated the presence of fastboot driver), and was racking my brains because I didn't think to reinstall the original fastboot driver.

I had help from Joshua Lynch a couple months back on this. It turns out that the reason the tablet wasn't seen was indeed a driver issue. What had confused it with me is that I did physically install both drivers fastboot & adb. However, my system only allowed one to be active at a time. So when I was trying to, if I'm remembering this correctly, fastboot into the tablet to console, it wasn't seen because adb was the active driver. All that needed to be done was remove adb & put in fastboot.
Just to let you all know, I did a full one & zero wipe of the tablet & installed Zombi-Pop rom with Joshua's help. The tablet was still slower than hell. Slower than any device I've ever used. I'm talking 5 to 15 second delay time from when touching something & getting a response. I found that disabling everything google (except play store & play services) helped a great deal.
But the tablet has never returned to its former speed prior to the asus update. Tinfoil hat: I have this feeling that they sent out an update that permanently screwed up the hardware on purpose.

berndblb said:
That's what i mean: Probably a driver problem. Open Device Manager on the PC. then connect/disconnect the tablet while in the bootloader. Check if anything changes, check for yellow triangle next to the driver if it shows as Fastboot interface.
You can also try this in adb shell in recovery since you do have that working. This will also format your data partition:
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10
Click to expand...
Click to collapse
Question: do you know if the original stock software that the tablet came with (before the update) can be installed? Is there a full set of instruction on this (and the stock rom)? I've got a ton of files (some roms, some files from asus website) downloaded for this tablet. I've taken a break from this thing, returning to it now... Ready to take another crack at it.
If someone wants to make some money and help me out with this, I'll pay them a total of 50 if all goes well. First 20 for their service to get the thing back on stock, original out of box software and updates disabled, another 30 when I've seen after a few days, that indeed it was done right and fast like it originally was.
Reason for this is that I already gave someone 50 for their help with this and the outcome wasn't acceptable. I've invested a ton of time in this and the $$ put in so far exceeds the value of the tablet.

I cant unlock bootloader!

I have nexus 5 and its bricked, But I cant unlock the bootloader using fastboot ( I think its because I have no rom ). Is there an another way to unlock the bootloader?

The fastboot oem unblock solution is the only way to unlock the bootloader without root.
If you can't do it then you may have hardware issues.

The phone is recognized when you run the command "fastboot devices"? If not, you'll need to get it recognized before issuing fastboot commands to the phone.

If you have no ROM, and the bootloader is locked, you've gotten yourself into quite the predicament. What error does fastboot oem unlock give you?
Sent from my Nexus 5X using Tapatalk

drsn0w said:
If you have no ROM, and the bootloader is locked, you've gotten yourself into quite the predicament. What error does fastboot oem unlock give you?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I get the devices to oem unlock, but when i try and flash a bootloader.img I get this
Owners-iMac:image-hammerhead-mob31e EmilyHaugen$ ./fastboot flash bootloader /Users/owner/Desktop/android/hammerhead-mob31e/bootloader-hammerhead-hhz20h.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.308s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.488s

Strange
Sent from my Nexus 5X using Tapatalk

After unlocking the bootloader, reboot the phone into fastboot and see if the bootloader is still unlocked.
Try relocking the bootloader and then unlock it. If the phone performs a factory wipe in a few seconds, the emmc chip may be damaged.

Primokorn said:
The fastboot oem unblock solution is the only way to unlock the bootloader without root.
If you can't do it then you may have hardware issues.
Click to expand...
Click to collapse
I think that has a root.
My friend rooted it and than remove kingroot (without unroot).
What the way to unlock bootloader with root?
Thenx

matan10 said:
I think that has a root.
My friend rooted it and than remove kingroot (without unroot).
What the way to unlock bootloader with root?
Thenx
Click to expand...
Click to collapse
BootUnlocker app

Primokorn said:
BootUnlocker app
Click to expand...
Click to collapse
But I have no rom. And I cant install rom because my bootloader is locked

matan10 said:
But I have no rom. And I cant install rom because my bootloader is locked
Click to expand...
Click to collapse
I know but you asked. No other solution mate except going to a repair shop.

Hello,
First some background and credits:
There are a few ways to brick a phone. Sometimes it's lack of experience, sometimes it's an accidental thing, sometimes there just isn't an explanation for what went wrong... (share your experience here, if you wish). For me, I owned my OPO for about 4 hours before things went wrong. First thing I did was I rooted it and installed TWRP. After creating a nandroid backup of the stock image I installed my favorite custom ROM and restored all my apps with TiBu. Everything was great and configured just the way I wanted it. I then wiped my old phone (Nexus 4), installed a new ROM and got it all ready for my wife. She was so excited to get rid of her GNex and move up to the N4. But then, for whatever reason, I opened an app on my OPO that I used to manage, download, and install kernels with. It came up with "there is a new kernel update!" and I instinctively clicked on "Install". 10 seconds later my phone was bricked. Nothing came on the screen, no fastboot, no recovery, nothing to boot to, no way to send data to and from it. The second the screen went black and the phone became lifeless I got that wretched feeling in my gut as I realized I just flashed a N4 kernel on my new OPO. Restoring the kernel management app with TiBu made it act like it's still running on my old phone, and in my excitement I didn't take a second to think things through...
I received a bit of consolation when a quick XDA search revealed that I am not the only dumbass to brick his phone this very way. I joined forces with some pretty smart and desperate people and tried different things, all described in the following thread: http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696. Unfortunately it took us what seemed like many long weeks to figure it all out. Well, in the end a solution was found and I documented it in the the following post: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136.
This was a few months ago, but I recently noticed many people continue to search for these directions and have problems finding them hidden among many pages and other threads, so I've decided to put this stand alone thread with these, now updated, directions.
Let me get one more thing straight, for the record. I did not find the way to unbrick the OPO. In fact I wasn't even the very first one to do it. It was a collective effort of few people who tried many different approaches and ideas, and I eventually documented these steps for others to follow. Being said, the following people deserve credit as well: @os_man, @rezor92, @Mnt-XDA. If I am forgetting other significant names and efforts, I apologize.
***CAUTION***
The following instructions are for hardware bricked devices ONLY and will not work on soft bricked devices. To determine whether your device is soft or hard bricked, click the button below:
Hardware brick
A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB. You might have a bricked OPO as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition.
Software brick
Please do not attempt to use these directions if your phone is soft bricked. A software bricked OPO is one that might be stuck in a bootloop, but has a working bootloader, recovery partition, fastboot, or adb. If you press the power button and images appear on the screen and you are able to enter fastboot mode (Power + VolUP) or recovery (Power + VolDOWN) then your device is soft bricked. This thread does not encompass soft brick recovery, the instructions below do not apply and will not work on these phones. Consult other threads for help on soft bricked devices.
If based on the above explanation of differences between soft and hard bricks you determined your device is hard bricked, here's what you will need to do...
1:
Download Color.zip from https://goo.gl/iDby26
After downloading, unzip the archive on your computer.
2:
Next, you need proper Windows drivers. There are architectural differences between Windows XP and Windows 7/8, so follow the directions below that pertain to you. One quick note about the drivers: the installation and process is very simple and straightforward on Windows XP (I also tested successfully on Windows 2003), but proves to be quite a challenge when running on Windows 7 or 8. Over and over people report issues when attempting the unbrick procedure on Windows 7/8, some have more luck than others. Being said, if you have access to a Windows XP computer, I highly recommend that you use that. If you have no choice but to use a Windows 7 or 8 computer and have problems, please share them here and read others' experiences.
So first, by now you probably tried a few different things to fix your phone and you've already installed some drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried so far and use the ones listed below. Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted. Then:
2a:
Windows XP users:
You are in luck, driver installation is straightforward. Go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through the prompts.
2b:
Windows 7 and Windows 8:
These operating systems block unsigned driver installations by default. Follow these steps (thanks @nag4pl for testing these):
Download and extract these Qualcomm 2012 drivers: https://goo.gl/cIKnFZ. Connect your bricked phone and let Windows do its thing.
Now something very essential you need to do here is to execute two commands to allow you to install unsigned drivers for QHUSB_BULK. Click on Start Menu > Type cmd.exe > Right Click and Run as Administrator.
In the CMD window type in the following commands (hit enter after each):
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Code:
bcdedit.exe -set TESTSIGNING ON
After both the commands should run successfully, restart your computer.
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software. For driver software location provide the path where you have extracted Qualcomm 2012 drivers you downloaded and make sure 'Include Subfolders' is checked. Proceed through all the installation prompts ignoring any warnings.
3:
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.
If you don't see your phone in the list of com devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.
Once you see the phone in the list, click Start. You should see the programs start writing different files to the phone. Each time it writes a file you'll see a progress bar. Once you see this process happening, smile, you know you will be good to go... After all files are written, the com line with your device will turn green. You're good, unplug and reboot your phone. It will boot to ColorOS, the Chinese OS that comes on OPO.
4:
Optional Steps:
Your phone is no longer bricked. You now have a few options to get back to stock. The easiest way is to use a toolkit from http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418, or you can flash an image manually by following directions from: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541. Download the proper image zip and after extracting it, run the following commands in fastboot mode:
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.
That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue.
Good luck! Share your experience here and let me know if I can improve this thread.
Please click the Thanks button if you found the above guide useful.
Click to expand...
Click to collapse
I saw this guide but its for one plus one.
Its any way to do this guide for nexus 5?

http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732/page40
This is the link

Can you boot into fastboot mode? If you can, connect the phone, run the fast boot command "fastboot oem unlock".

audit13 said:
Can you boot into fastboot mode? If you can, connect the phone, run the fast boot command "fastboot oem unlock".
Click to expand...
Click to collapse
I ran this command but it still locked. I think because its need to reboot after run the unlock command, but I cant reboot because I have no rom.

After you type "fastboot oem unlock", you should get a prompt on the phone to say "yes".

audit13 said:
After you type "fastboot oem unlock", you should get a prompt on the phone to say "yes".
Click to expand...
Click to collapse
Right. I did it and its looks like its unlocked, but after reboot to bootloader it was back seems locked.

If the bootloader relocks itself on reboot, the Emmc chip is damaged and needs to be replaced.

audit13 said:
If the bootloader relocks itself on reboot, the Emmc chip is damaged and needs to be replaced.
Click to expand...
Click to collapse
How much does a repair for switch emmc chip?
If I buy this chip, can I switch it alone?

It's the memory chip on the motherboard that needs to be replaced. Unless you have specialized soldering equipment, the best solution would be to find a nexus 5 with a smashed screen and working internal components.

Phone won't turn on, no system

I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.

zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.

Naveenthemi said:
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.
Click to expand...
Click to collapse
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?

Fcyrp Zip Need to Flash After Flash any Custom Rom
And Come in Telegram Official Group For Any Support of Redmi Note 7 Pro https://t.me/Rn7proGlobal

zhou111 said:
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?
Click to expand...
Click to collapse
Yes it's hardbricked for sure! But are you sure MiFlash doesn't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...

Naveenthemi said:
Yes it's hardbricked for sure! But are you sure MiFlash doens't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...
Click to expand...
Click to collapse
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.

zhou111 said:
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.
Click to expand...
Click to collapse
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)

Naveenthemi said:
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)
Click to expand...
Click to collapse
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.

zhou111 said:
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.
Click to expand...
Click to collapse
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too

Naveenthemi said:
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too
Click to expand...
Click to collapse
I entered the command says waiting for device. how do you flash with adb?

zhou111 said:
I entered the command says waiting for device. how do you flash with adb?
Click to expand...
Click to collapse
Oh that means ADB isn't recognizing it.
There isn't much we can do if ADB doens't recognize it!
Did you look up for Service Centres?

zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.

hackeroid said:
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.
Click to expand...
Click to collapse
He/She said the phone doesn't boot into Fastboot either so that's very unlikely to work :-\

LMV600AM Restore/Ugrade Guide

This restore process is intended for the AT&T V60 (lmv600am) model and will WIPE your data so back it up if you want to keep it!
This process will restore the lmv600am to original factory state for the AT&T v60 v20q build (a11). I’ve dumped all the required partitions from a new replacement phone sent to me by LG. This process uses the Qfil utility and assumes you already have a working knowledge of Qfil and that you have already installed it on your Windows PC. If you don’t have that knowledge start reading. The internet is full of Qfil guides.
You can’t damage or fix your existing imei relevant partitions from this restore because they aren’t included in this download.
You are responsible for backing up your existing phone partitions. I’m not liable for you using my work product and you do so at your own risk. If you’re unsure of what you’re doing then read more about Qfil and what is does. Again, if you are a newby go slow. Taking your time will save you a lot of aggravation.
This process will not fix your erased or damage imei number problem. There are process out there but they are usually reserved for people with an expert level of knowledge on the subject.
This guide is for anyone who’s presently unable to boot or who just can’t access AT&T ota services and wishes to upgrade their lmv600am to a newer a11 build. I have only tried this when my phone was already on an Android 11 rom. That’s not to say it won’t work coming from a Android 10 rom but I haven’t tried it.
This process will not fix your erased or damage imei number problem.
Steps
Download “Lmv600am v20q Restore Partitions.7z” file from ??? and unzip. Remember the unzipped restore directory path.
Plug your phone into PC with USB cable and put you phone in EDL (9008) mode. Again, there are guides on how to do this everywhere.
Start Qfil and select the port of your phone’ connection. (See Windows device manager)
Select the v60 firehose (.elf) which is included in the unzipped directory.
Select storage type = ulf which is located at the bottom right of the Qfil dialog screen. I’m using Qfil 2.0.3.5 version.
Next click on the “load XML” button and group select “rawprogram0” thru “rawprogram6” which are also in the unzipped directory, then hit OK. Next it will ask for the Patch0.xml file, hit cancel as we’re not patching anything.
Wait a few seconds and then click on the “Download” button. Qfil will now resolve all the names of the partitions to be restore and then start the download process to the phone.​
When complete phone reboots as I recall.

try first time, stuck at 88%, show a error
try second time, stuck at 55% for a whole night, no error
after, stuck at a random percent every time, no error
att a11 already crossflashed to EA

Why super.bin so big? 20GB stucking at flashing super every time

peterwode said:
try first time, stuck at 88%, show a error
try second time, stuck at 55% for a whole night, no error
after, stuck at a random percent every time, no error
att a11 already crossflashed to EA
Click to expand...
Click to collapse
My guess is your pc went to sleep. Other suggestions; change usb port... change cable... change PC. This procedure has been used by myself and others multiple times without failure. Qfil does nothing more than a simple read partition / write partition. There's no magic.

peterwode said:
Why super.bin so big? 20GB stucking at flashing super every time
Click to expand...
Click to collapse
The size of the super.bin (partitions system_a and system_b) is what it is. It's not like you have a choice. Hopefully, you do realize you're restoring both sides of the phone, slot a/slot b.

hooutoo said:
My guess is your pc went to sleep. Other suggestions; change usb port... change cable... change PC. This procedure has been used by myself and others multiple times without failure. Qfil does nothing more than a simple read partition / write partition. There's no magic.
Click to expand...
Click to collapse
Everything is changed, but the problem is the same, just stucked, progress no move forward, no error message , is the configuaration setting's problem? I am using the same configuaration with the crossflash guide

Finally figured out where the problem is , after upate qpst to the latest one, everything just ok now, thanks for your sharing and help

peterwode said:
Finally figured out where the problem is , after upate qpst to the latest one, everything just ok now, thanks for your sharing and help
Click to expand...
Click to collapse
You're welcome.

sorry for my mistake, not update , it is downgrade to 2.0.2.3, with 2.0.3.5 showing zero disk reading of qfil progress in the task manager, with 2.0.2.3 you can see qfil reading data from disk from computer , i don't know if it is bug or just a showing problem.

report one issue, cann't boot when changed to slot_a

did this. boots as cricket wireless and is just doing nothing but booting with the giant smiley face logo.
is there another step I need to do? Im surprised to see cricket and not ATT

chamilun said:
did this. boots as cricket wireless and is just doing nothing but booting with the giant smiley face logo.
is there another step I need to do? Im surprised to see cricket and not ATT
Click to expand...
Click to collapse
If you're seeing any boot logo and then getting stuck it usually means that the phone is trying to get to userdata. This restore does not include userdata for obvious reasons. My guess is you needs to reformat/wipe userdata.
The easiest way is probably by entering restore mode and selecting "reset to factory" which both reformats and wipes userdata.
As for the cricket logo, no telling where that's coming from or where your phone's been. But as per the Op description, these are 100% AT&T a11 v20q partitions.

phone wont get into the android boot screen for wiping cache/userdata/etc. kinda odd...
something tells me I need to write something additional. because my ATT model was crossflashed to the EU firmware
to bypass the fingerprint bug. however, they are shutting off 3G networks on the 22nd so cant keep using.
anyone else have any idea what I need to do?

Dude.... you don't need to be at boot screen whatever that is. You need to put your phone in recovery mode. Hold -vol and pwr until phone start to boot..... then release. Immediately press/hold +vol to put phone in recovery mode. Then select fastory reset which will rebuild (reformat/wipe) userdata . There are lots of guides on how to put a v60 into recovery mode.
If you can't get into recovery then put phone into edl mode (9008), start gfil and load the eng abl img to both abl_a and abl_b. Then restart phone and put it into fastboot mode, again guides all over internet on how to get to fastboot mode. From there try "fastboot -w" command from cmd prompt using adb/fastboot tools. If that doesn't work it has to be done from recovery mode.
Be sure you have all the proper drivers. For example when going into fastboot mode you will mostly likey have to manually load the adb bootloader driver so fastboot commands can access you phone.

hooutoo said:
eng abl img
Click to expand...
Click to collapse
hooutoo said:
Dude.... you don't need to be at boot screen whatever that is. You need to put your phone in recovery mode. Hold -vol and pwr until phone start to boot..... then release. Immediately press/hold +vol to put phone in recovery mode. Then select fastory reset which will rebuild (reformat/wipe) userdata . There are lots of guides on how to put a v60 into recovery mode.
If you can't get into recovery then put phone into edl mode (9008), start gfil and load the eng abl img to both abl_a and abl_b. Then restart phone and put it into fastboot mode, again guides all over internet on how to get to fastboot mode. From there try "fastboot -w" command from cmd prompt using adb/fastboot tools. If that doesn't work it has to be done from recovery mode.
Be sure you have all the proper drivers. For example when going into fastboot mode you will mostly likey have to manually load the adb bootloader driver so fastboot commands can access you phone.
Click to expand...
Click to collapse
all done. loaded eng abl. erased userdata in fastboot. still is on cricket startup screen and just stays there booting forever

does yours say "cricket wireless" when booting? so odd how this thing is behaving

got it finally to boot by resetting phone within recovery. fastboot -w command didnt do it. Now Im getting some type
of NT error that something doesnt match. but phone is working.
thanks!

Did you follow the steps, recovery mode and factory reset? Did it complete?

chamilun said:
got it finally to boot by resetting phone within recovery. fastboot -w command didnt do it. Now Im getting some type
of NT error that something doesnt match. but phone is working.
thanks!
Click to expand...
Click to collapse
Your welcome.
NT codes is a well know error so just google it. Also, maybe check with TG group.

hooutoo said:
Your welcome.
NT codes is a well know error so just google it. Also, maybe check with TG group.
Click to expand...
Click to collapse
everything worked but something is odd. its showing as cricket boot up, LG in settings. not ATT. and the NT error.
also the hidden code menu isnt working.
somehow Ive got a frankenstein phone now. was a pure ATT phone before I crossflashed. somehow I need to figure out
what to write to the phone to get proper version back. I do have the old backup. just need to figure out how we
did the crossflashing and kind of undo