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 ?
Related
Hi, need help with my tf300t, i was on latest cyanogenmod and twrp, after install rom manager i install cwm recovery for have autupdate and installation with cm10, after reboot to recovery it take me at twrp recovery, i reboot system and reboot again in recovery and now i'm stuck at asus logo, what can i do?
Tablet won't open the selection menu for usb recovery etc.
(If i must send it at asus support, unlock bootloader only invalidate the warranty asus or even that of the store where i buy it?)
(someone knows tell me about how much will it cost me?)
anthraxx90 said:
Hi, need help with my tf300t, i was on latest cyanogenmod and twrp, after install rom manager i install cwm recovery for have autupdate and installation with cm10, after reboot to recovery it take me at twrp recovery, i reboot system and reboot again in recovery and now i'm stuck at asus logo, what can i do?
Tablet won't open the selection menu for usb recovery etc.
(If i must send it at asus support, unlock bootloader only invalidate the warranty asus or even that of the store where i buy it?)
(someone knows tell me about how much will it cost me?)
Click to expand...
Click to collapse
Do I understand you used rom manager to install cwm? If so you just flashed TF201 recovery ( cwm ) onto a TF300 unit.
Use this link as it was made just for this situation.
http://forum.xda-developers.com/showthread.php?t=1680570&highlight=rom+manager
tobdaryl said:
Do I understand you used rom manager to install cwm? If so you just flashed TF201 recovery ( cwm ) onto a TF300 unit.
Use this link as it was made just for this situation.
http://forum.xda-developers.com/showthread.php?t=1680570&highlight=rom+manager
Click to expand...
Click to collapse
can't access to recovery
anthraxx90 said:
can't access to recovery
Click to expand...
Click to collapse
I'll have to think a little about this problem. No recovery, no boot, no bootloader menu, correct?
While stuck on Asus logo try fastboot devices and adb devices, report.
tobdaryl said:
I'll have to think a little about this problem. No recovery, no boot, no bootloader menu, correct?
While stuck on Asus logo try fastboot devices and adb devices, report.
Click to expand...
Click to collapse
can't access to flash menu just asus logo and unlock bootloader on the top left of the screen.
anthraxx90 said:
can't access to flash menu just asus logo and unlock bootloader on the top left of the screen.
Click to expand...
Click to collapse
Humor me!
Example:
I can run "adb logcat" and get logs long before unit completely boots or leaves the screen you are stuck on. Force power off by holding power till screen goes black power on, give one of the commands I gave above,. Do the same and try the other command. Report. You are pretty well trapped and we are looking for any way to process one command by adb or fastboot.
If neither of the above works we have a couple more option. but they will be handled much the same.
In looking at our posts I don't believe we are communicating very well.
Maybe someone else can come in and help you better.
Anyone?
tobdaryl said:
Humor me!
Example:
I can run "adb logcat" and get logs long before unit completely boots or leaves the screen you are stuck on. Force power off by holding power till screen goes black power on, give one of the commands I gave above,. Do the same and try the other command. Report. You are pretty well trapped and we are looking for any way to process one command by adb or fastboot.
If neither of the above works we have a couple more option. but they will be handled much the same.
In looking at our posts I don't believe we are communicating very well.
Maybe someone else can come in and help you better.
Anyone?
Click to expand...
Click to collapse
2 days ago i send my tf300 to asus but they called me this morning and ask for 150€ for repair (they told me: the flash memory must be change), i haven't this money, i take tablet to home this afternoon, there is a way to solve the problem by me without asus support? need help :crying:
Edit:I went to the center asus, and I taked my asus tablet, they told me that asus did that price (150€, i not accept that price and i take my tab to home), and that there may be a cable (I doubt it) that has the ability to connect your tablet to your PC even if bricked.
the tablet now is currently charging because battery is too low to poweron.
i hope you might help me. I'm desperate
The pc didn't recognize it in any way, try vol+ and power , vol- and power but nothing, can't access to flash menu and pc didn't recognize. how can i do?
http://forum.xda-developers.com/showthread.php?t=1766227 may help?
anthraxx90 said:
2 days ago i send my tf300 to asus but they called me this morning and ask for 150€ for repair (they told me: the flash memory must be change), i haven't this money, i take tablet to home this afternoon, there is a way to solve the problem by me without asus support? need help :crying:
Edit:I went to the center asus, and I taked my asus tablet, they told me that asus did that price (150€, i not accept that price and i take my tab to home), and that there may be a cable (I doubt it) that has the ability to connect your tablet to your PC even if bricked.
the tablet now is currently charging because battery is too low to poweron.
i hope you might help me. I'm desperate
The pc didn't recognize it in any way, try vol+ and power , vol- and power but nothing, can't access to flash menu and pc didn't recognize. how can i do?
http://forum.xda-developers.com/showthread.php?t=1766227 may help?
Click to expand...
Click to collapse
If you have cord plugged between pc and tablet and both powered on do you get anything if you use command ( adb devices )? I'm not talking about trying to get into any menu or using volume or anything else.
Just connect the cord between pc and tablet and give command.
You may have already done this but I'm not sure and it would be nice to know the message if the command fails!
tobdaryl said:
If you have cord plugged between pc and tablet and both powered on do you get anything if you use command ( adb devices )? I'm not talking about trying to get into any menu or using volume or anything else.
Just connect the cord between pc and tablet and give command.
You may have already done this but I'm not sure and it would be nice to know the message if the command fails!
Click to expand...
Click to collapse
What i must do exactly?
anthraxx90 said:
What i must do exactly?
Click to expand...
Click to collapse
connect powered tablet to pc and in terminal type - adb devices - tell me what response you get from command.
It may not work but is worth a try before you go farther.
If you have not set your path for adb you will need to cd into proper directory with terminal first before sending command. I can't even guess because I don't know your OS but since you had cwm you have used the terninal - Windows = cmd or command.com
tobdaryl said:
connect powered tablet to pc and in terminal type - adb devices - tell me what response you get from command.
It may not work but is worth a try before you go farther.
If you have not set your path for adb you will need to cd into proper directory with terminal first before sending command. I can't even guess because I don't know your OS but since you had cwm you have used the terninal - Windows = cmd or command.com
Click to expand...
Click to collapse
I use windows 8
{
"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"
}
http://tinypic.com/view.php?pic=2rwn4nd&s=6
(on my pc in programs file i've an asus folder with driver usb)
ok i've done it http://tinypic.com/view.php?pic=1vptd&s=6
but no device are listed under: list of devices attached
anthraxx90 said:
I use windows 8
http://tinypic.com/view.php?pic=2rwn4nd&s=6
Click to expand...
Click to collapse
This shows us you are in your home directory and your os does not know where adb is located. You probably used fastboot to flash cwm to your tablet. Fastboot and adb are normally in the same directory and you need to cd to that directory as you did when you flashed cwm.
If you don't know where that is located you can search for adb or fastboot.
Sorry I don't have windows, I'm using Ubuntu on a mac (I don't even use mac but have it on an external drive if needed). We can figure it out if we are both patient.
So if the above does not give needed results tell me and we'll adjust.
Ok i've tried fastboot and adb but fastboot tell me:wait for device and adb devices can't recognize tablet, there are no device under the list of connected device.
I've tried fastboot reboot and adb reboot to test if the device was connected but nothing happened.
anthraxx90 said:
Ok i've tried fastboot and adb but fastboot tell me:wait for device and adb devices can't recognize tablet, there are no device under the list of connected device.
I've tried fastboot reboot and adb reboot to test if the device was connected but nothing happened.
Click to expand...
Click to collapse
One step down. If you have tf300t on left side about one inch - 25.4 mm below sdcard there is a small hole (reset). With cord still plugged between pc and tablet, power on tablet and use a small paperclip to insert gently into hole. As you insert you will feel it stop, gently push slightly farther and you will feel a little spring.
This will cause your unit to restart and if we are lucky there will be a change in what happens with commands (adb - fastboot) and or what is displayed on the screen.
tobdaryl said:
One step down. If you have tf300t on left side about one inch - 25.4 mm below sdcard there is a small hole (reset). With cord still plugged between pc and tablet, power on tablet and use a small paperclip to insert gently into hole. As you insert you will feel it stop, gently push slightly farther and you will feel a little spring.
This will cause your unit to restart and if we are lucky there will be a change in what happens with commands (adb - fastboot) and or what is displayed on the screen.
Click to expand...
Click to collapse
i've done the reset, but nothing change with adb and fastboot
anthraxx90 said:
i've done the reset, but nothing change with adb and fastboot
Click to expand...
Click to collapse
Only two things left that I know about. You previously listed a link http://forum.xda-developers.com/showthread.php?t=1766227 that might possibly work but at the position we are in currently if it doesn't work we won't know the difference and the drivers already on your pc that are known to work will be replaced so.
1.
I have seen a post somewhere that the case was removed and the battery disconnected and then reconnected and that allowed access to the bootloader menu by holding down volume while reconnecting the battery.
2.
Try the drivers listed above.
Videos for removing case for battery access
1.
http://www.firstpost.com/topic/orga...former-battery-video-KJihe-hpA4M-14773-4.html
2.
http://www.youtube.com/watch?v=9eOu4Y9D33Y
I don't like either choice but with no adb or fastboot access, no recovery, and no bootloader menu we are pretty well trapped.
Just thought of something I have read twice recently. Even though fastboot appears to not work give it the command two or three times. I think I would try this first. Since a stock blob contains rom and recovery I would try to flash stock 10.4.2.13 blob.
fastboot -i 0x0B05 flash system blob
wait here because this is a big file
fastboot -i 0x0B05 reboot
You would unzip stock 10.4.2.13 twice to get the blob. Place the blob into the directory where you found fastboot.
tobdaryl said:
Only two things left that I know about. You previously listed a link http://forum.xda-developers.com/showthread.php?t=1766227 that might possibly work but at the position we are in currently if it doesn't work we won't know the difference and the drivers already on your pc that are known to work will be replaced so.
1.
I have seen a post somewhere that the case was removed and the battery disconnected and then reconnected and that allowed access to the bootloader menu by holding down volume while reconnecting the battery.
2.
Try the drivers listed above.
Videos for removing case for battery access
1.
http://www.firstpost.com/topic/orga...former-battery-video-KJihe-hpA4M-14773-4.html
2.
http://www.youtube.com/watch?v=9eOu4Y9D33Y
I don't like either choice but with no adb or fastboot access, no recovery, and no bootloader menu we are pretty well trapped.
Just thought of something I have read twice recently. Even though fastboot appears to not work give it the command two or three times. I think I would try this first. Since a stock blob contains rom and recovery I would try to flash stock 10.4.2.13 blob.
fastboot -i 0x0B05 flash system blob
wait here because this is a big file
fastboot -i 0x0B05 reboot
You would unzip stock 10.4.2.13 twice to get the blob. Place the blob into the directory where you found fastboot.
Click to expand...
Click to collapse
Ok i'll try to flash blob this afternoon at home, i hope it do something, cause i don't want open my tablet
Edit: i'm at home, the tablet's battery is low and it don't power on now, i to charge now and try
Nothing when i try to flash blob cmd is stop at waiting for devices.
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.
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.
Click to expand...
Click to collapse
windows don't see the tablet, i've tried but nothing, no usb input sound, it doesn't recognize tf300, i've already driver installed on pc
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.
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.
ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
{
"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"
}
Device; LG G2 D802 32GB
Some one please?
DroidsRugly said:
ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
Device; LG G2 D802 32GB
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.
This is why I worry messing around with my G2
Have you tried long holding the power button?
Sent from my Nexus 6 using Tapatalk
Same thing here. Any answers? I can hold the power button and it turns off for a second then turns itself on and these lines show up again. Same setup after using AutoRec on 4.4.2 rom.
This is a known problem. Have LG send you a new one
blastagator said:
This is a known problem. Have LG send you a new one
Click to expand...
Click to collapse
Sadly way outside the warranty. So it's pretty much toast?
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
Make sure you're phone is fully charged. I had a problem entering download mode with low battery. I also had to try different usb ports on my laptop for whatever reason.
Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.
walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
And sadly this was my phone. I switched for a while and was coming back and wanted an upgrade to the software. I hadn't updated from 4.4.2 as it had sat in a drawer, then did AutoRec (which I thought I had done before) and boom phone is completely unusable.
---------- Post added 27th December 2015 at 12:07 AM ---------- Previous post was 26th December 2015 at 11:55 PM ----------
dark_prince said:
Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.
Click to expand...
Click to collapse
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.
walkingagh said:
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.
Click to expand...
Click to collapse
Expand under "Ports Com Ports & LPT"
And you will see LGE Com Port Device.
Just flash the kdz away if u see so. otherwise go through the tot method if u see the com port devices to change the com port address to com41 and then flash tot.
I tried this on Windows 10, Windows 8.1, Windows 8 and Windows 7 (all 64-bit versions) and it worked on all of those. Even with USB 3.0 supported laptop.
Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files
wzedlare said:
Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files
Click to expand...
Click to collapse
Any good tutorials on fastboot? And those files come from a bootstack correct?
stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Same problem with me tried Kdz Method. But no luck any idea? It's been 3 months em using it like this. Any help?
Sent from my LG-D800 using Tapatalk
So pretty stuck at this point as well. KDZ method stalls at 60%.
UPDATE FASTBOOT WORKING! Took forever to figure out the drivers, but it's working. I have no clue what to do now.
Fastboot won't recognize the device though I have the fastboot driver installed and running. Any ideas?
TOT is just kinda giving up on me. Still chasing down any leads, but the phone feels pretty borked at this point.
Update: Now in download mode! Man this has been crazy. TOT working! Okay so here is how I did it.
First, I downloaded google's ADB drivers and installed the LG drivers as well. I am not sure which one did it. Then I plugged my phone in and went to device manager. For me, it had an unrecognized device and fastboot wasn't working. So I had to manually assign the driver.
Right click on the device and update driver > Let me choose > all devices > Google > LGE mobile ADB interface.
Now fastboot should be working.
Then I used the srktool_2.1. Option 4 then option 4 again, select model number. It reboots to black screen. From there I was able to completely power off (10 second hold on power button). And when it booted back up all the drivers installed. I was able to TOT back to stock using this guide. http://forum.xda-developers.com/showthread.php?t=2432476. KDZ might work as well.
Unfortunately the screen damage looks to be permanent. But I think this is worth more now than it was 30 minutes ago!
Hi Everyone
This is Guide how to repair your phone who was dead
My phone doesn't worked for 3 days so i get small trick and successfully repaired from dead
My phone was 5 times not worked like dead,Screen not Works ...only LED works,when i connect to pc usb device not recognized and nothing....
Explanation about my Problem:
IN MY CASE!
and the worst In my case Power button and Volume Buttons doesn't working so i open the BACK COVER eject the cable from volume button and insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
So we are starting the GUIDE:
1.First you need the drivers so you can get from this https://drive.google.com/folderview?id=0B1T7tp6tJ_3kX3p6SUxWb2NfWTQ&usp=sharing
2.After you installed the Drivers go to. Download mode if not goes try this... Press Volume UP and Volume DOWN and connect to usb to your pc
3.Go to device Manager to view the Port ,so the port can be "Android HS-USB QDLoader 9008 (COM3)"
4.Download the Panasonic Firmware Eluga and Extract (don't worry this is the same like idol 3 only name changed)https://docs.google.com/uc?id=0B01OmzpKE6vAVDhaSFN2aVFzaVU
5. After Extract you wil find EB-90S55EWLv1009.exe so run as administrator wait to load data
6.select 6045 and in the list down you can find your phone
7.and press the button "download"
8.So process starting ..indetifying your device you will get informations about imei..rooted or no .....
9.so automatically started to flashing the firmware (my it's go to 45 % and then i get error)
10.Don't worry press the button Reboot Device
11.and your device will reboot and you will view 'the screen powered by android and then panasonic so i get message Encrypted device just click the button "reset" and automatically device will be reseted and when wil finish with reset automatically reboots and wait to first boot you will get welcome screen set up and finished.....
12.So device successfully repaired from dead
If you want to go to CM or Stock for Idol 3
-i will write guide to unlock bootloader and flash TWRP recovery
-You must have Minimal Adb and Fastboot
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing " .powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-You successfully unlocked the bootloader one step more to flash the recovery
-Download the TWRP RECOVERY FROM THIS LINK:
https://www.androidfilehost.com/?fid=24421527759881858
-Then copy from when you downlaod and paste the recovery in C:\Program Files\Minimal ADB and Fastboot
-Press Shift in the directory and click Right on mouse and open command promt here
-Type fastboot -i 0x1bbb flash recovery twrp-3.0.0-1.img or fastboot -i 0x1bbb boot twrp-3.0.0-1.img (if you want to test before installation)
-so successfully installed recovery and flash CM Or whatever you want
[/SIZE][/COLOR][/B]
Sorry for Grammatical Errors!
This guide will repair from dead....
in my case , buttons also doesn't work , how did you opened the back cover?
xZrender said:
in my case , buttons also doesn't work , how did you opened the back cover?
Click to expand...
Click to collapse
here's video how you can open
https://www.youtube.com/watch?v=FrFE8FdTXrY
Alek Dev said:
Hi Everyone
IN MY CASE!
and the worst In my case Power button and Volume Buttons doesn't working so i open the BACK COVER eject the cable from volume button and insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
Click to expand...
Click to collapse
i opened back cover , but how did you press the volume button , it doesnt work for me , i ont know what to do ;/
xZrender said:
i opened back cover , but how did you press the volume button , it doesnt work for me , i ont know what to do ;/
Click to expand...
Click to collapse
Eject cable from motherboatd....insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
problem with idol 3 4.7 6039K
Hi there,
I don't know if this is the correct section, I hope so, otherwise I really appreciate you can drive me to the appropriate one, it's new for me this forum!
I have an idol 3 4.7, where I have installed kingroot and after I took out (I didn´t reset the phone, Just unistall the app),
yesterday i received the update system message, I imagine for the marshmallow update, so I say Yes, install it.
But the phone entered in bootloop. I only have the initial screen with the options as Reboot system, adb and so on.
I tried to wipe but nothing. So now my phone stucked. I tried with an assistance center in Quito but they could't
My questions are:
may I use this system for 6039K?
Or does anybody hear about a solution in this case?
Should I open and take out the battery?
Please, any suggestion will be really welcome in order to make the phone work again.
P.
nipozzano said:
Hi there,
I don't know if this is the correct section, I hope so, otherwise I really appreciate you can drive me to the appropriate one, it's new for me this forum!
I have an idol 3 4.7, where I have installed kingroot and after I took out (I didn´t reset the phone, Just unistall the app),
yesterday i received the update system message, I imagine for the marshmallow update, so I say Yes, install it.
But the phone entered in bootloop. I only have the initial screen with the options as Reboot system, adb and so on.
I tried to wipe but nothing. So now my phone stucked. I tried with an assistance center in Quito but they could't
My questions are:
may I use this system for 6039K?
Or does anybody hear about a solution in this case?
Should I open and take out the battery?
Please, any suggestion will be really welcome in order to make the phone work again.
P.
Click to expand...
Click to collapse
Hello
This Guide only works with Idol 3 5.5
but i will explain how to restore your device
Can you try with Mobile upgrade Q to restore,if doesn't work
Use this guide from wiemar ,it should help to you because it's for your model
http://forum.xda-developers.com/showpost.php?p=63709274&postcount=113
If you any questions ask me
Hi ! I follow the guide up to the section 9, unfortunately, in the Panasonic Firmware Eluga and Extract after pressing download it stops after 2% and I have got the error message "load nprg error error code 5002". Does someone know how to fix that ?
Thanks !
Error
I get: "Master Clear: FAIL Flash Status: [COM3->PC[3]] COM3->PC[3] failed to erase misc (Error code = 40016) " :crying:
Now I get the same error that matcail... did you solved it ???
Good tutorial but it does not help me. My phone keeps on rebooting.
Schumi_wk said:
Good tutorial but it does not help me. My phone keeps on rebooting.
Click to expand...
Click to collapse
Tell me info About your phone? Model,Country,ROM...../?
All is standard, no root, no twrp and the latest software from alcatel, the model is 6045Y. But all of a sudden my phone decided to random reboot and it didn't stop
So i looked to unbrick it and came with a couple of options, first i tried to sideload software but that didn't work, than i tried it with Mobile upgrade from alcatel and that didn't work.
Than i saw this thread and tried it twice but after Panasonic and the sound it starts to reboot again. Now i'm trying again with Mobile upgrade.
All that is changed is the recovery interface it looks now like it is from MM.
Schumi_wk said:
All is standard, no root, no twrp and the latest software from alcatel, the model is 6045Y. But all of a sudden my phone decided to random reboot and it didn't stop
So i looked to unbrick it and came with a couple of options, first i tried to sideload software but that didn't work, than i tried it with Mobile upgrade from alcatel and that didn't work.
Than i saw this thread and tried it twice but after Panasonic and the sound it starts to reboot again. Now i'm trying again with Mobile upgrade.
All that is changed is the recovery interface it looks now like it is from MM.
Click to expand...
Click to collapse
More Looks like Hardware Problem Try again with Mobile q if not works...Send to warranty repair.....
Alek, thank you for this great guide. It saved my 6045k model.
I was messing around with AlekOS 3.0, had issues with lock screen and experimented with modems. I managed to permanently disable secondary sim slot (was using famewolf's modem backups). I forgot to copy modem.img backup to my PC! Also tried bunch of TWRP backups with no luck. My last hope was Mobile Upgrade Q and reverting back tu 5.0.2. Unfortunately with no success (only one sim slot is recognized again).
Finally I found this thread, followed the guide and I can confirm that it did solve sim issue. The setup finished with no errors that you mentioned. It got stuck at 45%, but after a while (10min) it completed successfully.
Cheers!
I'm in the same situation as you,but my problem is that Panasonic Eluga doesn't recognice my devide,drivers are correctly installed,I checked everything but nothing:
{
"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´ve tried everything to downgrade my device (Mobile Q doesn't work) but nothing :crying:
peito said:
I'm in the same situation as you,but my problem is that Panasonic Eluga doesn't recognice my devide,drivers are correctly installed,I checked everything but nothing:
I´ve tried everything to downgrade my device (Mobile Q doesn't work) but nothing :crying:
Click to expand...
Click to collapse
You must do something Wrong...Press Pwr button and Volume up and down and thern connect to PC and then you will get RED SCREEN....Press Volume Up until you get Black screen and then press Download and if you get again same Send me Pm with Teamviewer ID AND PASS and i will try to help you
eXoSaX said:
Alek, thank you for this great guide. It saved my 6045k model.
I was messing around with AlekOS 3.0, had issues with lock screen and experimented with modems. I managed to permanently disable secondary sim slot (was using famewolf's modem backups). I forgot to copy modem.img backup to my PC! Also tried bunch of TWRP backups with no luck. My last hope was Mobile Upgrade Q and reverting back tu 5.0.2. Unfortunately with no success (only one sim slot is recognized again).
Finally I found this thread, followed the guide and I can confirm that it did solve sim issue. The setup finished with no errors that you mentioned. It got stuck at 45%, but after a while (10min) it completed successfully.
Cheers!
Click to expand...
Click to collapse
Alek Dev said:
You must do something Wrong...Press Pwr button and Volume up and down and thern connect to PC and then you will get RED SCREEN....Press Volume Up until you get Black screen and then press Download and if you get again same Send me Pm with Teamviewer ID AND PASS and i will try to help you
Click to expand...
Click to collapse
That is exactly what I'm doing,entering in Download mode and then download in the Panasonic software,but nothing,the program cannot read my phone,I'm really tired of trying this,I will stuck in your Alek rom (btw,no matter how many times I flash your modem,I cannot get the lock screen ).Ty anyway Alek and keep it up!!!!
Was on alek 3.0 before bootloop appear after a strange warning on android about battery, now got bootloop, no twrp access etc
try ur solution but after 45% and error, reboot and no screen about panasonic only bootloop
11.and your device will reboot and you will view 'the screen powered by android and then panasonic so i get message Encrypted device just click the button "reset" and automatically device will be reseted and when wil finish with reset automatically reboots and wait to first boot you will get welcome screen set up and finished.....
Click to expand...
Click to collapse
already tried SUGAR+QCT_SP+v10.5.1(4pda source) and mobile upgrade q 5.0.9, both finished without error after 100% but still bootloop
i think it s total broke with motherboard pb or battery
thorfr said:
Was on alek 3.0 before bootloop appear after a strange warning on android about battery, now got bootloop, no twrp access etc
try ur solution but after 45% and error, reboot and no screen about panasonic only bootloop
already tried SUGAR+QCT_SP+v10.5.1(4pda source) and mobile upgrade q 5.0.9, both finished without error after 100% but still bootloop
i think it s total broke with motherboard pb or battery
Click to expand...
Click to collapse
Looks Like Problem With Motherboard and Battery ..you can try again with Panasonic Firmware Tool and if this not help Send it to Warranty Repair
ok i m gonna send it to warr:crying:antly
retry mobil q upgrage wo success bootloop again