Database Info

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.

RUU Error 171 Stuck on waiting for boot loader

As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436

What we're your steps exactly? Did you relock your bootloader

a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.

Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.

iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.

Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?

iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.

Does anybody else have some more ideas?

Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.

redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.

I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.

Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.

DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.

i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.

Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?

kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.

Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!

diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.

jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita

Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you

[Q] I accidentally everything (TWRP)

Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?

JunoZXV said:
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
Click to expand...
Click to collapse
Im having exactly the same problem, did you find a solution to this?

So far no results yet. I tried hitting the reset button on the side but all that did was lead me back to the boot screen. I read something about undoing the the hard boot using a series of override programs. But the problem is the documentation is so cluttered that I can't fathom the instructions (I'll try it again just in case.)

Bump update: So I called Asus and it turns out it's gonna cost 288$ to get the thing fixed by them. So I'm not doing that. I'm looking into other ways of recovery. I've got other multiple options I'm exploring at the moment. Like looking for a recycling program or a way to use the technology in a new way.

UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this

JunoZXV said:
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
Click to expand...
Click to collapse
Unfortunately if you can only get to APX mode and you don't have nvflash specific blobs for your device you are hard bricked...

Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.

JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
Sorry it really doesn't look good, Maybe i can corrected but the device will fallback to APX mode if the bootloader is corrupted, without a bootloader you cant install/fix a recovery and without NvFlash blobs you cant fix the bootloader. Your two options are buy a new motherboard and replace it yourself or send it in for repair with Asus

JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
As JTR says I'm pretty sure you can't fix this without replacing the hardware now. I don't think your friend really understands what APX mode is. YOu can't access the bootloader nor recovery. Without NVflash backup blobs you can't recover anything, there is no way to get your TWRP backups back on to the device and even if you could you have no working bootloader......

[Q] I need to return a broken rooted phone, and have a question before I do so...

I need to return a broken rooted phone, and have a question before I do so...
the phone has been rooted, and has the HellFire ROM installed. The phone currently won't boot up completely. It gets to the boot animation, and just loops forever. I first thought this was a battery issue, as I'm unable to even do a factory reset or get into download mode. After ordering a new battery, I found this wasn't the issue, and now need to send it back to tmobile.
now my question...
if I send it back, will they be able to tell if it's rooted, since it won't boot up, or is there a way I can make it impossible for them to find out? I've heard I can cook it in the microwave for a few seconds, but I'm not trying to blow anything up. LOL
any assistance would be greatly appreciated.

SevnSins said:
I need to return a broken rooted phone, and have a question before I do so...
the phone has been rooted, and has the HellFire ROM installed. The phone currently won't boot up completely. It gets to the boot animation, and just loops forever. I first thought this was a battery issue, as I'm unable to even do a factory reset or get into download mode. After ordering a new battery, I found this wasn't the issue, and now need to send it back to tmobile.
now my question...
if I send it back, will they be able to tell if it's rooted, since it won't boot up, or is there a way I can make it impossible for them to find out? I've heard I can cook it in the microwave for a few seconds, but I'm not trying to blow anything up. LOL
any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Are you sure that you can't key combo into recovery?
If you have the time, make a jig to force your phone into download mode. Then you can use odin to flash stock.
If you are wanting to send it in for warranty because you can't accomplish the tasks above.
Then you have adb access on then run the tool in my signature and use the unroot command.
(It will take a while for adb to start up at the bootscreen but it does startup.)
Just make sure that you have drivers properly installed.
They shouldn't be able to tell the difference.

Lgrootnoob said:
Are you sure that you can't key combo into recovery?
If you have the time, make a jig to force your phone into download mode. Then you can use odin to flash stock.
If you are wanting to send it in for warranty because you can't accomplish the tasks above.
Then you have adb access on then run the tool in my signature and use the unroot command.
(It will take a while for adb to start up at the bootscreen but it does startup.)
Just make sure that you have drivers properly installed.
They shouldn't be able to tell the difference.
Click to expand...
Click to collapse
No, I've tried booting into recovery & download mode both several times, and they both are unsuccessful. When trying recovery, it displays the blue recovery starting text, but never goes into recovery. It just skips to the boot animation, and loops. When trying download mode, as soon as it asks to press volume up or down, the device powers off. it doesn't even give me the time to click anything.
Not sure what you mean by "make a jig to force download mode", but I'll give your second suggestion a try.
thanks

SevnSins said:
No, I've tried booting into recovery & download mode both several times, and they both are unsuccessful. When trying recovery, it displays the blue recovery starting text, but never goes into recovery. It just skips to the boot animation, and loops. When trying download mode, as soon as it asks to press volume up or down, the device powers off. it doesn't even give me the time to click anything.
Not sure what you mean by "make a jig to force download mode", but I'll give your second suggestion a try.
thanks
Click to expand...
Click to collapse
i downloaded your script, placed on a flash drive, and I'm getting the attached errors.

SevnSins said:
i downloaded your script, placed on a flash drive, and I'm getting the attached errors.
Click to expand...
Click to collapse
Which version of windows?
I have tested this script on four different machines,
It seems that your path variable is most likely messed up.(Unless you manage to find issues with my code which is appreciated too )
If you like then you can post the output of the path command while running adbClient and I can help you fix that problem.
Otherwise use the instadb command to fix this if you don't want to fix your potential path variable problem.
(instadb will install adb to the system)
Back to the topic at hand, Jig
There is a link to making a usb jig. (It is a VERY helpful link, as long as you take the time to read everything [The Xda way ] )
That can get you into download mode.
You can either go find a usb jig online and buy it, or you can make your own.
I also found this at the bottom of the page:
darkamikaze - "I got this from sparkfun. While it's not necessarily buying a complete jig, it saves the hassle of cutting a perfectly working usb cord
https://www.sparkfun.com/products/10031 "
I'm interested in the path thing though, so please do post the output of the path command being used inside the tool.

Lgrootnoob said:
Which version of windows?
I have tested this script on four different machines,
It seems that your path variable is most likely messed up.(Unless you manage to find issues with my code which is appreciated too )
If you like then you can post the output of the path command while running adbClient and I can help you fix that problem.
Otherwise use the instadb command to fix this if you don't want to fix your potential path variable problem.
(instadb will install adb to the system)
Back to the topic at hand, Jig
There is a link to making a usb jig. (It is a VERY helpful link, as long as you take the time to read everything [The Xda way ] )
That can get you into download mode.
You can either go find a usb jig online and buy it, or you can make your own.
I also found this at the bottom of the page:
darkamikaze - "I got this from sparkfun. While it's not necessarily buying a complete jig, it saves the hassle of cutting a perfectly working usb cord
https://www.sparkfun.com/products/10031 "
I'm interested in the path thing though, so please do post the output of the path command being used inside the tool.
Click to expand...
Click to collapse
I'm using Win7
I'm not as familiar with adb as I should be, as I haven't had to use it much through my experiences, so I don't really know my way around it that well.
instadb is asking for username & password info, and I don't know what goes in there.
I don't have a soldering iron, so I'll likely need to buy one it looks like.
I've attached the path output you requested.
thanks for your help

SevnSins said:
I'm using Win7
I'm not as familiar with adb as I should be, as I haven't had to use it much through my experiences, so I don't really know my way around it that well.
instadb is asking for username & password info, and I don't know what goes in there.
I don't have a soldering iron, so I'll likely need to buy one it looks like.
I've attached the path output you requested.
thanks for your help
Click to expand...
Click to collapse
Thanks for the path info.
If you want to build it then you can buy a soldering iron, but if you manage to buy an already built jig it might be cheaper and require less time. ey
instadb requires the username of an admin account on your machine and the password for that account. (It elevates user permissions then copies binaries to the system32 folder)
You can do this manually by copying the dlls for adb from the bin folder and the adb and fastboot executables from the bin folder into system32.
After that you shouldn't receive anymore errors.
Thanks for the info, apparently nothing is wrong with the path variable. (Whats weird is the "F:\-" in the photo you attached it should normally be drive letter:\path to adb , F:\bin in a variable)
Try my tool on a local drive. (Its finnicky sometimes )

Lgrootnoob said:
Thanks for the path info.
If you want to build it then you can buy a soldering iron, but if you manage to buy an already built jig it might be cheaper and require less time. ey
instadb requires the username of an admin account on your machine and the password for that account. (It elevates user permissions then copies binaries to the system32 folder)
You can do this manually by copying the dlls for adb from the bin folder and the adb and fastboot executables from the bin folder into system32.
After that you shouldn't receive anymore errors.
Thanks for the info, apparently nothing is wrong with the path variable. (Whats weird is the "F:\-" in the photo you attached it should normally be drive letter:\path to adb , F:\bin in a variable)
Try my tool on a local drive. (Its finnicky sometimes )
Click to expand...
Click to collapse
ok, looks like the script is working now, but I'm getting a "device unauthorized" error. The device is connected, and has the boot animation looping.
i also tried to reboot into recovery from your script, and get the same "device unauthorized" error.
screenshot attached.

SevnSins said:
ok, looks like the script is working now, but I'm getting a "device unauthorized" error. The device is connected, and has the boot animation looping.
i also tried to reboot into recovery from your script, and get the same "device unauthorized" error.
screenshot attached.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2401452
Its impossible to use adb at this point. (Never say never: Has adb worked before?)
You have a samsung phone right?
Your phone would have to be working to accept a key on screen for adb access.
The only thing now is the usb jig.

Lgrootnoob said:
http://forum.xda-developers.com/showthread.php?t=2401452
Its impossible to use adb at this point. (Never say never: Has adb worked before?)
You have a samsung phone right?
Your phone would have to be working to accept a key on screen for adb access.
The only thing now is the usb jig.
Click to expand...
Click to collapse
I do have a samsung phone (Galaxy S3), but I don't recall if I ever used adb with this phone. I know I've used it a few times in the past, but that could have been on my G1 & G2.
think I'm just going to put it in the microwave like I used to do my playstations. LOL! I need to get a working phone, and waiting for a jig to ship is going to take a few days I'm sure.
thanks again for all your help

SevnSins said:
I do have a samsung phone (Galaxy S3), but I don't recall if I ever used adb with this phone. I know I've used it a few times in the past, but that could have been on my G1 & G2.
think I'm just going to put it in the microwave like I used to do my playstations. LOL! I need to get a working phone, and waiting for a jig to ship is going to take a few days I'm sure.
thanks again for all your help
Click to expand...
Click to collapse
Well seems like a repair would leave you with the jig as the only option.
If your house burns down then I got your back there too.
You could just come chill with me.
Just make sure to post pics of your microwaved phone. (Or a video :laugh

Lgrootnoob said:
Well seems like a repair would leave you with the jig as the only option.
If your house burns down then I got your back there too.
You could just come chill with me.
Just make sure to post pics of your microwaved phone. (Or a video :laugh
Click to expand...
Click to collapse
well... where wasn't a fire, but I got a pretty cool spark. although; it still didn't "kill it" all the way. it's still try to boot up. I just decided to send it in, if they charge me for it, I'll just pay it. my job is taking over my phone bill anyways, so I shouldn't need to worry about it.
thank again for your help :good:

Softbricked my nexus 5? Any help?

So i'm not super competent in adb and what not, but just competent to use wuggs toolkit. I went to google's website to download lollipop 5.0 for my nexus 5. Then i set the phone back to stock, flash 5.0 and its running well. Then i go back in to settings, developer options, and to root my nexus 5 and install TWRP on it through wuggs. Now it has twrp, but will not boot up past the google name with the unlock. I only have the fastboot page and TWRP. The big kicker here is that my pc says does not recognize device and it flickers back and forth with connection every two seconds to my PC. When i go into device manager it shows android device though. So well hey i figure since i have a softbricked nexus i'll just click the button for it and reset. Well it wont do it, it pulls up fastboot.exe goes through a few commands, some saying it failed then it stops and windows tells me to close fastboot.exe
Any help from the very respected XDA?

oh, gawd.. fastbooting a factory img would have been so much faster. sorry, toolkit, i cant help you with it.

hayden55 said:
So i'm not super competent in adb
Click to expand...
Click to collapse
There's your answer right there. That's how ppl like Op brick their devices everyday

Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.

jayRokk said:
Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.
Click to expand...
Click to collapse
aww but i really wanted a hand hold.

hayden55 said:
aww but i really wanted a hand hold.
Click to expand...
Click to collapse
here is an extra long :highfive: for your hand holding

chapelfreak said:
here is an extra long :highfive: for your hand holding
Click to expand...
Click to collapse
Hey thanks bud! Problem was it couldnt connect to the computer for more than 5 seconds...
SOO.... i messed with mounting an OTG jump drive and it had my old TWRP back with android 4.4.4. IT Worked!
p.s. i tried just mounting system data etc... the turn on mtp connection button and it Would show up better than just plugging in but couldnt download anything big. and no adb connection

dicecuber said:
There's your answer right there. That's how ppl like Op brick their devices everyday
Click to expand...
Click to collapse
i do not need your input if you aren't going to contribute to the problem just antagonize the op

Current problem at hand: phone now will only connect to pc for 5 seconds at a time. What could do this and how do I reflash to normal?

Still using toolkits?

hayden55 said:
i do not need your input if you aren't going to contribute to the problem just antagonize the op
Click to expand...
Click to collapse
It's a suggestion

Disclaimer: I use OS X/Terminal to fix these things normally and honestly found that after the initial learning curve, it's easier than using Windows or Wugfresh. I'm not a developer, just a hobbyist user.
Make sure you're using an OEM cable to connect to the computer if you're getting dropouts. Also, attempt to uninstall and reinstall OEM drivers (I believe Wugfresh has instructions on how to do this) for Windows.
If you have confirmed that you have TWRP 2.8.1.0 installed, try to boot to TWRP --> ADB Sideload. Connect phone to computer, open Terminal/Console and type the command 'adb devices' (without the apostrophes. I haven't used Windows since I stop using Wugfresh, so the command probably differs). If the device can be seen through this, you should be able to return to the bootloader and start issuing fastboot commands to flash the image.
Let me know how I can help!