Develop Bugs

Help - Am I Bricked - Can Get into Recovery

I'm a bit of a NOOB, so bear with my terminology. My phone was rooted and Nand unlocked (S=off), running Fresh 3.4. It will not accept calls so I have to take it to Sprint. I ran the latest RUU to get it unrooted, but I could not use Titanium Backup to restore my apps. I ran Universal AutoRoot.zip http://forum.xda-developers.com/showthread.php?t=838448 and went through what seemed to be the complete process. At the end I was left with the bootloader menu to boot into the recovery but my EVO will not go into recovery. When I try I get I get a phone with a red triangle. I have tried everything I know (I'm a bit of a NOOB), and I cannot get to recovery or Nandroid. I did a Nandroid Backup but can't get to it. My phone no longer communicates with my computer. I have just moved and need my phone to set up appointments. Please help, I'm desperate. I have posted this to multiple forums.

jminor4326 said:
I'm a bit of a NOOB, so bear with my terminology. My phone was rooted and Nand unlocked (S=off), running Fresh 3.4. It will not accept calls so I have to take it to Sprint. I ran the latest RUU to get it unrooted, but I could not use Titanium Backup to restore my apps. I ran Universal AutoRoot.zip http://forum.xda-developers.com/showthread.php?t=838448 and went through what seemed to be the complete process. At the end I was left with the bootloader menu to boot into the recovery but my EVO will not go into recovery. When I try I get I get a phone with a red triangle. I have tried everything I know (I'm a bit of a NOOB), and I cannot get to recovery or Nandroid. I did a Nandroid Backup but can't get to it. My phone no longer communicates with my computer. I have just moved and need my phone to set up appointments. Please help, I'm desperate. I have posted this to multiple forums.
Click to expand...
Click to collapse
If you ran the RUU and unrooted you WILL NOT be able to do a nandroid restore or be able to go into recovery. Those are things that are only available with rooting.

so how can I get my phone operational, rooted or unrooted?

Run the RUU again. That should bring back to a fully operational state. You won't be rooted though but at least it will work and you can bring it in to Sprint. Just make sure that the RUU you run is the correct one for your software version.

my phone does not communicate with my computer so I can't run the RUU exe. There must be a way to unlock the phone and access to the Nandroid or at least allow the phone to communicate with the computer.

jminor4326 said:
my phone does not communicate with my computer so I can't run the RUU exe. There must be a way to unlock the phone and access to the Nandroid or at least allow the phone to communicate with the computer.
Click to expand...
Click to collapse
Put your phone in fastboot and see if your computer sees it. Do you have the sdk setup by any chance?

jminor4326 said:
my phone does not communicate with my computer so I can't run the RUU exe. There must be a way to unlock the phone and access to the Nandroid or at least allow the phone to communicate with the computer.
Click to expand...
Click to collapse
There is no way to get the phone unlocked unless you ROOT. And as far as getting it to communicate with the computer. Get into your bootloader and use the USB option, I don't remember what its called but I believe it is the top option that should get you connected to your computer then the RUU should run successfully.

the computer does not see the phone in any mode (that I know of). I know someone who does have access to sdk. what needs to be done?

jminor4326 said:
the computer does not see the phone in any mode (that I know of). I know someone who does have access to sdk. what needs to be done?
Click to expand...
Click to collapse
If your bootloader runs then that should work, I have done it a million times when I borked my phone doing stupid stuff lol.

It was not clear the computer saw the phone in USB mode - I tried. Are you saying use the USB option. then what - use Sdk commands?

how do I know the Bootloader is working, or capable of doing the trick?. what signs. The computer still can't see the phone

jminor4326 said:
It was not clear the computer saw the phone in USB mode - I tried. Are you saying use the USB option. then what - use Sdk commands?
Click to expand...
Click to collapse
Nope, you don't have to use any commands at all. Just run the RUU you want from your computer. The RUU as in the script that runs from your computer.

Try fastboot, the top option. You on windows?

AdamHart612 said:
Try fastboot, the top option. You on windows?
Click to expand...
Click to collapse
There ya go, thats the option I was referring to. Sorry I was to lazy to boot into bootloader and see what it was actually called.

Once in fastboot you should see drivers install if its your first time, otherwise (if you can) cd to your android-sdk-windows/tools folder and run "fastboot devices". Your phone should show up in the output. If not then its still not seeing your phone.
If your phone is being recognized then run the RUU for your software version or higher. Sometimes running the RUU takes a few tries.

AWESOME! Thanks Yellowcard8992 and MetalHead. The RUU is running. I started from Bootloader and clicked the exe. Thanks a million! That was my first issue. How do I, or what program or app or whatever do I use, to root my phone 'enough' to use Titanium Backup. This is an invaluable app, when one has Root. I still need to take it back to sprint, and I don't want these Root / S-off issues again.

AdamHart612 said:
Once in fastboot you should see drivers install if its your first time, otherwise (if you can) cd to your android-sdk-windows/tools folder and run "fastboot devices". Your phone should show up in the output. If not then its still not seeing your phone.
If your phone is being recognized then run the RUU for your software version or higher. Sometimes running the RUU takes a few tries.
Click to expand...
Click to collapse
Follow what he is saying. And another thing to add is that you may need to restart your computer in order to get it to recognize your phone too, as well under fastboot to reboot the bootloader. These have both gave me the ability to run the RUU after doing that. And if you downloaded a folder that said it was the ruu thats not what we are talking about, you need to download the file we are referring to here...
http://shipped-roms.com/index.php?category=android&model=Supersonic
As for your question about how to be able to use titanium, your going to have to use a full root method with S-OFF. There isn't really a partial way to do it, so if your using Titanium, then you have to be rooted unfortunately.

Broncos - which is the most up-to-date RUU to use as far as Sprint is concerned? The link Shipped ROMS you provided shows lots of RUUs, I thought .651.5 was newest, but I see a .651.6. There are several permuatations... which one. What about Rooting. Is there a 'good' 'easy' way? Or is there a program like Titanium that doesn't need root. Can you suggest a method? thanks again for being so prompt in your responses. I really feel lots better.

jminor4326 said:
Broncos - which is the most up-to-date RUU to use as far as Sprint is concerned? The link Shipped ROMS you provided shows lots of RUUs, I thought .651.5 was newest, but I see a .651.6. There are several permuatations... which one. What about Rooting. Is there a 'good' 'easy' way? Or is there a program like Titanium that doesn't need root. Can you suggest a method? thanks again for being so prompt in your responses. I really feel lots better.
Click to expand...
Click to collapse
3.30 is the newest.
Root is necessary for backing up protected apps, etc. What hboot version are you? That currently dictates your rooting options.

jminor4326 said:
Broncos - which is the most up-to-date RUU to use as far as Sprint is concerned? The link Shipped ROMS you provided shows lots of RUUs, I thought .651.5 was newest, but I see a .651.6. There are several permuatations... which one. What about Rooting. Is there a 'good' 'easy' way? Or is there a program like Titanium that doesn't need root. Can you suggest a method? thanks again for being so prompt in your responses. I really feel lots better.
Click to expand...
Click to collapse
Your fine, there for awhile I thought that you were gonna have a heart attack. Just remember when your messing with your phone to ALWAYS take deep breaths. As far as the RUU goes you should be just fine running this one: RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe.
And as far as Titanium I'm not sure if there is one, it all depends on what you are trying to backup. What do you use it for?

[Q] noob - 2.20?

How do I know if my phone is 2.20?
I can't seem to find anywhere in my "about" section anything that has these numbers... or even 1.85...
*edit* Found it! I'm on 3.18. Now with that being said, I have been searching and searching on how to root for 3.18. I have found several threads where a user will ask if it's do able yet and they get flamed with "it's been asked a thousand times, search!' or "look in the forums"... Well I am a complete noob and I can't find it... please point me in the right direction??????

Your first wrong decision was to put this thread in the general section.
Now I'll give you some clues what to do, and you shouldn't ask anything else as it will be really easy for you to google it and find out all the details:
1) Unlock your phone at htcdev.com (careful, it will wipe out all your data and there's no another way to do it);
2) Flash a clockworkmod recovery for One X via fastboot flash recovery filename.img;
3) Flash a supersu package via recovery;
4) Enjoy your root privileges.
I underlined keywords to look for in google.

Adiost said:
Your first wrong decision was to put this thread in the general section.
Now I'll give you some clues what to do, and you shouldn't ask anything else as it will be really easy for you to google it and find out all the details:
1) Unlock your phone at htcdev.com (careful, it will wipe out all your data and there's no another way to do it);
2) Flash a clockworkmod recovery for One X via fastboot flash recovery filename.img;
3) Flash a supersu package via recovery;
4) Enjoy your root privileges.
I underlined keywords to look for in google.
Click to expand...
Click to collapse
Thank you x1000!!! I got so overwhelmed very quickly with all the "experts" out there and I could not find the right material. The two techniques I tried failed and I didn't want to brick my phone because I didn't know what I was doing...
Thank you again!!!!

bugzeem6s said:
Thank you x1000!!! I got so overwhelmed very quickly with all the "experts" out there and I could not find the right material. The two techniques I tried failed and I didn't want to brick my phone because I didn't know what I was doing...
Thank you again!!!!
Click to expand...
Click to collapse
It's pretty hard to brick a hox, There is almost always a solution, read carefully but don't worry too much

I'm really starting to think this isn't meant to be... When I go to install Android SDK on my computer it says to extract the file straight to C:\ and then I "should" have a folder named C:\Android, well, I don't. Kept re trying and re trying, nothing.... Then I go to ask a question and I get the infamous I cannot page because I have less than 10 posts... Think I am going to give it up... Oh well...
windows 8...

bugzeem6s said:
I'm really starting to think this isn't meant to be... When I go to install Android SDK on my computer it says to extract the file straight to C:\ and then I "should" have a folder named C:\Android, well, I don't. Kept re trying and re trying, nothing.... Then I go to ask a question and I get the infamous I cannot page because I have less than 10 posts... Think I am going to give it up... Oh well...
windows 8...
Click to expand...
Click to collapse
I was pretty certain uderlining fastboot.
http://www.4shared.com/zip/j9DPgqkY/FastbootADB.html
This is all the tools you'll ever need on your PC. There are two of them, including fastboot.exe. No need to install the whole Android SDK.

error code 160 MID not allowed
i also got error code 141 could not generate result

another thing... my phone is 4 days old...

bugzeem6s said:
another thing... my phone is 4 days old...
Click to expand...
Click to collapse
https://www.google.de/url?sa=t&rct=...=0H-OBcV12hM_MACsirhxXQ&bvm=bv.50500085,d.ZWU
use this tutorial man..you could try to search on your own...it helps often you know?
http://forum.xda-developers.com/showthread.php?t=1583801 or this here

Try searching for the all in one toolkit for Hox.
Does the trick without the headache.
Sent from my HTC One X using xda app-developers app

I've tried the all in one, i've tried many tutorials, i've searched and searched and searched and searched... Nothing but circles... I'm thinking it's the phone...

did both of the windows 8 tutorial and... NOTHING!!! so d**n pissed right now!!

http://forum.xda-developers.com/showthread.php?t=2069904
[HOW TO] Unlock bootloader, Root, Flash Custom ROM, Flash Kernel And More!
Don't forget to enable USB debugging in your current ROM or else fastboot will not work. And install HTC drivers, but I assume you already did that.
Sent from my HTC One X using xda app-developers app

please delete this thread

bugzeem6s said:
please delete this thread
Click to expand...
Click to collapse
Did you succeed?
Sent from my HTC One X using xda app-developers app

nope. not wasting anymore time on it... error after error.

Problem in Mobile (htc ADR6350)

I have a problem in Mobile (htc ADR6350), or what is called (HTC Incredible 2) almost
When you turn it on and then up to the slogan (HTC) and then restart frequently.
I'm doing tried scanning manufacturers (FACTORY RESET) or repair (recovery) of (HBOOT)
But as soon as you press the power button to select one of them the restart and so
Knowing There is a full backup
I hope you help me resolve this problem .... appreciate your cooperation and apologize for the bad translation.
system info:
vivo_w XB ENG S-OFF RL
HBOOT-0.96.200 (PG3210***)
RADIO-1.09.01.0722
OS Ver.-1.34.605.4

yshai1 said:
I have a problem in Mobile (htc ADR6350), or what is called (HTC Incredible 2) almost
When you turn it on and then up to the slogan (HTC) and then restart frequently.
I'm doing tried scanning manufacturers (FACTORY RESET) or repair (recovery) of (HBOOT)
But as soon as you press the power button to select one of them the restart and so
Knowing There is a full backup
I hope you help me resolve this problem .... appreciate your cooperation and apologize for the bad translation.
system info:
vivo_w XB ENG S-OFF RL
HBOOT-0.96.200 (PG3210***)
RADIO-1.09.01.0722
OS Ver.-1.34.605.4
Click to expand...
Click to collapse
Let me be the first to say this.
What?
Sent from my ADR6350 using xda app-developers app

FordNate said:
Let me be the first to say this.
What? [/QUOT
Okay, I agreed ... but, let's try to be helpful to OP whose native language is obviously not English.
I believed s/he is trying to say the device is doing an endless boot-looping and cannot get into Recovery - looking for help from us here.
OP, what carrier or home system (CDMA or GSM) are you using the phone on? Did it worked before? What were you doing with the device before this happened - trying to flash a new/different ROM, kernel or radio, etc. ??
You will need to learn and use ADB, read the sticky in this Forum and/or get someone familiar to help you with it. In the unlikely situation of being on Verizonwireless CDMA system, you can flash the RUU file and restore it to stock (unrooted) and start over - after getting it activated again & restore all the factory settings.
Click to expand...
Click to collapse

thanks Letitride,,,,help my
Letitride said:
FordNate said:
Let me be the first to say this.
What? [/QUOT
Okay, I agreed ... but, let's try to be helpful to OP whose native language is obviously not English.
I believed s/he is trying to say the device is doing an endless boot-looping and cannot get into Recovery - looking for help from us here.
OP, what carrier or home system (CDMA or GSM) are you using the phone on? Did it worked before? What were you doing with the device before this happened - trying to flash a new/different ROM, kernel or radio, etc. ??
You will need to learn and use ADB, read the sticky in this Forum and/or get someone familiar to help you with it. In the unlikely situation of being on Verizonwireless CDMA system, you can flash the RUU file and restore it to stock (unrooted) and start over - after getting it activated again & restore all the factory settings.
Click to expand...
Click to collapse
thanks Letitride
* yes....the device is doing an endless boot-looping.
* using carrier or home system (CDMA).
* What do you mean (ADB)?
* How do (flash the RUU file and restore it to stock (unrooted) and start over - after getting it activated again & restore all the factory settings.)
and Where did it get them?
please help my
Click to expand...
Click to collapse

yshai1 said:
Letitride said:
thanks Letitride
* yes....the device is doing an endless boot-looping.
* using carrier or home system (CDMA).
* What do you mean (ADB)?
* How do (flash the RUU file and restore it to stock (unrooted) and start over - after getting it activated again & restore all the factory settings.)
and Where did it get them?
Click to expand...
Click to collapse
It sounded like you are a complete newcomer to all this and you are going to need extra help to avoid bricking your device completely into a useless paperweight.
ADB is Android Debug Bridge, see the "Wiki" section above here on XDA and read about it, you can also google for details & how to.
Please answer, was your DI2 working before? Is (was) it activated on Verizonwireless? Was it working before this endless boot-looping?
To give you a very general idea of what is involved here, and it isn't simple but most of us learned it, sometimes - the hard way !! So be careful, very careful on what you are about to do !! If you are not confident or comfortable, don't even attempt to try & do it.
http://forum.xda-developers.com/showthread.php?t=2357721
http://forum.xda-developers.com/showthread.php?t=1876073
Do you have the HTC device drivers loaded & working on your PC? Does it recognize the DI2 when it is connected?
The links to the RUU might be broken but please answer the questions above and I will try to offer some suggestions on how best to proceed.
If all of these are "foreign" to you and you are completely lost, you need expert help instead of trying a DIY (Do It Yourself) ...
Click to expand...
Click to collapse

thanks mr. Letitride,,,,help my
Letitride said:
yshai1 said:
It sounded like you are a complete newcomer to all this and you are going to need extra help to avoid bricking your device completely into a useless paperweight.
ADB is Android Debug Bridge, see the "Wiki" section above here on XDA and read about it, you can also google for details & how to.
Please answer, was your DI2 working before? Is (was) it activated on Verizonwireless? Was it working before this endless boot-looping?
To give you a very general idea of what is involved here, and it isn't simple but most of us learned it, sometimes - the hard way !! So be careful, very careful on what you are about to do !! If you are not confident or comfortable, don't even attempt to try & do it.
http://forum.xda-developers.com/showthread.php?t=2357721
http://forum.xda-developers.com/showthread.php?t=1876073
Do you have the HTC device drivers loaded & working on your PC? Does it recognize the DI2 when it is connected?
The links to the RUU might be broken but please answer the questions above and I will try to offer some suggestions on how best to proceed.
If all of these are "foreign" to you and you are completely lost, you need expert help instead of trying a DIY (Do It Yourself) ...
Click to expand...
Click to collapse
I apologize for the delay ... Because of the circumstances
These answers your questions:
was your DI2 working before?
yes
Is (was) it activated on Verizonwireless?
yes
Was it working before this endless boot-looping?
yes
Do you have the HTC device drivers loaded & working on your PC?
yes
Does it recognize the DI2 when it is connected?
yes
Click to expand...
Click to collapse

yshai1 said:
... was your DI2 working before? yes
Is (was) it activated on Verizonwireless? yes
Was it working before this endless boot-looping? yes
Do you have the HTC device drivers loaded & working on your PC? yes
Does it recognize the DI2 when it is connected? yes
Click to expand...
Click to collapse
Here is a dropbox link to the OEM/stock RUU file released from VZW that I've saved & restored to dropbox from my collection - https://dl.dropboxusercontent.com/u....01.1111_NV_VZW1.92_release_225831_signed.exe
Please download this to your PC (linked file will be removed after 72 hours) - and prepare your DI2 by making sure it's 75% to 100% charged first. Make backup copies of your mSD card to a safe location, just in case.
Next, power on your DI2 and connect it to your PC via the micro-USB cable, then run or launch this RUU file. Read the warnings and click thru to run it - it will flash & restore your phone to factory fresh, stock condition and result in your DI2 being UN-rooted again. However, it will not change or affect SIM unlocking (if it was already done) - and, the process should take about 10 minutes or so, and when it is finished, power down & reboot the smartphone - and it should take you to the initial Startup/Setup Screen menu - follow it and get it activated again, including downloading the latest PRL from OTA.
When it is finished, you will need to follow the steps & guides to root it, install a custom recovery and SU, etc. Then, you can install your choice of custom ROM and/or kernet, etc.
The above approach is more fool-proof than using ADB to flash a different bootloader and to try to restore it to working conditions etc. with the tradeoff of losing root, which can be easily reversed again.
Let me know if you decided to go ahead and the results/outcome, etc.
Option #2 - If, however, you do not want to lose root and you can boot your device into Custom Recovery (CWM - not stock recovery) - use this link here - http://forum.xda-developers.com/showthread.php?t=1599767
Follow it & download the "Stock" PG32IMG from CS, copy it to your mSD card, boot into Recovery & flash the zip file - it SHOULD get your device backup and running again (it might NOT, I haven't done this in a while) and as long as you don't need to mess with the bootloader again (which might be corrupted or damaged, etc.) - you are good to go. Once it's up & running, you can restore & setup your APPS again - and/or install other custom ROM of your own choice, at your own risk, of course. But, make a CWM Backup first before doing so in between.
Good Luck & Regards !

i am havig troble with my HTc ADR350
my phone keep shutting down how do i resolve this?

[Q] Bricked T999L Failed Bootloader update

Hi! I need some serious help. I accidentally bricked my phone while updating the Bootloader.
It's a Samsung Galaxy S3 SGH-T999L (T-Mobile, but it works with my Vodaphone SIM)
Absolutely nothing on the screen, no boot, no recovery mode (just installed CWM), no download mode. Just a red LED when plugged in via USB.
Device Manager shows this: "QHSUSB_DLOAD"
I live in Egypt so there's no such thing as 'insurance' or 'warranty'.
I tried the instructions here: http://forum.xda-developers.com/showthread.php?t=2439367
Didn't work.
Is this the end? Or is there yet hope for it?

Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I just installed the CWM custom recovery via Android Toolkit, and was preparing to flash Cyanogen. It said that an S3 needed a Bootloader update to install Cyanogen versions greater than 10.1, So I followed the links and I think I accidentally flashed the Bootloader for SGH-T999 (not the T999L).
CWM said it succeeded, rebooted the phone (did not fix root when it asked), and it just never turned on since (it's been a while)

P.s: Idk if this even matters when its as deep as the Bootloader, but the phone had been rooted for months before.
Oh, and I found this and am downloading the latest T999L in case I need it if ODIN can help: http://forum.xda-developers.com/showthread.php?t=2439367
And from yet more Google I found these drivers, but it won't let me post outside links
But Device Manager says "Driver is not intended for this platform."
That's all I got so far, will keep looking for a good driver and check this thread as often as I can

This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.

Kygies27 said:
This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.
Click to expand...
Click to collapse
YAY! Found working drivers here: http://forum.xda-developers.com/showthread.php?t=1536354&page=4
By: richardlibeau
ATTACHED FILES
File Type: zip QHSUSB_Drivers_(x64).zip - [Click for QR Code] (72.3 KB, 568 views)
File Type: rar qhsusb_dload_Drivers.rar - [Click for QR Code] (56.0 KB, 584 views)

More Google (Where is everybody?)
Found this: http://forum.gsmhosting.com/vbb/f824/karbonn-a9-dead-qualcomm-hs-usb-qdloader-9008-how-fix-1740061/
It seems if I can just find the corresponding hex files, etc, this could work.
Or I could somehow reprogram my CPU and make things even worse...
I'm really stuck now.
P.s: I've ofc by now seen nearly everyone go for a JTAG repair. I will check the shops around here when they open, but I don't know if they can do anything about it.

Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah, shops open soon so hopefully I can see what can be done.
I figured not to bother with the qualcomm tools, messing with things I didn't quite understand was how I got in this trouble in the first place.
But just to clarify something, the Android Toolkit wasn't what bricked it, I tried to install the firmware from a .zip on my SDcard viz CWM recovery, but it was the wrong one (I was so damn sure I was T999, not T999L).
Thank you guys for all the help, I'll post if the guy fixes it!

I know, I only mentioned it because you mentioned using it. Just warning you for the future is all.
Good luck!

[Q] Can I flash a new bootloader using recovery (twrp)?

Can I flash a new bootloader using recovery (twrp)? (flashed plenty of ROMs and Kernels wasn't sure if the steps are the same for a bootloader)
So if I plug my rooted Nexus 7(2013) in to any usb cable on any computer, it is just not detected(assuming usb port is dead at this point, only charges), Cannot even get adbd wifi to start and listen on port 5555 went through every possible scenario.( basically tried everything you can will throw at me, (MTP/PTP, usb debugging on/off, new cables, new computers, remove every possible android driver and re-install)
I saw one post where someone seemed to have a similar issue but was able to update the bootloader and his problem was solved!
Now I am not sure how he did it since I can't seem to find any good info on updating the bootloader directly from say TWRP I have no other access into the device remotely or via USB

kernelsandirs said:
Can I flash a new bootloader using recovery (twrp)? (flashed plenty of ROMs and Kernels wasn't sure if the steps are the same for a bootloader)
So if I plug my rooted Nexus 7(2013) in to any usb cable on any computer, it is just not detected(assuming usb port is dead at this point, only charges), Cannot even get adbd wifi to start and listen on port 5555 went through every possible scenario.( basically tried everything you can will throw at me, (MTP/PTP, usb debugging on/off, new cables, new computers, remove every possible android driver and re-install)
I saw one post where someone seemed to have a similar issue but was able to update the bootloader and his problem was solved!
Now I am not sure how he did it since I can't seem to find any good info on updating the bootloader directly from say TWRP I have no other access into the device remotely or via USB
Click to expand...
Click to collapse
Yeah it's possible, I did it for the Nexus 4 before. Usually the bootloader update files are found within the OTA zip updates. Usually the bootloader is composed of multiple files, not just one. You can take those files and put them in a flashable zip and make sure the script flash the files to the correct partition of the device, all the info are in the updater-script file in the zip.
It look like this is the last OTA update for the N7 that have the bootloader files: http://android.clients.google.com/p....signed-razor-KTU84L-from-KOT49H.df43279b.zip
So you can use make a flashable zip for those bootloader files or I can do it later.
I guess a smarter person would be able to dump these partitions from their device, maybe just by using "dd" command while in recovery's ADB.

I previously flashed a pre-rooted 4.4.4 OTA Stock ROM which is what I have been running ever since.
I really don't know if, or why the bootloader would affect my ability to use the USB port or not, but I guess I just had some hope based on one other post that seemed to work with.
I am not sure how to make a flashable zip from an existing ROM image, only flashable zips I made came from Titanium backup producing the flashable files for me
eksasol said:
Yeah it's possible, I did it for the Nexus 4 before. Usually the bootloader update files are found within the OTA zip updates. Usually the bootloader is composed of multiple files, not just one. You can take those files and put them in a flashable zip and make sure the script is flash it to the correct partition of the device, all these infos are usually found in the official OTA zip. The problem is not all OTA zip have bootloader files, just the one that specifically update it.
It look like this is the last OTA update for the N7 that have the bootloader files: http://android.clients.google.com/p....signed-razor-KTU84L-from-KOT49H.df43279b.zip
So you can use make a flashable zip for those bootloader files or I can do it later.
The next one will be for Android 5, so we'll look forward to that also. I guess a smarter person would be able to dump these partitions from their device or something.
Click to expand...
Click to collapse

So your computer doesn't recognize the tablet when it's at the bootloader? Can you even get into bootloader? Tried different cables? Different USB ports?

I can get to TWRP, but no usb not recognized there, cannot use the mount feature in TWRP, tried all items in pretty much every post I could find that were related, inlcuding the items you suggest yes.
Maybe something with the stock rooted ROM has gone wacky, Been very good to this tablet as far as babying the usb port, as I have had other devices have broken ports as my kids would yank cables etc.
So really the only thing I have not done since this trouble started was just do a factory reset and re-flash the ROM, just afraid that is something goes wrong durring flash I will be out of luck restoring anything since I cannot get to the filesystem to put new ROMS etc unless I download them to SD before I begin the process while I have access to the OS and wifi.
nhizzat said:
So your computer doesn't recognize the tablet when it's at the bootloader? Can you even get into bootloader? Tried different cables? Different USB ports?
Click to expand...
Click to collapse

[snip]

Thanks @eksasol I think I may just let this sucker chill until the stock rooted Lollipop ROM, I was already on 4.02 I just thought there was a newer one, I think the Lollipop version has a 4.04 bootloader.
I greatly appreciate your time on this.
So I would assume that if the flash fails for any reason I will be the proud new owner of a nexus 9 shortly after

@eksasol do you have a flashable 4.04 bootloader or know a guide to making a bootloader flashable, I did use your 4.02 and it worked great, but for the Lollipop version I need 4.04 but can only find .img that needs fastboot, which I do not have access to since USB does not seem to work still.

kernelsandirs said:
@eksasol do you have a flashable 4.04 bootloader or know a guide to making a bootloader flashable, I did use your 4.02 and it worked great, but for the Lollipop version I need 4.04 but can only find .img that needs fastboot, which I do not have access to since USB does not seem to work still.
Click to expand...
Click to collapse
You will need to wait until the OTA zip for KitKat to Lollipop become available, it will include the proper 4.04 bootloader files needed for flashing.

OK cool, guess I am just impatient

@eksasol any chance you can throw a flashable 4.04 bootloader together, i see several others looking for one that are in the same boat as me, i looked around for a tutorial on making one but did not find any so far. Anyway if you get a chance or have some info on making one i would be grateful.

Here is the Android 5.0 bootloader version 4.04. For Nexus 7 WiFi only (Flo, Razor), again it will check to see if it's the correct device before proceeding with flashing. Go to this link: http://forum.xda-developers.com/nexus-7-2013/general/flashable-factory-image-zips-android-5-t2939599
kernelsandirs said:
@eksasol any chance you can throw a flashable 4.04 bootloader together, i see several others looking for one that are in the same boat as me, i looked around for a tutorial on making one but did not find any so far. Anyway if you get a chance or have some info on making one i would be grateful.
Click to expand...
Click to collapse
You didn't have to remind me every single day.

Thanks for this. I'm alright with adb and fastboot (i.e. I can follow directions) but I'm running the Windows 10 tech preview and it absolutely does not support either. Drivers are fine, it just won't do it. Won't happen at all. Then I throw it all on a flash, take it to work (Win7 Pro), and it works just as easy as you like, so it's not (likely) user incompetence... I woulda waited but figured someone else might have asked. So, much appreciated!

dragontology said:
Thanks for this. I'm alright with adb and fastboot (i.e. I can follow directions) but I'm running the Windows 10 tech preview and it absolutely does not support either. Drivers are fine, it just won't do it. Won't happen at all. Then I throw it all on a flash, take it to work (Win7 Pro), and it works just as easy as you like, so it's not (likely) user incompetence... I woulda waited but figured someone else might have asked. So, much appreciated!
Click to expand...
Click to collapse
They decided to skip 9?
I posted the full device's image in flashable zip formats here:
http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/