Database Info

Xoom Wifi "Failed image LNX 0x0002 / RSD mode 2"

Hey everyone. I figured id make an official thread,although a thread a few down is very similar but still quite different.
I attempted to re-lock my XOOM wifi and I got the error.
-only able to get into RSD mode 2 or Fastboot protocol
-pc will not recognize through adb or RSD 5.0
-tried various command and no luck
-Screen wont turn off unless battery dies.
- reinstalled sdk, drivers etc.
I might of missed a few details, but ive been all around the forums and have yet to see a solution for this other than send it to Motorola. Ha just curious to whether anyone could shed a little more light on this situation. Not being able to RSD or adb seems like a bad situation, even if we did have that darn sbf id still be stuck! Thanks guys!
Sent from my DROIDX using Tapatalk

Try to get the xoom back into fastboot by rebooting (vol up + power) and then immediately holding vol down + power until the fastboot screen comes up. From there try pushing system and boot .img's through fastboot. Then you should be able to reunlock from the fastboot command on your pc. There is no way that I know of to re-lock a wifi only xoom as of yet.

Yeah, my bootloader screen says that im "Starting Fastboot protocol service" but I get no response from my PC. I've never had problems with adb recognizing my xoom before this. Its like the drivers arent even compatible with the device anymore?? For craps i attempted to send some commands through adb even though it didnt recognize the device, and had no luck. ADB simply replies "waiting for device" for all of them.

try reloading your moto drivers

Make sure you aren't using a front panel port. I had thus problem for ages, XOOM is a power hog. As for the LNX failure its the result of relocking with an invalid image, don't do it.
Sent from my HTC Desire using Tapatalk

Yeah, i spent days trying to figure that one out with the front ports vs. the back ports with my droid. I could never get it to remount in RSD when flashing a .sbf.
Thanks for the heads up though. Im not sure what made me think that it would be ok. My failure to do some research always lands me in pretty much the same spot! Here.
I reloaded all the drivers ect and have been unable to get anything. My droid works great, but no xoom.

Had this exact thing happen to me today. What fixed it for me was
- boot into fastboot (Power+Vol Up then immediately hold Vol Down until you see it display the fastboot message) and push the stock boot/system images found all over this forum for your model (Wifi/3G)
Now obviously your ADB isn't seeing your device... neither was mine
- Go under Device Manager on your PC and uninstall your Motorola drivers from whatever devices are listed
- Do a fresh install of the Moto Drivers and restart your PC
- Run, 'fastboot oem lock' to allow RSD to do it's work
That's what it took for me. If that fails, unplug your Xoom from the PC and set to debug mode, then plug back in and let Windows find your drivers. Windows could take some time, and actually took me unplugging/replugging twice until it decided it found them.
RSD is a load of junk, but when it works it's like the miracle worker =P Good luck and keep your head up! These things are harder than people think to completely wreck =)

Xezuka said:
Had this exact thing happen to me today. What fixed it for me was
- boot into fastboot (Power+Vol Up then immediately hold Vol Down until you see it display the fastboot message) and push the stock boot/system images found all over this forum for your model (Wifi/3G)
Now obviously your ADB isn't seeing your device... neither was mine
- Go under Device Manager on your PC and uninstall your Motorola drivers from whatever devices are listed
- Do a fresh install of the Moto Drivers and restart your PC
- Run, 'fastboot oem lock' to allow RSD to do it's work
That's what it took for me. If that fails, unplug your Xoom from the PC and set to debug mode, then plug back in and let Windows find your drivers. Windows could take some time, and actually took me unplugging/replugging twice until it decided it found them.
RSD is a load of junk, but when it works it's like the miracle worker =P Good luck and keep your head up! These things are harder than people think to completely wreck =)
Click to expand...
Click to collapse
Just curiousity, if we can't boot our xoom, how can we enable USB debug mode?

This is the same of my problem:
http://forum.xda-developers.com/showthread.php?t=1052762

tritran18518 said:
Just curiousity, if we can't boot our xoom, how can we enable USB debug mode?
Click to expand...
Click to collapse
Sorry I guess I didn't mean to set it to Debug from the Xoom, but as in to remove it and boot into Fastboot. Then plug it back in and allow Windows to install the drivers.
I had a hard time getting it to work, but after uninstalling and reinstalling the drivers, it recognized it and allowed me to flash the SBF.
Correct me if I'm wrong here! It's what worked for me. My Xoom went down like this and I resurrected it this way. Been working flawlessly on Tiamat 1.3.1 ever since.

Sorry guys, but the condition I'm in is becoming popular lately. I'm able to get the XOOM wi/fi to show "starting fastboot protocol" but absolutley no recognition on the pc. RSD or ADB. Therefore all commands sent from the ADB simply respond with "waiting for device" and unable to flash any images onto the device. Its in a real brick mode. At least for the time being with the lack of software communication on the pc and no .sbf yet. I sent the device into motorola for repair. They said the repair would be under the warranty and free of cost. I was honest as well, telling the repp I had unlocked the device and attempted to re-lock. Thanks for all the suggestions and input guys.

follow up?
hello i am curious what happened with your returned brick? did moto replace it?
I ask because i have the exact same issue and have gone through all the suggestions.
same error, cannot get into fastboot, no adb, no RSD, nothing. tried the various vol power button combos etc. no recognition on PC at all. yes i re-installed drivers etc etc etc... i have been reading...
it seems only option is to wait on SBF or return?

Yeah the only solution would be an sbf flash. But even with that i do not know how because the RSD lite does not recognize the device either.I simply placed an order online, they sent a box the next day, sent it and got it back in two days. Extremely fast. I told the tech rep over the phone that i had unlocked the device and and then downloaded an app that starting causing for restarts and so i attempted to re-lock the device and from there it was officially a true brick. I was honest and they seem to be very understanding. Im sure they understand that the lack of support for the device is evident and we are all beta testers. SO let em know whats going on. I also let him know i was a developer, whether it mattered or not i dont know, but i was just being honest. Its all covered under warranty he said. I didnt pay a penny

OK well its good to know I am totally screwed!!! thanks for the reply...
I told the rep on the phone what I did but I don't think he had any clue what I was talking about... he asked to me to reboot with vol up, then try to boot into fastboot, but didn't once say fastboot, just said vol down, then said he would send me a shipping box.
Get it today!!

I am in this situation after trying to re-lock in order to install the 3.1 update. I tried re-installing and updating the Moto drivers, rebooting etc but I can't get my PC to recognise the device in fastboot or RSD. I am on a stock Canadian ROM (but unlocked obviously).
I have sent an email to Motorola and been honest with them. Will see what they say.

That's the thing - moto provides all the tools to relock for US ONLY! There is no official way for canadians, which makes no sense. So us canadians can unlock no problem, but cannot relock, yet US units can? Strange to me...

chaz03 said:
Yeah the only solution would be an sbf flash. But even with that i do not know how because the RSD lite does not recognize the device either.I simply placed an order online, they sent a box the next day, sent it and got it back in two days. Extremely fast. I told the tech rep over the phone that i had unlocked the device and and then downloaded an app that starting causing for restarts and so i attempted to re-lock the device and from there it was officially a true brick. I was honest and they seem to be very understanding. Im sure they understand that the lack of support for the device is evident and we are all beta testers. SO let em know whats going on. I also let him know i was a developer, whether it mattered or not i dont know, but i was just being honest. Its all covered under warranty he said. I didnt pay a penny
Click to expand...
Click to collapse
Try rsdlite 4.9 or earlier it should see it then.

I tried RSD 4.9 and no luck. I think it just doesn't work with Wi-Fi only zooms.
Sent from my Nexus S using XDA App

footboydog said:
I tried RSD 4.9 and no luck. I think it just doesn't work with Wi-Fi only zooms.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Anyone who locked the zoom back and now can't boot, try my instructions from another thread...
1) Turn the xoom on and leave it plugged into USB. 2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.

crushsuitandtie said:
Anyone who locked the zoom back and now can't boot, try my instructions from another thread...
1) Turn the xoom on and leave it plugged into USB. 2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.
Click to expand...
Click to collapse
I have just tried this and still no luck. Fastboot just sits there with the "waiting for device" message and the Xoom just boots with the "Starting RSD mode 2" message. I also tried your suggestion with rebooting into fastboot mode by holding the vol down button and that doesn't work either.
BTW I don't have a custom boot.img. I am on a stock ROM but I just had the bootloader unlocked.
Incidentally I have tried RSD lite 4.8, 4.9 and 5.0 now and none work.

[Solved]Stuck at white screen

I'm trying to fix my brother's phone. He was running one of the GB Valhallas and then one day his baseband just disappeared. Considering that my Vibrant had the same issue once when flashing ICS, I just downloaded a CWM flashable modem thinking it would solve the problem. Nothing changed and the baseband still showed nothing so I downloaded a new rom, flashed it, it booted but the baseband was still nothing. So I tried to use heimdall to flash just the modem, it gave me some weird error, so I turned the phone off to try again and then that's when it just turned on with a blank white screen. I can't seem to get it into download mode or to even boot normally. Anything I can do? Is a jig my only option? Would that even work?
Any help at all would be appreciated. Thanks

Have you tried pulling the battery, plugging it into the usb able and the usb cable into the computer, then press the power button and volume buttons at the same to to get into download mode?
If you can do that, you can use the heimdall one click and completely reflash the phone.

yep I've tried that, I've tried every combo known to man. Just keeps coming up with a white screen

Sounds water damaged
Sent from my SGH-T959V using XDA App

Nope, the little thing in the back is still white, and he hasn't dropped it in water. :/
Sent from my SGH-T959 using XDA App

When it's on & plugged into the PC via the USB cable, does the.computer recognize it? Have you tried opening ODIN to see if it recognizes it? I'm just wondering if you're getting into a download mode but you just can't tell due to the white screen.
Sent from my SGH-T959V using xda premium

stephen_w said:
When it's on & plugged into the PC via the USB cable, does the.computer recognize it? Have you tried opening ODIN to see if it recognizes it? I'm just wondering if you're getting into a download mode but you just can't tell due to the white screen.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
If not that, then make a jtag and try that. Otherwise, if it is still under warranty, call samsung and do a repair ticket for it. Don't tell them you flashed anything to it. Say it just spontaneously happened...hehehe

stephen_w said:
When it's on & plugged into the PC via the USB cable, does the.computer recognize it? Have you tried opening ODIN to see if it recognizes it? I'm just wondering if you're getting into a download mode but you just can't tell due to the white screen.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
I don't think so, I'm running Linux so I haven't tried odin, I guess I could dust off the windows partition and try it out. But when I tried flashing with heimdall it says:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to open file ""
Re-attaching kernel driver...
Then it says flash successful (obviously not), and nothing happens.
thomas.raines said:
If not that, then make a jtag and try that. Otherwise, if it is still under warranty, call samsung and do a repair ticket for it. Don't tell them you flashed anything to it. Say it just spontaneously happened...hehehe
Click to expand...
Click to collapse
Is jtag same as a jig? And no it was refurbished when he got it and that was over 6 months ago, I don't know if it's still covered under any warranty. Otherwise I would have thought the same thing

Stick with Linux vs. Windows. ODIN is a pain in the rear for the most part. I assumed you were on Windows. My bad!
What about going to grab the Android SDK, extract it, find the tools directiory under the extracted archive, and execute 'android'. that should load the AVD manager software. When that executes, only select the Platform-Tools to download. When you have it, go into the platform-tools directory (at the same level as tools), and you'll have the Android Debug Bridge (adb).
Execute: ./adb reboot download
If that comes back without error, the phone should be in download mode (even if you can't tell). If that happens, go try to re-run Heimdall for the install.

stephen_w said:
Stick with Linux vs. Windows. ODIN is a pain in the rear for the most part. I assumed you were on Windows. My bad!
What about going to grab the Android SDK, extract it, find the tools directiory under the extracted archive, and execute 'android'. that should load the AVD manager software. When that executes, only select the Platform-Tools to download. When you have it, go into the platform-tools directory (at the same level as tools), and you'll have the Android Debug Bridge (adb).
Execute: ./adb reboot download
If that comes back without error, the phone should be in download mode (even if you can't tell). If that happens, go try to re-run Heimdall for the install.
Click to expand...
Click to collapse
Tried that too. It said there was no device found. :/ Tried getting it to connect but it wouldn't work.
It's a cold day in hell though because Windows actually worked. I went into it and after like half an hour of updates ... I was able to run odin and even though the screen stayed white it actually recognized it when I did the vol +/- hold! So you had the right idea the first time lol. Don't get why it wouldn't work with heimdall though.. Thanks!!

Weird! Glad you got it working though. Please update the title of the thread with [SOLVED] at the beginning.
Thanks!
Sent from my SGH-T959V using xda premium

Need help. Phone has bad rom, can't access recovery

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.

[Q] LG P500 Bricked - No ADB, no fastboot recognition

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]:...$

[Q] Hard-Bricked, no boot. Failed during flash

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