Database Users

[Q] Can't get into recovery, can't get into bootloader download, am I bricked?

I am currently stuck without being able to get into bootloader or recovery. I have a rom that is currently working for about 10 minutes at a time (FLEXREAPER-RF1_rv3-CUSTOM-ICS for HC).
I was orignially on the HC bootloader, using CWM v5. I then used the file found here http://skrilax.droid-developers.org/a500/nvflash/images/a500_a501_bootloaders_apx_ics_v7.zip and installed it from CWM. It looked like it installed just fine.
The problem is that now, when I try to get into recovery, I just see this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Using Afterota, I was able to get my CPUID and the rest
Tablet Serial : 11920475015
Tablet Cpuid : 011920475015
Tablet Sbk : 0x6AA1E101 0x69CCD301 0x991D3003 0x07580203
Bootloader : 0.03.0X-HC
Android Build : FLEXREAPER-RF1_rv3_Acer_AV041_A500_1.031_033_041.00_CUS_WW_GEN1
But when I try to use blackthund3r or Timmydean, my tablet goes into APX just fine (with the screen blank and the power button white), but none of the tools can get my tablet to go into bootloader download mode.
I am totally stuck, and have no idea what to do. I have tried following instructions for http://forum.xda-developers.com/showthread.php?t=1622425 and http://forum.xda-developers.com/showthread.php?t=1516012, but neither of them can get me into bootloader. When I use the TimmyDean tool and put my tablet into APX manually, I get to the screen where I put in the CPUID, but i tells me that the CPUID I am entering is invalid. I've checked using multiple methods, and I always get my CPUID back at 011920475015. Is this a valid CPUID?
I am going crazy here.

I have the same problem,
i cant boot into recovery mode.
and i cant get it to boot into APX mode i just get a black screen.
and can not find any wifi networks wont even search.
Would love some help.

MrR0ng said:
I am currently stuck without being able to get into bootloader or recovery. I have a rom that is currently working for about 10 minutes at a time (FLEXREAPER-RF1_rv3-CUSTOM-ICS for HC).
I was orignially on the HC bootloader, using CWM v5. I then used the file found here http://skrilax.droid-developers.org/a500/nvflash/images/a500_a501_bootloaders_apx_ics_v7.zip and installed it from CWM. It looked like it installed just fine.
The problem is that now, when I try to get into recovery, I just see this screen
Using Afterota, I was able to get my CPUID and the rest
Tablet Serial : 11920475015
Tablet Cpuid : 011920475015
Tablet Sbk : 0x6AA1E101 0x69CCD301 0x991D3003 0x07580203
Bootloader : 0.03.0X-HC
Android Build : FLEXREAPER-RF1_rv3_Acer_AV041_A500_1.031_033_041.00_CUS_WW_GEN1
But when I try to use blackthund3r or Timmydean, my tablet goes into APX just fine (with the screen blank and the power button white), but none of the tools can get my tablet to go into bootloader download mode.
I am totally stuck, and have no idea what to do. I have tried following instructions for http://forum.xda-developers.com/showthread.php?t=1622425 and http://forum.xda-developers.com/showthread.php?t=1516012, but neither of them can get me into bootloader. When I use the TimmyDean tool and put my tablet into APX manually, I get to the screen where I put in the CPUID, but i tells me that the CPUID I am entering is invalid. I've checked using multiple methods, and I always get my CPUID back at 011920475015. Is this a valid CPUID?
I am going crazy here.
Click to expand...
Click to collapse
Well, first off, your UID is fine. For ICS that is. TimmyDeans tool requires an HC UID. So you can't use it in TimmyDeans. Theoretically the SBK is the same for both in a lot of cases, just the UID number changes. But you have your UID so all is not lost.
Probably just the recovery image got toasted. Also, there are reports that a small percentage of tablets don't get along well with certain version recoveries. No know reason for this.
Can you boot into fastboot mode? (vol+ amd PWR) if so, you can try to fastboot a new recovery image through the android SDK. You can access fastboot through the Android SDK/Platform-tools folder on your PC (open a command window there. Put the tab in fastboot mode, plug in to PC, make sure windows recognizes it as fastboot device.
fastboot flash recovery recovery.img
(recovery.img being the name of the recovery you wish to use)
or
You can try the manual method of NVFlash. Personally I use one of the older tools from BlackThund3r to do this. It's not listed anymore, so if you need it, I'll have to package it in a zip file and post it.
Anyhow, those are a couple of methods to use.
MD

Hi
i need more info on how to fastboot through the Android SDK/Platform-tools.
i have downloaded the android sdk but look like just a package DOWNLOADER developer.android.com/sdk/index.html
cant use the other methods ( NVFlash BlackThund3r) it just hang on the black screen

First off, you have to download and install the Android SDK. When finished, it should install (under Win7) C:\program files (x86)\android\android-sdk
When you install it. make sure you right mouse click and "install as administrator". A good practice to get into when installing things.
Everything you need to know about installing the SDK (including platform tools) can be found here;
http://developer.android.com/sdk/index.html
In there is a folder \Platform-tools. This is where you find Adb And Fastboot. If you hold SHIFT + Right mouse click, you can open a command window there. (win7)
But this is all dependent on whether you installed the correct drivers. Some say Acer Drivers will work. Personally I prefer to use the Google USB Drivers for Android. (google USB Drivers Android).
How do you know your drivers work? Easy, put your tab in APX mode, display will be black but you see the PWR button lit.
Check Windows Device manager with the tablet plugged in. Should list an APX device or Recovery Device. If it doesn't, you need to install the drivers manually by selecting the folder where you extracted the google drivers to. Ignore any incompatibility message.
Whether APX Mode, or Fastboot, Windows should load the specific drivers. If Device Manager doesn't reflect this, then you need to sort it out.
If you want to reflash something using Fastboot, like a boot.img or recovery.img, place the .img file in the same directory as the fastboot command. In most cases with the newer version SDK, it will be in Platform-tools.
The more common fastboot commands can be found in this thread, which I posted the command for recovery.img earlier.
http://forum.xda-developers.com/showthread.php?t=1619913

When i open fastboot.exe the window opens for 1 second and then closes again. am i missing something else.
i am starting to think i may have bricked my tab.

xgutterratx said:
When i open fastboot.exe the window opens for 1 second and then closes again. am i missing something else.
i am starting to think i may have bricked my tab.
Click to expand...
Click to collapse
Dude, you can't "double click" fastboot.exe. Don't work that way.
As I posted earlier, open a CMD window in the platform-tools folder on your PC.
Then put your tab in fastboot mode (vol+ and PWR) till your tab says "fastboot mode". Then plug it in, and check Windows loads the fastboot drivers. (you should see it loading drivers in the windows taskbar).
After that, then you can run the fastboot command to install a recovery image. "IN THE CMD WINDOW"
If you don't feel comfortable doing this, then don't. We can find some other method that may be more comfortable for you.
I can zip up the app that I use, and maybe you should try that first. It uses NVFlash. As I really don't want you to bork things up anymore than they are now. Especially if you're not comfortable with fastboot (you can really bork things up with this).
Give me a little bit, and I'll post something for you guys to try.

Now, this is the tool I generally use. It requires the tab be in APX mode.
http://www.4shared.com/zip/ycbdG0qY/Ver4_BL_and_CWM.html
Extract the zip to your PC. It contains ver4 unlocked bootloader and CWM. I know this combo works.
Put your tab in APX mode. Connect to PC and verify windows loads the correct APX drivers. Then unplug the tab.
Start the app by "right mouse clicking A500APXFLASH.exe, and select "run as administrator".
Plug your APX Mode Tab into the USB when the app tells you. ( i think you have to do this first, or the app will do it for you. Can't remember, an don't feel like flashing another bootloader to find out)
Get your SBK number (usually I have this in notepad so I can copy and paste it).
Usually I select Manual as I only want to select the Ver4 unlocked.bin and the Thor Recovery and none of the other stuff.
Then I select Automatic when prompted. And follow the prompts when asked.
NOTE: After plugging in your APX mode tab, you may still see a message at the bottom of the app stating "No APX Devices Detected" Ignore this and click Next.
This was a small bug.
Also, sometimes on Win7 you may get a windows error box. Ignore this also and close it.
DO NOT UNPLUG the tab until the apps says complete. The whole process takes about 5 minutes or so to complete.
Then it's safe to unplug the tab. Shut it down, and reboot to recovery to make sure it works.
Also something I want to mention. If you guys installed OTA's, make sure you delete the "boot to recovery.p" in your tabs System file as states in Civato's thread. Otherwise, when you boot normally, it will delete your Custom Recovery, and you'll be doing this again.
MD

Hi MD,
thx for trying to help out here, much appreciated.
I've just tried your steps, the apx flash utility stays put at "stage two - uploading image..." and the nvflash cmd prompt stays at "[resume mode]". Waited for 10 minutes...nothing.
Is there anything else to try ?
ta,
T

Tommmii said:
Hi MD,
thx for trying to help out here, much appreciated.
I've just tried your steps, the apx flash utility stays put at "stage two - uploading image..." and the nvflash cmd prompt stays at "[resume mode]". Waited for 10 minutes...nothing.
Is there anything else to try ?
ta,
T
Click to expand...
Click to collapse
Well, there's always some tricks to try.
Did you use the Google drivers and verify you tab is registered in Windows Device Manage as APX device or Recovery Device?
To manually go to APX, shut down tab. Put a paper clip in the reset button, and hold. With your other hand, press and hold PWR for 3 seconds, release PWR, then about 1 second later remove paper clip. You should have black display with pwr lite on. Plug in tab and check device manager.

apx flashutil claims "Acer APX Mode device detected"
device mgr shows "Acer USB Boot-recovery driver" under "Universal Serial Bus controllers"

Tommmii said:
apx flashutil claims "Acer APX Mode device detected"
device mgr shows "Acer USB Boot-recovery driver" under "Universal Serial Bus controllers"
Click to expand...
Click to collapse
OK, that's good (I had to double check with mine)
Now, did you run the package I posted earlier? Reason is, it uses a .bin file instead of an apx package.
Also, as I am dealing with several other folks, do you have a bootloader when you boot? Like Skirlax_CZ blah blah blah version xxxx?

I tried the bootloader_ics_v4.bin and the recovery you supplied.
There's no mention of a bootloader on the A501
Supposition : if my cpuid were wrong, would apxflash throw an error?

Tommmii said:
I tried the bootloader_ics_v4.bin and the recovery you supplied.
There's no mention of a bootloader on the A501
Supposition : if my cpuid were wrong, would apxflash throw an error?
Click to expand...
Click to collapse
@Tommmii, Which tablet do you have? a 500 0r 501?
Generally, if the UID/Sbk were wrong, the apps would throw an error.

A501
I'm beginning to suspect my UID (037c700140c0941) could be wrong.
If so, i'll be stuck up a creek without a paddle

Tommmii said:
A501
I'm beginning to suspect my UID (037c700140c0941) could be wrong.
If so, i'll be stuck up a creek without a paddle
Click to expand...
Click to collapse
Looks like an HC UID. But it doesn't matter. If this was the UID you pulled under HC. Basically, ICS will change the UID. As a matter of fact, it may change it several times when you install ISC Roms. What shouldn't change, in most cases, is the SBK. Usually the SBK is the same under HC and ICS. At least with my tab it was.
Naw,,,, you still got a paddle.
I got a 501 also.
So tell me, do you have any bootloader at all when you try to boot normally?
Also, you didn't tell me what happened when you tried running the app I posted with the Ver4 unlocked bootloader. Did it work? (don't worry if it said 500 or 501, can fix that later)
Attached is my 501 ver4.bin Throw it in the same directory as the tool I posted.

Power On gives the white Acer logo, followed by a bootlogo ("android" metallic type letters) From memmory that could be the stock HC bootlogo. Stuck in a loop though...
VolDown & PWR gives the HC Andy with an exclamation triangle dangling above his head.
edit : just tried renaming SD_Acer_A501_1.309.02_COM_GEN1 to update.zip , it updated the rom but no boot same as above
edit2 : didn't see your attachement...just tried it, stuck at [resume mode] in the nvflash debug window

You rock so hard!
The super ridiculous fastboot method worked PERFECT for me. Took me all of 2 minutes. I was pulling my hair out. Thanks so much for the AMAZING support. Love the android community.
Moscow Desire said:
Well, first off, your UID is fine. For ICS that is. TimmyDeans tool requires an HC UID. So you can't use it in TimmyDeans. Theoretically the SBK is the same for both in a lot of cases, just the UID number changes. But you have your UID so all is not lost.
Probably just the recovery image got toasted. Also, there are reports that a small percentage of tablets don't get along well with certain version recoveries. No know reason for this.
Can you boot into fastboot mode? (vol+ amd PWR) if so, you can try to fastboot a new recovery image through the android SDK. You can access fastboot through the Android SDK/Platform-tools folder on your PC (open a command window there. Put the tab in fastboot mode, plug in to PC, make sure windows recognizes it as fastboot device.
fastboot flash recovery recovery.img
(recovery.img being the name of the recovery you wish to use)
or
You can try the manual method of NVFlash. Personally I use one of the older tools from BlackThund3r to do this. It's not listed anymore, so if you need it, I'll have to package it in a zip file and post it.
Anyhow, those are a couple of methods to use.
MD
Click to expand...
Click to collapse

Tommmii said:
Power On gives the white Acer logo, followed by a bootlogo ("android" metallic type letters) From memmory that could be the stock HC bootlogo. Stuck in a loop though...
VolDown & PWR gives the HC Andy with an exclamation triangle dangling above his head.
edit : just tried renaming SD_Acer_A501_1.309.02_COM_GEN1 to update.zip , it updated the rom but no boot same as above
edit2 : didn't see your attachement...just tried it, stuck at [resume mode] in the nvflash debug window
Click to expand...
Click to collapse
Ewwww.... right now, I am at a loss for a plan of attack.
After running the rom, and it updating ok, the Acer with the metallic logo's tells me it's a modified bootloader (I saw this in the earlier unlocked bootloader logos. Ver3 I believe. However, this ver3 I don't believe had flashboot capability.
Ver3 is ok. You can run it. Why we can't get it updated to ver4 right now, is beyond me.
Hmmm.... will have to come up with a different plan.
One thing puzzles me, why when you ran that .... "update", it didn;t put a stock bootloader on it.
Ewwww... too bad you are not near Moscow. I would love to get my hands on it.

could i run nvflash manually when connected in APX mode ?
Perhaps it would show more debug info then...?

Completly black screen. help?

OK,, so I. Came Fro the AOKP rom then flashed. .30 stock from Asus. So I could flash the Hydro 4.0 rom. Everything went fine. Was working perfectly for couple days. Didn't use for one day. Try turn on screen, nothing. Hold power to turn on, nothing. Neither can boot into recovery :/ After I flashed the hydro rom. Haven't messed with anything, don't even think I installed any new apps.
When screen is black, can only see charging light while charging. Anny ideas?!?!
Please and thank you

try if you can get adb running after you switched it on
then type these messages
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
Enter
when finished
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
Try to boot now. If it´s still not running
dl this file:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html Its for the tf300T
unback it
start WSGFlasher
choose 2 for Install menu
choose 1 for full unbrik

Ill try this right when I get home, but I have no idea what could've happened to brick it. The first part you said with adb, what exactly will that do. Just same thing as zip, without using the zip?

So for the life of me I cant get adb to work! Idk what I can or should do. My comp recognized it as an advanced device before. The only sign of life it has is a solid orange light by the power button.(charging or not) I've tried everything. Any help will be so much appreciated. And thanked as many times as I can press it lol

Mine is on its way back from the repair center from similar symptoms. Everything working, but the screen was black. I could see the backlight coming on when I hit the power button. Heard the 'ding' when I plugged in the charger, and could see it on my TV when I purchased an HDMI cable. It started after a quick charge - it was working fine in the morning, I charged it during lunch, and then never could get it back on.

Ya I read ur situation happening alot, like alot on previous TF models, you would think a big company like Asus would recognize all the problems from previous tabs. And find a solution so it doesn't happen with the next model. Everyone keeps rushing out there new tablet when the still have aloe of bugs and defects
When you sent urs in, did you have ur bootloader unlocked?
And my problem is way different than urs. Mine won't turn on at all. Just happened out of no where. I wish I had ur problem. Cause at least I could use it threw HDMI. And still use it. But idk what to do, and don't no if it was my fault or damn hardware to a **** (that Asus sold me)
If anyone has any work around please help (ADB doesn't work anymore, used to not now)

trevor7428 said:
Ya I read ur situation happening alot, like alot on previous TF models, you would think a big company like Asus would recognize all the problems from previous tabs. And find a solution so it doesn't happen with the next model. Everyone keeps rushing out there new tablet when the still have aloe of bugs and defects
When you sent urs in, did you have ur bootloader unlocked?
And my problem is way different than urs. Mine won't turn on at all. Just happened out of no where. I wish I had ur problem. Cause at least I could use it threw HDMI. And still use it. But idk what to do, and don't no if it was my fault or damn hardware to a **** (that Asus sold me)
If anyone has any work around please help (ADB doesn't work anymore, used to not now)
Click to expand...
Click to collapse
Does windows device manager sees any kind of a transformer device?
If yes try to install the drivers by hand.
right klick on the device
choose update driver software
choose search manually on computer
next window choose from a list on computer (the one at the buttom of the window)
Then you will get a 2sided window
right side you have the company names
left side you have the model type
if you have something like asus ther on the right side choose it
then on the left side choose Asus android ADB device (!!!! not the one with Composite)
then klick on next
if a window pops up saying something like its not recommended just hit yes and install it anyway.
Translatet it from German, so I hope the translation is correct. Just follow the steps and you will know what I mean.
or, if you are only able to get Fastboot running you need the blob file out of the Asus update (it has to be placed in the folder were the fastboot.exe is) update and this fastboot command:
fastboot -i 0x0B05 flash system blob
I had to run the fastboot command more than 20 times, but finally it run through and i was back to stock.
for fastboot dl this package
http://www.4shared.com/zip/npKPgYok/WSG_UnBricker_Skript_no_Fw.html
extract the folder to c: and rename the folder to trecovery
open cmd
type cd c:\trecovery\
now you are in the folder with fastboot.exe
Than type the fastboot command

mikaole said:
Does windows device manager sees any kind of a transformer device?
If yes try to install the drivers by hand.
right klick on the device
choose update driver software
choose search manually on computer
next window choose from a list on computer (the one at the buttom of the window)
Then you will get a 2sided window
right side you have the company names
left side you have the model type
if you have something like asus ther on the right side choose it
then on the left side choose Asus android ADB device (!!!! not the one with Composite)
then klick on next
if a window pops up saying something like its not recommended just hit yes and install it anyway.
Translatet it from German, so I hope the translation is correct. Just follow the steps and you will know what I mean.
or, if you are only able to get Fastboot running you need the blob file out of the Asus update (it has to be placed in the folder were the fastboot.exe is) update and this fastboot command:
fastboot -i 0x0B05 flash system blob
I had to run the fastboot command more than 20 times, but finally it run through and i was back to stock.
for fastboot dl this package
http://www.4shared.com/zip/npKPgYok/WSG_UnBricker_Skript_no_Fw.html
extract the folder to c: and rename the folder to trecovery
open cmd
type cd c:\trecovery\
now you are in the folder with fastboot.exe
Than type the fastboot command
Click to expand...
Click to collapse
I understood perfectly. But device manager does not pick up my tf300 anymore. It used to say Asus transformer but not after black screen. And I've had to use fastboot in the past with C:/recovery. But adb won't recognize so I don't no if i have any options left. If so don't no what my options are.
I thanked you anyways for trying to help I appreciate that.

trevor7428 said:
I understood perfectly. But device manager does not pick up my tf300 anymore. It used to say Asus transformer but not after black screen. And I've had to use fastboot in the past with C:/recovery. But adb won't recognize so I don't no if i have any options left. If so don't no what my options are.
I thanked you anyways for trying to help I appreciate that.
Click to expand...
Click to collapse
If you are not able to get fastboot or adb running I think you are stucked. Only way I know of to unbrick without them is APX with NVflash, but this is not running on TF300 till now. But I heard someone is working on it, cause it is already out for the prime. So maybe in the near future we will get it for the TF300.

mikaole said:
If you are not able to get fastboot or adb running I think you are stucked. Only way I know of to unbrick without them is APX with NVflash, but this is not running on TF300 till now. But I heard someone is working on it, cause it is already out for the prime. So maybe in the near future we will get it for the TF300.
Click to expand...
Click to collapse
Well that sucks. But I really don't no if its bricked or a hardware problem. Cause everything was fine beforehand. I flashed stock then hydro rom. And was working good for couple days with reboots. Then I went to turn it on but it wouldn't. I didn't even instal a new app after flashing hydro. (Not saying its hydro rom fault. Just last thing I did before black screen)
Could a brick happen for no reason? If its hardware I wonder if its something someone could fix. That's not Asus or costing same as new tablet.

Need Help! Tablet Stuck and Fastboot Not Working

I am sitting dead in the water with an EVGA Tegra Note 7 that can't turn on Wireless and won't let me install drivers to move further or even do a restore.
First off I am using Tomsgt Super Tool: http://forum.xda-developers.com/showthread.php?t=2627654
So my device was continuing to fail an OTA update so I was going to use this device to reinstall the basic 4.4.2. However during the process Fastboot.exe gave a failed message in Windows, but it showed fastboot after the device name. I continued to let it Restore Tegra Note 7 to Android 4.4.2 and first of all it did it way too fast and once it was finished I couldn't get the Wireless to enable. I read another person with the same problem that had to redo the process. Well I can't get past reinstalling ADB and Fastboot, now not even ADB..
I tried uninstalling the device from Windows letting it reinstall and then checking it again. No matter what I do the USB Driver Scan fails over and over. I got this issue the first time, but somehow I got it to catch the device once and install ADB.
1) Yes USB Debugging in Enabled
2) Yes Anti-Virus is Off
3) Bootloader unlocked
4) Tried Different USB Ports
So what the hell is going on here?? All I wanted to do was run a damn OTA update.. Now I have a tablet with no wireless and I obviously can't do an OTA update now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was thinking about not using the tool and doing it all manually like I used to do, but all the tool does is auto execute files/folders in specific orders, basically an elaborate .bat file. So if it is failing at ADB, it is going to fail for me manually too.
Please give me some idea of what to do. I don't see how relocking the bootloader would do anything, but aside from that it was a non-rooted stock 4.4.2 OS running.
Is there something I need to do in order to get Impactor to work?
So then I plug the device into a 9 year old laptop with Windows XP and Impactor sees the device on the first try and installs the driver (it takes 2-3 minutes). Then it finishes and I close impactor, but I get an error next saying device not found. I restart the machine and now it is exactly like my desktop, Impactor can't see the device at all.
What in the hell is going on here? If I had known all this was going to happen I would have skipped their damn OTA update that continued to fail.
BTW with XP I can prevent Windows from installing any type of driver, so I did. Should I let XP search for a driver and see what happens?
Someone throw me some ideas, you can see a full explanation of what is happening if you scroll up to my screenshot. I basically have a dead device because I wanted to use this tool to do a recovery...
Wireless refuses to turn on, it just sits there for hours if I let it.
Someone please give me guidance, I was out of the Android scene for a while and I've forgotten a lot of the tricks I used to know.

If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.

share_needles said:
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
Click to expand...
Click to collapse
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again. I believe there is a quick message that flashes the first time I try to select Fastboot, however it's way too fast to read. When I do it again after that is when I will see a black flash, but apparently from what I have heard that is all Fastboot kernel is supposed to do??
How do I verify Fastboot is working before I flash the damn thing?

NCSUZoSo said:
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again.
How do I verify Fastboot is working before I flash the damn thing?
Click to expand...
Click to collapse
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.

share_needles said:
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
Click to expand...
Click to collapse
Can I get some official links for the newest/compatible versions of TWRP and the latest stock ROM I can install that is the most up to date (with Google Apps)?
Sorry to ask, but I am short on time most of the time and I might have an hour or so to work on it tomorrow.

Sorry I don't have official links but it would take you 10mins to find them through google. Good luck.

I have two files which I believe are correct except the TWRP file has an odd extension..
"Shaky156-TWRP-recovery.img.exe"
the other that is supposed to have GApps is: Stock-4.4.2-2.5-TegraNote7.zip
If that zip is only like 440 MB is that even possible? Can someone point me in a better direction if this sounds wrong.
Sources, TWRP: http://forum.xda-developers.com/showthread.php?t=2586432
Actually thinking about it and I bet with having things specific to img files like IMGBurn and other software it may create a .exe so it's easier to emulate it as a disk.
Do we have any good custom ROMs these days you'd suggest over stock? Are any that stable yet? If not can anyone find me a complete download if a 440MB zip is too small to have GApps in it.

I used Fastboot commands to get TWRP installed and Android is "upgrading.." now, so hopefully this will fix it.
I have the tablet up and running going into Google Play now.
I used this thread's link for the latest TWRP (2.7.1.0): http://forum.xda-developers.com/showthread.php?t=2586432
I got a completely stock version of 4.4.2 and OTA shows this as the most up to date version. I got my copy of the 4.4.2 ROM out of the Super Tool's folder that you can find here: http://forum.xda-developers.com/showthread.php?t=2627654
The tricky part to this my first time was I forgot you can open a command window inside the folder that contains TWRP/Fastboot/etc. (hold Shift and Right Click in the folder where all the data is and hit open command window)
Obviously everything came off a SD Card installed into the TN7.

answer for dummies
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks

aimeymarie said:
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
Click to expand...
Click to collapse
Your best bet is to find someone you know who the above is not a foreign language to. I mean it could be broken down step by step as basic as possible and you may still not understand parts.

[HOWTO] Unbrick Hardbricked (stuck onUSB Logo) MeMo Pad ME170CX (and others)

This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool

Hey @korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated

Premie said:
Hey korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated
Click to expand...
Click to collapse
I literally faught that error for a whole day. I tried 5 different computers, all had that issue. Usually my tablet would connect and disconnect once before the logo came up. Within that brief window, I was able to start the flash and it worked. I'm pretty sure that's what did it. If you aren't seeing this, turn up your PC's volume and listen for the USB sounds.
This whole thing is pretty annoying, but when it works, it works.

Thanks
I shall keep going at it until it works or I find another solution.

PLEASE help me!
korockinout13 said:
This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool
Click to expand...
Click to collapse
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?

Nandr0idC0nsumer said:
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?
Click to expand...
Click to collapse
If you have a working boot loader, you don't need to do this.

korockinout13 said:
If you have a working boot loader, you don't need to do this.
Click to expand...
Click to collapse
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore

Nandr0idC0nsumer said:
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore
Click to expand...
Click to collapse
What happens instead of fastboot mode?

korockinout13 said:
What happens instead of fastboot mode?
Click to expand...
Click to collapse
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."

Nandr0idC0nsumer said:
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."
Click to expand...
Click to collapse
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.

korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well

Nandr0idC0nsumer said:
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well
Click to expand...
Click to collapse
You have adb? That's not possible unless you are getting past the boot loader.

korockinout13 said:
You have adb? That's not possible unless you are getting past the boot loader.
Click to expand...
Click to collapse
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload

Nandr0idC0nsumer said:
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload
Click to expand...
Click to collapse
Hm... seems like you should be able to work with that if you have something flashable.

korockinout13 said:
Hm... seems like you should be able to work with that if you have something flashable.
Click to expand...
Click to collapse
Returned the tablet at Best Buy to get "fixed" (come on bestbuy, I know you mean replaced.) Thanks for your help

Repair
Hi,
I think i can help you out because i worked with the intel tool for weeks now to find a solution to root the me581cl.
Go to my thread and download a newer version of intelPhone tool.
http://forum.xda-developers.com/general/help/root-downgrade-asus-me581cl-t3075678
If you crashed your tab totaly, you must put the 4 OS IFWI,dnx files like in the first post and then also boot.img, fastboot.img, recovery.img.
Uncheck only the ifwi folder, but select it before. So its possible to check blank phone and on demand flash.
Then click start flash and the files get loadet up. Now push vol+ and vol- togehter and plug in the device.
(device must be off before you plug it in. If not, press 10 sec the power button.)
The reest you can read in my thread. A downgrade from Android 5 to 4.4 is also possible.
Good luck

Guys, my ME176CX is shafted after completing the L update, it boots to the android with the red exclamation box...i can get past this by using the volume + & power and arrive in the recovery. from there I have tried the wipe cache/wipe userdata (doesn't help) also i tried to adb sideload one of the roms in the collection of roms thread. no good. ideas??

Any solution?
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
Man I'm living in Venezuela a bad country to get damaged any gadget everything is 5 times expensive who your country and without any help in our soil by ASUS.

is this solution applicable to non-intel memopad? (e.g. me172V)

playinghier said:
is this solution applicable to non-intel memopad? (e.g. me172V)
Click to expand...
Click to collapse
No, this is very specific to the Intel chipset.

Fastboot mode not detected by PC

So my G2 D800 is currently stuck on Fastboot mode but whenever I run the command "Fastboot devices" it only shows the device as "?", which I thought meant that it had issues recognizing it because of corrupted drivers.
After doing some searching, I decided to download Google USB drivers and LG device drivers, but sadly the computer installs the device as "ADB Google Interface" or "Fastboot Google Interface" and not as an LG device, and this makes the device to show as "?" when the "Fastboot devices" command is run.
I also tried the "ADB devices" command and it came back with a empty line where the G2 should appear.
Just for the record, the G2 cannot enter into Download mode nor Recovery Mode.
Is there a way of making my device show up properly?

potemkinbuster said:
So my G2 D800 is currently stuck on Fastboot mode but whenever I run the command "Fastboot devices" it only shows the device as "?", which I thought meant that it had issues recognizing it because of corrupted drivers.
After doing some searching, I decided to download Google USB drivers and LG device drivers, but sadly the computer installs the device as "ADB Google Interface" or "Fastboot Google Interface" and not as an LG device, and this makes the device to show as "?" when the "Fastboot devices" command is run.
I also tried the "ADB devices" command and it came back with a empty line where the G2 should appear.
Just for the record, the G2 cannot enter into Download mode nor Recovery Mode.
Is there a way of making my device show up properly?
Click to expand...
Click to collapse
ADB devices doesn' t work as it' s in fastboot mode. The ? doesn' t matter fastboot should work.
There are also plenty of guides here in general how you can fix your problem. you need to use the fastboot flash command to flash the proper files to get everything working again. I suggest to erase download mode partition first and get your phone booting/working recovery again. Cause if you did something wrong you could always still enter Fastboot mode by entering download mode because the download mode will be missing so it will go to fastboot.
So fastboot is detected else there wouldn' t be a ?

the only solution for your case is to use testpoint solution to get the download mode (fastboot dont work) i have the same problem before.

wulsic said:
ADB devices doesn' t work as it' s in fastboot mode. The ? doesn' t matter fastboot should work.
There are also plenty of guides here in general how you can fix your problem. you need to use the fastboot flash command to flash the proper files to get everything working again. I suggest to erase download mode partition first and get your phone booting/working recovery again. Cause if you did something wrong you could always still enter Fastboot mode by entering download mode because the download mode will be missing so it will go to fastboot.
So fastboot is detected else there wouldn' t be a ?
Click to expand...
Click to collapse
I've tried this, but it takes forever and when it comes back with a response it only says (ERROR TOO MANY LINKS), which makes the use of fastboot commands useless
albatron34 said:
the only solution for your case is to use testpoint solution to get the download mode (fastboot dont work) i have the same problem before.
Click to expand...
Click to collapse
I wishi I could make it get into download mode xP

Ok, I will keep updating this and hopefully if I find the solution, I might be able to help others with the same case as me.
So far I've tried:
*Flashing all *.img files of my model (D800).
-If you are able to finally enter Download mode, but when you try to flash the ROM you can't because of a wrong model, please check here for a solution.
*Since the method above did not work for me, I had to "destroy" download mode to get back into Fastboot mode so I could Flash TWRP recovery image file.
This has caused my phone to stop being recognized by the PC, which means that when the fastboot commands are run, I cannot get it to work as the computer doesn't know the exact location of the phone (USB, Vendor ID, Details about phone).
To try to make it appear again, I redownloaded the drivers, fastboot files and even went as far as installing manually the drivers through Linux, but none of this seem to work.
As of now, the phone cannot be recognized, but I won't give up until I find a solution!!!

potemkinbuster said:
Ok, I will keep updating this and hopefully if I find the solution, I might be able to help others with the same case as me.
So far I've tried:
*Flashing all *.img files of my model (D800).
-If you are able to finally enter Download mode, but when you try to flash the ROM you can't because of a wrong model, please check here for a solution.
*Since the method above did not work for me, I had to "destroy" download mode to get back into Fastboot mode so I could Flash TWRP recovery image file.
This has caused my phone to stop being recognized by the PC, which means that when the fastboot commands are run, I cannot get it to work as the computer doesn't know the exact location of the phone (USB, Vendor ID, Details about phone).
To try to make it appear again, I redownloaded the drivers, fastboot files and even went as far as installing manually the drivers through Linux, but none of this seem to work.
As of now, the phone cannot be recognized, but I won't give up until I find a solution!!!
Click to expand...
Click to collapse
Did you also tried linux to run the fastboot command as root? Or did you saw the device in device manager in windows?
If all the things don't work then you might need to do the hard brick fix method.
It also may sounds odd but check oe the device is maybe recognized in adb

I ve had same problem as op does. What I did is next:
1. Opened phone and shortened those two capacitors to force phone in QHUSB_BULK mode. (there is tutorial on XDA how to do it)
2. After I connected it to PC it showed many partitions (as it supposed to do)
3. Followed this video https://www.youtube.com/watch?v=_d5b_osUTug
4. Flashed .kdz of choice using flashtool
Im in u hurry now but ask if you need anything else and Ill anwer you when I get home.

wulsic said:
Did you also tried linux to run the fastboot command as root? Or did you saw the device in device manager in windows?
If all the things don't work then you might need to do the hard brick fix method.
It also may sounds odd but check oe the device is maybe recognized in adb
Click to expand...
Click to collapse
I tried with Linux and it wasn't identified.
When I used the "lsusb" command I would get back a google device connected as the vendor ID.
ADB doesn't recognize it either

Godra said:
I ve had same problem as op does. What I did is next:
1. Opened phone and shortened those two capacitors to force phone in QHUSB_BULK mode. (there is tutorial on XDA how to do it)
2. After I connected it to PC it showed many partitions (as it supposed to do)
3. Followed this video https://www.youtube.com/watch?v=_d5b_osUTug
4. Flashed .kdz of choice using flashtool
Im in u hurry now but ask if you need anything else and Ill anwer you when I get home.
Click to expand...
Click to collapse
I'd try this, but I don't have a guide good enough to show me which capacitor I should deal with...

potemkinbuster said:
I tried with Linux and it wasn't identified.
When I used the "lsusb" command I would get back a google device connected as the vendor ID.
ADB doesn't recognize it either
Click to expand...
Click to collapse
so it partly like works, perhaps you can still get it to work but else you must do the hardbrick fix method from general. I can't say much other things how you could fix it if fastboot mode doesn't work recovery not then you must use that.

potemkinbuster said:
I'd try this, but I don't have a guide good enough to show me which capacitor I should deal with...
Click to expand...
Click to collapse
Yeah, its a bit tricky when doing it first time but its not that hard. I used this tutorial to open phone and short those capacitors. You just have to remove almost all conectors (but camera one) and remove everything to get to SoC.

I did try to shorten capacitors and removes all connectors but i suppose to shorten them when i put back connectors exept the battery , the probleme whene i reattach them i can no longer see the capacitors @@

There is that small metal piece that is glued to one of those conectors I have removed to be able to access capacitors.

Godra said:
There is that small metal piece that is glued to one of those conectors I have removed to be able to access capacitors.
Click to expand...
Click to collapse
that small metal piece is the volume boutton , and it seemd that they are not removable

No, there is one bellow it but it might be different in your phone. What version of G2 do you have?

Godra said:
No, there is one bellow it but it might be different in your phone. What version of G2 do you have?
Click to expand...
Click to collapse
I have a g2 d802 32g , and I faild trying to shorten the capacities , there is no clear tut to do it
note : in fastboot devices , my lg is recognized as an "?"

kakashi_senpai said:
I have a g2 d802 32g , and I faild trying to shorten the capacities , there is no clear tut to do it
note : in fastboot devices , my lg is recognized as an "?"
Click to expand...
Click to collapse
So exactly same device as mine. And mine device was recognized as "?" as well. I have tried all drivers and yet it didnt work.
Is your phone still opened?
There is one small hole on each side of back of device from which you can see LCD. When you successfuly shorten capacitors youll see purple-like color which means display got power although if you flip your phone your screen will look like its not on. After that you connect battery conector and unplug USB and your device should (well, mine at least did) be in bulk mode.

Godra said:
So exactly same device as mine. And mine device was recognized as "?" as well. I have tried all drivers and yet it didnt work.
Is your phone still opened?
There is one small hole on each side of back of device from which you can see LCD. When you successfuly shorten capacitors youll see purple-like color which means display got power although if you flip your phone your screen will look like its not on. After that you connect battery conector and unplug USB and your device should (well, mine at least did) be in bulk mode.
Click to expand...
Click to collapse
this is a pic from my phone can u please show where to put the wire please
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kakashi_senpai said:
this is a pic from my phone can u please show where to put the wire please
Click to expand...
Click to collapse
Well first you need to remove the buttons plate as it's located underneath that. See the images if you don't know what I mean:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
The only video perhaps available I searched through the thread was this:
https://www.youtube.com/watch?v=15krGmydqgQ&feature=youtu.be
It isn't very clear with the unbricking situation but I unbricked my phone using the images too, Just try to read and see the images and you should be able to unbrick it only you need a thin wire kinda not too large. I couldn't find a smaller wire so it took me like 15 minutes to get it unbricked as I also had some fail attempts.

Yes sir thats my probleme , I tryd to remove the buttons plates but they are stuck with both side , in the video u gave , they are separated
---------- Post added at 10:59 PM ---------- Previous post was at 10:04 PM ----------
well i succeeded to remove button plate , and my device was read as bulk mode. and now i reattached battery and unplug usb connector, now i put back buttons ? and plug it again or what i do exactly ?