Hey everyone,
I have an LG P500 ( AT&T Variant - 'LG Thrive'). I had it rooted, although this is not the cause of the bricking. One day all of a sudden out of the blue it would not boot. After pressing the power button, the LG logo will come on, and the 4 button LEDs will flash 4 times and stay lit and the device will continue to stay on the LG screen. Currently this is the status of my device. ADB or fastboot are unable to notice the device whether it's on the LG screen, Emergency mode, or the console looking screen (white text/black background). FYI, I never had CWM or any alternate recovery program installed. Also - suggestions for the KDZ program would not be helpful, I run Linux and do not have access to a Windows computer.
Thanks for any help!
ok try factory reset power+vol down +home
hold them till u see android
androidisfuture said:
ok try factory reset power+vol down +home
hold them till u see android
Click to expand...
Click to collapse
This just brings me to the udc_start terminal looking screen (white text/black background).
rjortiz said:
This just brings me to the udc_start terminal looking screen (white text/black background).
Click to expand...
Click to collapse
Ok if that doesnt' works, you try this,, Power + Volume Up + Home,, that's how i use to make a factory reset on my thrive
And if that doesn't work either try this http://forum.xda-developers.com/showthread.php?t=1088046, this helped me to unbrick my thrive,, take note, that you will need a windows computer,, don't know if this works on ubuntu or another linux variant
If you decide to try the second method pm me
gabo_lope said:
Ok if that doesnt' works, you try this,, Power + Volume Up + Home,, that's how i use to make a factory reset on my thrive
Click to expand...
Click to collapse
This key combo has no effect on my device.
gabo_lope said:
And if that doesn't work either try this http://forum.xda-developers.com/showthread.php?t=1088046, this helped me to unbrick my thrive,, take note, that you will need a windows computer,, don't know if this works on ubuntu or another linux variant
If you decide to try the second method pm me
Click to expand...
Click to collapse
Basically this thread is showing how to flash recovery through fastboot, which I can/have tried through my system. As I mentioned, fastboot does not recognize the phone, nor will anything transfer through it (or through ADB).
I'm not sure but I'm starting to think that the last time my phone worked I did not have debugging enabled. Would that cause this current problem? Although, the phone does display the console screen:
Code:
fastboot mode started
udc.start()
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
--suspend--
deleted
gabo_lope said:
that shows when you plug it in on the computer?
Click to expand...
Click to collapse
It shows this only when I do the key combo VolDn+Home+Power. Plugging it into the computer has no effect - it goes to the LG logo screen.
rjortiz said:
It shows this only when I do the key combo VolDn+Home+Power. Plugging it into the computer has no effect - it goes to the LG logo screen.
Click to expand...
Click to collapse
on what linux version are you on?
gabo_lope said:
on what linux version are you on?
Click to expand...
Click to collapse
kUbuntu, the system works fine connecting to my other Android based phone - so that is not an issue. I also have a Debian system to use if I needed to.
rjortiz said:
kUbuntu, the system works fine connecting to my other Android based phone - so that is not an issue. I also have a Debian system to use if I needed to.
Click to expand...
Click to collapse
OK, so if you say that fastboot doesn't recognizes the phone, i would guess that you have the android sdk, for fastboot to work,,, also the phone was recognized before by the computer??
just had an idea,, i will try on my computer...
well i tried to screw up my phone, by using using an incorrect recovery,, to recover it using ubuntu, the phone was recognized, and i recover it, but i had debugging enabled, and as you said before you have it disabled... The thing is this: i booted into the rom, and turn off the debugging, then i screw up my phone again and connect it, and it wasn't recognized,, I run out of ideas, maybe someone else knows a way to comunicate the phone and the computer.
The only thing left would be using KDZ, but that's a windows program, you could use wine, but even running it on windows sometimes causes a hard brick, i couldn't image what would happen if you use it on wine, so if you still have warranty i suggest you to use it
My best of luck...
gabo_lope said:
,, also the phone was recognized before by the computer??
just had an idea,, i will try on my computer...
Click to expand...
Click to collapse
I wanted to state that my other Android phone connects to this computer fine, therefore saying the computer itself does not have a problem with connecting. But, no, this bricked phone is not recognized by the computer.
gabo_lope said:
OK, so if you say that fastboot doesn't recognizes the phone, i would guess that you have the android sdk, for fastboot to work,,, also the phone was recognized before by the computer??
just had an idea,, i will try on my computer...
well i tried to screw up my phone, by using using an incorrect recovery,, to recover it using ubuntu, the phone was recognized, and i recover it, but i had debugging enabled, and as you said before you have it disabled... The thing is this: i booted into the rom, and turn off the debugging, then i screw up my phone again and connect it, and it wasn't recognized,, I run out of ideas, maybe someone else knows a way to comunicate the phone and the computer.
The only thing left would be using KDZ, but that's a windows program, you could use wine, but even running it on windows sometimes causes a hard brick, i couldn't image what would happen if you use it on wine, so if you still have warranty i suggest you to use it
My best of luck...
Click to expand...
Click to collapse
Thank you for all your help and attempts to recreate the problem...I hope your phone isn't completely bricked as well.
rjortiz said:
Thank you for all your help and attempts to recreate the problem...I hope your phone isn't completely bricked as well.
Click to expand...
Click to collapse
that's the thing, i was able to recover my phone using this windows tool http://forum.xda-developers.com/showthread.php?t=1827723
rjortiz said:
Hey everyone,
I have an LG P500 ( AT&T Variant - 'LG Thrive'). I had it rooted, although this is not the cause of the bricking. One day all of a sudden out of the blue it would not boot. After pressing the power button, the LG logo will come on, and the 4 button LEDs will flash 4 times and stay lit and the device will continue to stay on the LG screen. Currently this is the status of my device. ADB or fastboot are unable to notice the device whether it's on the LG screen, Emergency mode, or the console looking screen (white text/black background). FYI, I never had CWM or any alternate recovery program installed. Also - suggestions for the KDZ program would not be helpful, I run Linux and do not have access to a Windows computer.
Thanks for any help!
Click to expand...
Click to collapse
ADB wont recognize your phone if you cant enter fastboot.
What you can do is.. enter emergency mode andUse this tool.. its safe.
The recovery image given is for P500.. so replace it with thrive's recovery image.. partition data is ok to use!!
rr0yy said:
ADB wont recognize your phone if you cant enter fastboot.
What you can do is.. enter emergency mode andUse this tool.. its safe.
The recovery image given is for P500.. so replace it with thrive's recovery image.. partition data is ok to use!!
Click to expand...
Click to collapse
LGMDP is for Windows and won't run correctly in WINE.
Install VMware.. then you can install windows over it.
It will be like using windows over linux.. you dont need any partition or anything for that.
After you are done.. you can remove it easily!!
Are you running fastboot in terminal with root permissions
Sent from my LG-P500 using xda app-developers app
lg-one-man said:
Are you running fastboot in terminal with root permissions
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
I've tried both, either way gets the same result of nothing.
Regardless, I stated that I can use this computer to successfully connect to my other phone because I wanted to eliminate the possibility of the computer as a problem with connecting to the device.
When you run fastboot in terminal and then type device ,what does it say?
Sent from my LG-P500 using xda app-developers app
lg-one-man said:
When you run fastboot in terminal and then type device ,what does it say?
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
It prints nothing and quits. For 'adb devices' it says "List of attached devices" and lists nothing.
Code:
[email protected]:...$ ./fastboot devices
[email protected]:...$ ./adb devices
List of devices attached
[email protected]:...$
Related
I was wondering if this is happened to anyone else. When i put my phone into ap fastboot mode, windows does not detect new hardware to install drivers for fastboot. If i boot phone normally, my pc recognizes the phone and installs a list of drivers. I am trying to fxz back to stock, but not luck. I read that once in ap fastboot, "Transfer Mode: USB Connected" should appear once conected to pc, mine does not. Any help would be appreciated, trying to get on that ICS train.
Clericgram said:
I was wondering if this is happened to anyone else. When i put my phone into ap fastboot mode, windows does not detect new hardware to install drivers for fastboot. If i boot phone normally, my pc recognizes the phone and installs a list of drivers. I am trying to fxz back to stock, but not luck. I read that once in ap fastboot, "Transfer Mode: USB Connected" should appear once conected to pc, mine does not. Any help would be appreciated, trying to get on that ICS train.
Click to expand...
Click to collapse
The "Transfer Mode: USB Connected will show in your phone, not on your PC. Once you see this on tour phone's screen, you can run the restore script.
Sent from my MB865 using xda's premium carrier pigeon service
Correct, "Transfer Mode: USB Connected" does not show up on my phone.
Clericgram said:
Correct, "Transfer Mode: USB Connected" does not show up on my phone.
Click to expand...
Click to collapse
Try a different USB cable. That has happened to me before, I know it sounds odd, and it is, but give it a shot.
I have tried 2 different cables, i will fish out a third.
Have you tried restarting your PC? Sometimes Windows gets goofy and needs a restart. Also, are you using the USB port from the back of the PC, not the front?
Sent from my MB865 using xda's premium carrier pigeon service
I am suspecting that i have a power issue with my setup.I removed other devices from my pc and Rsd lite recognizes the phone in ap fastboot but the phone does not say "Transfer Mode: USB Connected". Trying flash now but seems to be stuck on 2/18 reboot bootloader.
Edit: Failed Flashing Process No arrival message
Apex_Strider said:
Have you tried restarting your PC? Sometimes Windows gets goofy and needs a restart. Also, are you using the USB port from the back of the PC, not the front?
Sent from my MB865 using xda's premium carrier pigeon service
Click to expand...
Click to collapse
From the back.
So the only way that rsd can detect the phone in fastboot, is if i restart my computer with the phone plugged in, and in fastboot mode. This is very weird to me because i have fxz in the past.
In device manager fastboot is recognized as MOT Single ADB Interface.
Any Ideas?
Clericgram said:
So the only way that rsd can detect the phone in fastboot, is if i restart my computer with the phone plugged in, and in fastboot mode. This is very weird to me because i have fxz in the past.
In device manager fastboot is recognized as MOT Single ADB Interface.
Any Ideas?
Click to expand...
Click to collapse
The last time I tried using AP Fastboot to run my returntostock.script it wouldn't complete, and got an error. So, I had to use RDSLite, and it worked like a charm. I haven't needed to FXZ since then, so don't know if it was a fluke that time. So, are you now able to FXZ via RSDLite now?
Sent from my MB865 using xda's premium carrier pigeon service
Apex_Strider said:
The last time I tried using AP Fastboot to run my returntostock.script it wouldn't complete, and got an error. So, I had to use RDSLite, and it worked like a charm. I haven't needed to FXZ since then, so don't know if it was a fluke that time. So, are you now able to FXZ via RSDLite now?
Sent from my MB865 using xda's premium carrier pigeon service
Click to expand...
Click to collapse
No Failed Flashing Process no arrival message 2/18
I tried reinstalling drivers and rsd.
Don't know why i did not try this earlier, but i just fixed my issue by doing it on my laptop.
I got the same issue. Sorry I didn't see this thread before. Although mine says "transfer mode" but it will not boot into the recovery. Heck If I can't do it tonight, I'll do it tomorrow on my XP com. Stupid WIN7...
Fall of Enosis said:
I got the same issue. Sorry I didn't see this thread before. Although mine says "transfer mode" but it will not boot into the recovery. Heck If I can't do it tonight, I'll do it tomorrow on my XP com. Stupid WIN7...
Click to expand...
Click to collapse
Power off the phone. Hold both vol buttons, then hit the power button. Once it's in recovery, vol down to apfastboot, vol up to select it.
Plug in the phone, open rsdlite, you should see your phone connected now.
Flash the FXZ and go from there.
41rw4lk said:
Power off the phone. Hold both vol buttons, then hit the power button. Once it's in recovery, vol down to apfastboot, vol up to select it.
Plug in the phone, open rsdlite, you should see your phone connected now.
Flash the FXZ and go from there.
Click to expand...
Click to collapse
Oh that's not what I'm saying mate, I know how to physically get into recovery. But I am saying that the first thing ADB does to start the FXZ flash process is reboot the phone into recovery. And it won't.
And also, for some reason it's not recognizing the device properties. Oh well, I'll do it tomorrow on my dependable XP machine LOL.
Fall of Enosis said:
Oh that's not what I'm saying mate, I know how to physically get into recovery. But I am saying that the first thing ADB does to start the FXZ flash process is reboot the phone into recovery. And it won't.
And also, for some reason it's not recognizing the device properties. Oh well, I'll do it tomorrow on my dependable XP machine LOL.
Click to expand...
Click to collapse
Ah, moto is touchy with driver installation and device recognition. I would unplug your phone, uninstall moto device manager, then reboot.
After reboot, reinstall moto device manager, and reboot again.
After the reboot, plug your phone in, it should be clean drivers and newly recognized devices.
After everything is recognized and installed, open adb and check to see if your device is recognized for good measure. If all checks out, try flashing the FXZ again. On a side note, in your program files((x86) if you run 64bit win) you see an RSDlite folder, inside is SDL.exe (that's RSDlite). Right click and run it as an administrator. Hopefully this helps.
Sorry if some of this seems noobish, I'm just going by what works for me and sharing.
This fixed RSD not seeing my phone even with the correct drivers... I am running Windows 7 x64
http://forum.xda-developers.com/showpost.php?p=22986758&postcount=16
Same on Droid 4
I am having the same problem with my Droid 4 and after reading this thread,I will try all the options and methods you guys have described here. Thanks for the great info!!
EDIT: I booted into my Ubuntu Linux with the phone connected through AP Fastboot mode and Ubuntu recognized my phone right away. Try using Linux,it works much better than Windows. Just read how to do things with Linux if you are not experienced with it. My Windows 7 x64 did not recognize the phone AT ALL in AP Fastboot so I went to Linux.
Clericgram said:
So the only way that rsd can detect the phone in fastboot, is if i restart my computer with the phone plugged in, and in fastboot mode. This is very weird to me because i have fxz in the past.
In device manager fastboot is recognized as MOT Single ADB Interface.
Any Ideas?
Click to expand...
Click to collapse
i may be up a creek now. i've tried everything i can.
here's the whole situation, maybe someone can offer some guidance on how i can get my phone back.
i installed this rom, http://forum.xda-developers.com/showthread.php?t=1835478, but did not see that there was a problem with people getting stuck at the initial google boot logo. i wouldn't have tried it if i did.
but it's too late now. so i too have that problem. in addition, i also have that problem with the nexus s in that the power button is busted, works only to boot the phone.
so i boot the phone normally, i get to that boot logo indefinitely.
i press up and power button i get to fastboot screen. for some reason the volume buttons don't work on that screen so i can't pick recovery there. only thing that works is hitting the power button and reboots the bootloader.
i plug the phone into my pc and i can't access it through adb, fastboot... does not recognize a device is connected.
so in summary, all i can do is access the fastboot screen or the boot logo screen.
if someone can help me figure out how to do one of the following: boot into recovery instead of fastboot, figure out how to use the volume buttons in fastboot, or get the phone recognized by my pc so i can use adb, that would be awesome.
i feel like i just bricked it for good....
thanks
Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)
Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium
i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.
Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2
in the prior rom it was recognized by the laptop, before i tried to flash the rom i linked above that created this mess...
albundy2010 said:
Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)
Click to expand...
Click to collapse
AlphaEchoViktorSierra said:
Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yep fastboot is a great tool, if you have a nexus s then you MUST get it working!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
wookietv said:
i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.
Click to expand...
Click to collapse
Seems like your nexus s drivers are not installed in your laptop
google the nexus s usb drivers download them and put in the respective folder
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
albundy2010 said:
Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
was gonna ask the same question
like i said, i already had the sdk and drivers installed.
they worked fine before i installed that rom.
this definitely seems like it's on the fault of the phone, not the laptop.
looks like you got busted like a SIR!!
Just kidding man dont take it seriously...
I might sound silly but i hope you have tried this but if you have not then do try
Go here and try changing the usb plugs
http://forum.xda-developers.com/showthread.php?t=1785672
IT shows flashboot steps, you need to connect phone in bootloader mode which you are achieving atm, and see if it works
and if it doesnt then let me know i will try to help out more if i could
P.S I am also new in android so pardon my noobnes
i went another route...
i figured i had nothing to lose at this point... so i ripped the phone apart and attempted to fix the power button, which i believed in turn would fix not being able to use the volume keys in the fastboot screen.
i was correct. i jiggled with the power button inside and it seemed to work. the volume keys now reacted in the fastboot screen.
i was able to then get into recovery, wipe the phone, connect the phone to the laptop and put a new rom on it.
i'm not sure if its fixed the button completely, but at least i can get into the new rom :laugh:
well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future
converse5 said:
well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future
Click to expand...
Click to collapse
+1, I agree with you. It does not cost much as well. I had this problem and was managing with apps. But finally got it replaced for good.
Hello all,
I seem to have really soft bricked my TF300TG. I've now run out of ideas and maybe someone in here can help.
The following happend: I wanted to update my rooted TF300TG from running JB (CleanRom 3.0.4) with Bootloader ww_epad_10.4.3.9 to the current stock Rom from ASUS ( V10.6.2.6 ). I did unzip the zip from ASUS once and used the resulting zip for the flash.
I attemted this via Method 3: TWRP v. 2.5.0.0, following this guide (http://forum.xda-developers.com/showthread.php?t=2187982), guess I should have read the whole thread, not just the first 20 pages.
What happend was, that during the flash in TWRP I got an error with no error message. I tried to flash again for three times with the "same" error. Thats when I panicked and rebooted the device.
Since then its sitting here, just showing the ASUS logo and doing nothing. I think I understand why its doing nothing since I have still the old bootloader v 10.4.3.9 but a new 4.2 Stock ROM (albeit maybe damaged).
Sadly I have also had no success communicating with the device via ADB or Fastboot.
I still can access the bootloader menue which shows 4 icons: RCK, Android, USB and Wipe. But: the volume up key is not working (did work in Android though) and the volume down key traverses the item entries. So I have no way to select USB which should put me into fastboot mode.
Does anyone have any idea? Otherwise I'm declaring this my last Android tablet (loved it but it didn't quite live up to expectations, Tegra 3 just sucks) and move on.
Thanks for reading!
jak4kaj said:
Hello all,
I seem to have really soft bricked my TF300TG. I've now run out of ideas and maybe someone in here can help.
The following happend: I wanted to update my rooted TF300TG from running JB (CleanRom 3.0.4) with Bootloader ww_epad_10.4.3.9 to the current stock Rom from ASUS ( V10.6.2.6 ). I did unzip the zip from ASUS once and used the resulting zip for the flash.
I attemted this via Method 3: TWRP v. 2.5.0.0, following this guide (http://forum.xda-developers.com/showthread.php?t=2187982), guess I should have read the whole thread, not just the first 20 pages.
What happend was, that during the flash in TWRP I got an error with no error message. I tried to flash again for three times with the "same" error. Thats when I panicked and rebooted the device.
Since then its sitting here, just showing the ASUS logo and doing nothing. I think I understand why its doing nothing since I have still the old bootloader v 10.4.3.9 but a new 4.2 Stock ROM (albeit maybe damaged).
Sadly I have also had no success communicating with the device via ADB or Fastboot.
I still can access the bootloader menue which shows 4 icons: RCK, Android, USB and Wipe. But: the volume up key is not working (did work in Android though) and the volume down key traverses the item entries. So I have no way to select USB which should put me into fastboot mode.
Does anyone have any idea? Otherwise I'm declaring this my last Android tablet (loved it but it didn't quite live up to expectations, Tegra 3 just sucks) and move on.
Thanks for reading!
Click to expand...
Click to collapse
Try resetting the device (the little hole beneath the volume rocker and try to get to fastboot. there is no real reason other than broken PITs or trashfiles in /misc that should prevent you form getting fastboot.
also read my post here (or better the threat)
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
buster
Buster99 said:
Try resetting the device (the little hole beneath the volume rocker and try to get to fastboot. there is no real reason other than broken PITs or trashfiles in /misc that should prevent you form getting fastboot.
also read my post here (or better the threat)
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
buster
Click to expand...
Click to collapse
Hi buster,
thanks for the reply. Sadly I can't seem to enter fastboot since "fastboot erase system" stays at "waiting for device" when I reset the device with a paper clip and press the volume down button.
I'm trying this on linux but that should be a plus versus using windows.
Thanks again
jak4
jak4kaj said:
Hi buster,
thanks for the reply. Sadly I can't seem to enter fastboot since "fastboot erase system" stays at "waiting for device" when I reset the device with a paper clip and press the volume down button.
I'm trying this on linux but that should be a plus versus using windows.
Thanks again
jak4
Click to expand...
Click to collapse
yeah - linux sometimes is less of a nightmare when it comes to fastboot commands - but remember to install adb and fastboot
gl
Buster
Buster99 said:
yeah - linux sometimes is less of a nightmare when it comes to fastboot commands - but remember to install adb and fastboot
gl
Buster
Click to expand...
Click to collapse
Yes I have fastboot and adb installed. They come with the Android SDK which I need for work.
jak4
I have the same problem. Difference is that I did a reset after a failed install of CM11. Stuck at ASUS splash. Cannot access recovery or any other option that was previously available. Nothing is detecting the device as it sits...Tried Ubuntu, Win 7, Win 8.1. I have tried installing all drivers I could find, even tried installing as legacy device, but all drivers give an error that device cannot start. Did A LOT of searching around, and it seems to come down to the tablet not being detected by PC in the state it's in. Seems like there is a lot of help out there for folks that can get their computers to at least see the device.
Would die for some help!
coppervines said:
I have the same problem. Difference is that I did a reset after a failed install of CM11. Stuck at ASUS splash. Cannot access recovery or any other option that was previously available. Nothing is detecting the device as it sits...Tried Ubuntu, Win 7, Win 8.1. I have tried installing all drivers I could find, even tried installing as legacy device, but all drivers give an error that device cannot start. Did A LOT of searching around, and it seems to come down to the tablet not being detected by PC in the state it's in. Seems like there is a lot of help out there for folks that can get their computers to at least see the device.
Would die for some help!
Click to expand...
Click to collapse
what recovery did you use for installing cm11?
Buster99 said:
what recovery did you use for installing cm11?
Click to expand...
Click to collapse
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.
coppervines said:
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.
Click to expand...
Click to collapse
yeah well with an old recovery kitkat gets you a brick - try to get it somehow to fastboot and you should be able to get it working again
gl
buster
Buster99 said:
yeah well with an old recovery kitkat gets you a brick - try to get it somehow to fastboot and you should be able to get it working again
gl
buster
Click to expand...
Click to collapse
I would hate to think that my USB cable could be bad...it's been a LONG time since its done anything other than charge. Just need the pc to see the damn thing. ANY insight would be helpful.
APX
I was able to get to APX mode with the universal drivers (Vol +reset)...looking around to see if anyone else has had success. I never installed Nvflash...
in the other threat a guy just needed a working cable to get it to work. it's a pain with asus and the cable
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
in the other threat a guy just needed a working cable to get it to work. it's a pain with asus and the cable
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What thread? Not sure I understand what you mean...
http://forum.xda-developers.com/showthread.php?t=2179759
Sent from my TF300T using XDA Premium 4 mobile app
Buster99 said:
http://forum.xda-developers.com/showthread.php?t=2179759
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Since i have apx access, i'm assuming the data side of the cable is working...plus, without being able to get into adb/fastboot on the tablet a new cable would be useless. Thinking about getting a mobo on ebay...one for 50 and one for 75$ i think. will have to get wife's approval first
coppervines said:
Since i have apx access, i'm assuming the data side of the cable is working...plus, without being able to get into adb/fastboot on the tablet a new cable would be useless. Thinking about getting a mobo on ebay...one for 50 and one for 75$ i think. will have to get wife's approval first
Click to expand...
Click to collapse
So I'm assuming there is no solution to this problem without sending it to ASUS or getting a new Motherboard?
I'm in the exact same position...
coppervines said:
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.
Click to expand...
Click to collapse
Wipe data from the bootloader erases everything, if you don't have nvflash blobs I think you're done for.
ebildude123 said:
Wipe data from the bootloader erases everything, if you don't have nvflash blobs I think you're done for.
Click to expand...
Click to collapse
"bootloader wipe data" soft brinks your tab.
always use custom recovery or fastboot to wipe the tf300t.
otherwise you need to erase all partitions and reflash recovery and start from scratch. assuming that fastboot still works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
"bootloader wipe data" soft brinks your tab.
always use custom recovery or fastboot to wipe the tf300t.
otherwise you need to erase all partitions and reflash recovery and start from scratch. assuming that fastboot still works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Boot loader wipe is a hard(ish) brick unless you have nvflash blobs since all you have access to is apx mode, no boot loader, no recovery, etc.
Sent from my TF300T on OmniROM (4.4.2) using Tapatalk 4
not necessarily, I did it for cm10.1 (drunken flashing not advised ) and i don't have an NV backup.
and i had fastboot to work with.
but things may have changed since then.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
I was trying wipe everything on the phone but for some reason it saids no OS. So when it boots up, I only see the google word on the screen.
Trying to flash the stock rom, followed instruction to install adb drivers...etc then boot the phone into fastboot mode,. This is the one screen I can get so far. Looks like my pc can't detect my phone. it saids failed when running those commands...Can someone give me a hint what to do next?
All I want is to put the stock rom back in.
thx
you didnt wipe data, you wiped your system partition, wiped the rom off your phone. and that screenshot is the stock recovery. you need to boot into the bootloader to flash the factory img(stock). the bootloader is the same as fastboot mode.
I did wipe data. I remember I checked that box
I also got this error in the command line.
simms22 said:
you didnt wipe data, you wiped your system partition, wiped the rom off your phone. and that screenshot is the stock recovery. you need to boot into the bootloader to flash the factory img(stock). the bootloader is the same as fastboot mode.
Click to expand...
Click to collapse
benzso63 said:
I did wipe data. I remember I checked that box
I also got this error in the command line.
Click to expand...
Click to collapse
before you tried any code.. did you do "fastboot devices" first, to make sure fastboot sees your phone?
also, sounds like you used twrp recovery. if you just swipe on the wipe screen, it wipes your partitions. if you chose advanced, then it gives you a list of things to wipe, then all you'd do is choose data and wipe.
I power down the phone, hit vol down + power. And I see the Fastboot mode
I connected the usb cable to my pc, but when I ran the code, it saids device not found. My pc can't see it
Now I am not using twrp at all just want to at least have the fastboot mode see my pc. but it is not.
Any other step i can make the phone communicate to my pc ?
simms22 said:
before you tried any code.. did you do "fastboot devices" first, to make sure fastboot sees your phone?
also, sounds like you used twrp recovery. if you just swipe on the wipe screen, it wipes your partitions. if you chose advanced, then it gives you a list of things to wipe, then all you'd do is choose data and wipe.
Click to expand...
Click to collapse
benzso63 said:
I power down the phone, hit vol down + power. And I see the Fastboot mode
I connected the usb cable to my pc, but when I ran the code, it saids device not found. My pc can't see it
Now I am not using twrp at all just want to at least have the fastboot mode see my pc. but it is not.
Any other step i can make the phone communicate to my pc ?
Click to expand...
Click to collapse
you're going to have to install that driver first, before it'll see your phone. you are using windows? try koushes universal adb driver for windows http://www.koushikdutta.com/post/universal-adb-driver
I did. I installed it. I have tried different drivers.
If I goto device manager, Android Device and under that it saids "Android Bootloader Interface".
I don't see anything saying Nexus or so.
simms22 said:
you're going to have to install that driver first, before it'll see your phone. you are using windows? try koushes universal adb driver for windows http://www.koushikdutta.com/post/universal-adb-driver
Click to expand...
Click to collapse
benzso63 said:
I did. I installed it. I have tried different drivers.
If I goto device manager, Android Device and under that it saids "Android Bootloader Interface".
I don't see anything saying Nexus or so.
Click to expand...
Click to collapse
If everything else fails try lg flashtool as a plan B. Link in my signagure.
Will try everything you say. Also this is a screen capture.
When I put the phone in fastboot mode, I notice this pops up under device manager (screen shot)
So does it mean it detects the phone right? But for some reason when I run the command code, it saids device not found.
bitdomo said:
If everything else fails try lg flashtool as a plan B. Link in my signagure.
Click to expand...
Click to collapse
benzso63 said:
Will try everything you say. Also this is a screen capture.
When I put the phone in fastboot mode, I notice this pops up under device manager (screen shot)
So does it mean it detects the phone right? But for some reason when I run the command code, it saids device not found.
Click to expand...
Click to collapse
It means you installed the drivers right.
Reboot your PC, try other USB port, close any unecessary apps in the background, avoid USB3.0 ports or run the flash-all.bat in administrator mode. These are the ideas that have come into my mind in this moment.
Oh by the way I was following your link.
RIght now my phone has the screen firmware update. do not unplug.. the usb connection until the process is complete....
Then follow the rest of your instructions.
Now how do I Enter your phone to Download Mode. ? Right now still with this screen "Firmware update".
bitdomo said:
It means you installed the drivers right.
Reboot your PC, try other USB port, close any unecessary apps in the background, avoid USB3.0 ports or run the flash-all.bat in administrator mode. These are the ideas that have come into my mind in this moment.
Click to expand...
Click to collapse
benzso63 said:
Oh by the way I was following your link.
RIght now my phone has the screen firmware update. do not unplug.. the usb connection until the process is complete....
Then follow the rest of your instructions.
Now how do I Enter your phone to Download Mode. ? Right now still with this screen "Firmware update".
Click to expand...
Click to collapse
When you see "Firmware update" that is the download mode. Watch the video I made. Maybe it explains everything more.
I got that part. Now I am using the LG Flash Tool, port 1 com41. I clicked the yellow arrow and screen showing it is ready. But on the phone I don't need any progress at all, it is till 0%. would it automatically run it itself ?
bitdomo said:
When you see "Firmware update" that is the download mode. Watch the video I made. Maybe it explains everything more.
Click to expand...
Click to collapse
benzso63 said:
I got that part. Now I am using the LG Flash Tool, port 1 com41. I clicked the yellow arrow and screen showing it is ready. But on the phone I don't need any progress at all, it is till 0%. would it automatically run it itself ?
Click to expand...
Click to collapse
What is shown on the PC?
Bro, now its running. I moved to usb 3.0 port. will keep you posted
Confirmed. Working Flawlessly ! OMG, you are my life saver. Really appreciate your hard work.
Man, you are the BEST !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
bitdomo said:
What is shown on the PC?
Click to expand...
Click to collapse
benzso63 said:
Bro, now its running. I moved to usb 3.0 port. will keep you posted
Confirmed. Working Flawlessly ! OMG, you are my life saver. Really appreciate your hard work.
Man, you are the BEST !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Your welcome.
You need to open a Master Class LOL. Seriously, you have no idea how frustrated when you can't get the phone to work.
bitdomo said:
Your welcome.
Click to expand...
Click to collapse
benzso63 said:
I was trying wipe everything on the phone but for some reason it saids no OS. So when it boots up, I only see the google word on the screen.
Trying to flash the stock rom, followed instruction to install adb drivers...etc then boot the phone into fastboot mode,. This is the one screen I can get so far. Looks like my pc can't detect my phone. it saids failed when running those commands...Can someone give me a hint what to do next?
All I want is to put the stock rom back in.
thx
Click to expand...
Click to collapse
if your pc cannot detect your phone , it seems you havn't install driver.
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
+1
gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
So will the tablet not boot into the bootloader ?
Thx Josh
lj50036 said:
So will the tablet not boot into the bootloader ?
Thx Josh
Click to expand...
Click to collapse
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.
gtgeek said:
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.
Click to expand...
Click to collapse
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh
lj50036 said:
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh
Click to expand...
Click to collapse
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?
gtgeek said:
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?
Click to expand...
Click to collapse
Nope there is just no way...
The chip is locked down ... :crying:
There is lots of info out there but its just info ...
No one to date has come back from where you are ....
Thx Josh