Database Info

usb won't mount

Hi Guys,
My friend bricked his phone some how (he's using the htc one s on tmobile) and I myself am using the evo lte, thought i could be of some assistance, but I'm stuck as well...wonder if you guys could help me help him lol.
so I performed the tasks on post #8 from on how to "fix soft-brick" in the sticky, but being able to only access bootloader, and twrp recovery Im at a stall. While in recovery, i go the the options to mount, it won't mount my usb so that i can bring over a rom to flash in recovery. So my problem is that the phone won't mount to my computer so i can bring over a rom i downloaded on my computer to the phone.
if i reboot system it sticks at the htc develop splash page.
Im pretty stuck and hope u guys can me help my boy.
P.S. i told him next time when you flash, always make a backup....cuz he was trying to flash a jelly bean wip (i don't even think it was a rom for his phone).
Thanks in advance guys!

bump, anyone kind to help me out with this?
Thanks again, hope to help him out, but Im at my wits end because i keep on getting running into the same problem.

jdizzle316 said:
bump, anyone kind to help me out with this?
Thanks again, hope to help him out, but Im at my wits end because i keep on getting running into the same problem.
Click to expand...
Click to collapse
You're going to either need to push a rom to his phone using ADB, or perhaps flash an RUU using Fastboot. Are you familiar with either process? There may be other options, but I'm familiar with both of these scenarios and can at least point you in a direction. Lemme know!

Yeah ADB push is your best option right now. IIRC USB mount in recovery does not work due to kernel limitation. (I could be wrong but remember reading about it)
Look here
http://forum.xda-developers.com/showthread.php?t=1667929

baseballfanz said:
Yeah ADB push is your best option right now. IIRC USB mount in recovery does not work due to kernel limitation. (I could be wrong but remember reading about it)
Look here
http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
I agree with him, I kinda had the same problem your friend had and adb pushing a Rom is probably your best option right now...
Sent from HTC one s

Thank you very much guys, I am not too familiar with pushing thru adb but have been reading up on it through the development section and am ready to dive in.
I very much appreciate the input fellas, will keep you updated with the status of this so that others in this situation can benefit from this as well.
Thanks again!

jdizzle316 said:
Thank you very much guys, I am not too familiar with pushing thru adb but have been reading up on it through the development section and am ready to dive in.
I very much appreciate the input fellas, will keep you updated with the status of this so that others in this situation can benefit from this as well.
Thanks again!
Click to expand...
Click to collapse
If you need help along the way, just ask we are all here to help each other to get ones problem solved and learn from it
Sent from HTC one s

Ok guys, heres the update as promised. Mission to restore was success!
First, I tried to push thru adb, but it would never stick, would always get hung up. Given, being my first time pushing thru adb i probably did it incorrectly. In fact, I managed to push the rom over to the sd card once, but was unable to flash it from recovery (CWM).
Here is how i fixed the problem of being bricked. I relocked the bootloader, using the "all in one kit" and then i downloaded the TMOUS RUU, booted the phone into bootloader and then ran the ruu's exe. Within 10 minutes it was back to bone stock.
I hope this helps fix others with the same problems, if you guys need any help, feel free to hit me up.
Thanks guys for the suggestions and pointing me in the right direction...I couldn't have done it without your help!

jdizzle316 said:
Ok guys, heres the update as promised. Mission to restore was success!
First, I tried to push thru adb, but it would never stick, would always get hung up. Given, being my first time pushing thru adb i probably did it incorrectly. In fact, I managed to push the rom over to the sd card once, but was unable to flash it from recovery (CWM).
Here is how i fixed the problem of being bricked. I relocked the bootloader, using the "all in one kit" and then i downloaded the TMOUS RUU, booted the phone into bootloader and then ran the ruu's exe. Within 10 minutes it was back to bone stock.
I hope this helps fix others with the same problems, if you guys need any help, feel free to hit me up.
Thanks guys for the suggestions and pointing me in the right direction...I couldn't have done it without your help!
Click to expand...
Click to collapse
Congrats on getting it restored hopefully you do a backup of it so this won't happen again
Sent from HTC one s

Thanks! I'll definitely advise my friend to do so, or I may for him lol.
Again, couldn't have done it without everyones help
Sent from my EVO using xda app-developers app

Can my Nexus be fixed?

Hello all
I suspect that either my Nexus has a hardware fault (internal memory) or I bricked it somehow.
For the past few weeks the phone has been getting stuck on the google boot screen quite a lot - It takes several attempts
to start up each time so I've been trying to keep the battery from running down.
The other day while I was attempting to switch roms I put the stock img on my SD card but when I went to flash it CWM
couldnt mount my (internal) SD Card. Senior forum member Caliban2 suggested that it could be my recovery so I installed CWM 6.0.0.7 non-touch using fastboot and, like magic, the phone started up -though I suspect this may have been luck.
I rebooted the phone out of curiosity and it got stuck on the google boot screen - no amount of battery pulling and restarting could coax
it back to life, so I went into CWM again to discover that it could not mount the SD Card, I was getting the 'cannot mount' and 'E:Unable to open ums lunfile(no such file or directory)' error messages. My windows 7 PC could see the phone but said that their was non memory inserted. Out of curiosity I installed CWM 5.0.2.0 but that produced the same results.
So now my phone appears dead, is the internal memory or something related to it is broken? I have seen things on here about using an unbricking tool in Debian Linux or flashing stock using odin but I confess that I have not tried these solutions and don't fully understand them (yet).I wussed out and dropped the phone into a local repair workshop, I imagine they will be trying these same steps themselves and they say it will take them a few days to get back to me.
My problem is that I need a phone for work and I gave my backup phone (HTC Hero) to my dad recently. Should I just take the plunge
and go out today and buy a new phone? Or is there a reasonable chance that these guys can fix my nexus s, or that I might be able to?
I'm a relative 'noob' at this so I thank you all for your advice in advance, it's much appreciated.
Derek

Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.

Thanks, will do. It's in the shop at the moment, I suspect this is probably what they're doing now.
Perhaps subconsciously I'm just looking for someone to tell me it's irreparable so I can rush out
and pick up a Galaxy Nexus.
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse

Hey Harbb
Just wanted to give you an update on this, got it back from the shop who said they would need to send it to Samsung for a hardware repair, didn't expect it to work but fastbooted the stock bootloader, radio and image to the device and it's now working!
I've already moved onto a Galaxy Nexus on contract but at least now I can make a bit of money back off my old phone.
Thanks again for the advice
Derek
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse

[Q] Need help, bad! Greatly Appreciated!

Okay, I rooted my TF101 B90 model and all was good. I installed rom manager and flashed its custom recovery and had that whole issue that the sd card wasn't read and such. After much frustration I finally tried Wheelie (Nvflash) and it keeps failing and now I have nothing on my tablet. I can get into APX mode and flashing the stock rom using many custom utilites always fails (Usually says something like command failure :go failure or could not load bootloader to device) I'm sure it's probably fixable, I just need someone to type it out for me (I'm pretty smart when it comes to Android but I'm honestly stumped right now) Or please redirect me to a post that could help, However I have read a lot of the posts about this and everyone is getting there's to work and I can't get mine. Thank you!!!
Andrew

I beg your help with my tf103c

Hello All,
I tried to find the best place in the forum to put this thread, i hope this one is ok.
Three days ago i made a big mistake trying to root my ASUS TF103C, i have downloaded a wrong zip file with scripts for ZenFone5 and execute a .bat that destroy the tablet (totally my fault). i spent three days reading and trying everything, i read all the forums and tried lot of fastboot procedures and also EasyFlash with stock firmware "WW_epaduser9_2_1_27UpdateLauncher" but nothing. To make it worst (after reading a lot) i realize that i don't have recovery (power+volume down is not working) and i'm sure that my bootloader is locked (since i didn't unlocked) .... I don't know what else to do i'm sure it must be a way to flash a new firmware with fastboot, i mean, i don't want to loose the hope :crying: . At this point i really don't care which firmware , which android version i just want to revive the tablet.
I read this forum A LOT and i know you are experienced people with android and procedures like this.
PLEASE , can you help me ?
Thanks in advance and sorry for my english.

Hello Pr0sper,
i am quite a n00b too but i am suffering a similar error with my tf101 and was trying a lot too.
So just to make sure you did everything:
Are you able to connect your Tablet with your Pc? Is the PC recognising the connection with your Pc?
Is Cold-booting Linux available?
Can you start APX mode on Tablet?
Did you run ADB?
Regards
Bava

[Completed] Please help me. No OS. HTC One M7.

Hey there guys. I bought an HTC One M7 from amazon which came unlocked. Problem was, i couldnt get it to connect to my provider, Koodo. Long story short, i went to flash a Stock Telus Rom to it, no META file in the zip. Already wiped my phone. So now theres no OS. I have TWRP still (thank god for that) but it just sits at the HTC logo and wont boot, as i know thats what happens when you mess up. Fairly familiar with THIS issue, as ive done it to my Samsung Galaxy SIII MANY times before, but had odin to fix it. I have an RUU.exe. Got it from a forum here. Cant connect to my phone (error 171 i believe). Everything is connected properly, and my PC recognizes it, but only as an MTP device. I am gonna try an RUU.zip and flash it with fastboot. See if that method works. But any help at all would be GREATLY appreciated as i dont want to have spent $299 to waste it like betting on the Maple Leafs.
Side note: I cannot get ADB Sideloader to work properly. I have a Custom Rom that i attempted to flash that way, but i got the error that was like ADB version (31) is not up to date with server (36) or something along the lines of that and then it fails to load daemon everytime. Tried some fixes from these forums but none of them were successful. Not familliar with ADB and all that stuff, so if anyone has any fix for the ADB, please dumb it down to kindergardener levels.
Sorry this is so long. Tried to explain everything as detailed as possible for a more acturately helpful response.
UPDATE Got the RUU.zip file to work after a couple hours of messing around with it. Had to fast boot getvar to obtain my model id, and change that in the android-info.txt in the zip file. Is flashing now. HUGE thanks to all of the thousands of XDA forums. Helped me out with everything!

AndyA2098 said:
Hey there guys. I bought an HTC One M7 from amazon which came unlocked. Problem was, i couldnt get it to connect to my provider, Koodo. Long story short, i went to flash a Stock Telus Rom to it, no META file in the zip. Already wiped my phone. So now theres no OS. I have TWRP still (thank god for that) but it just sits at the HTC logo and wont boot, as i know thats what happens when you mess up. Fairly familiar with THIS issue, as ive done it to my Samsung Galaxy SIII MANY times before, but had odin to fix it. I have an RUU.exe. Got it from a forum here. Cant connect to my phone (error 171 i believe). Everything is connected properly, and my PC recognizes it, but only as an MTP device. I am gonna try an RUU.zip and flash it with fastboot. See if that method works. But any help at all would be GREATLY appreciated as i dont want to have spent $299 to waste it like betting on the Maple Leafs.
Side note: I cannot get ADB Sideloader to work properly. I have a Custom Rom that i attempted to flash that way, but i got the error that was like ADB version (31) is not up to date with server (36) or something along the lines of that and then it fails to load daemon everytime. Tried some fixes from these forums but none of them were successful. Not familliar with ADB and all that stuff, so if anyone has any fix for the ADB, please dumb it down to kindergardener levels.
Sorry this is so long. Tried to explain everything as detailed as possible for a more acturately helpful response.
UPDATE Got the RUU.zip file to work after a couple hours of messing around with it. Had to fast boot getvar to obtain my model id, and change that in the android-info.txt in the zip file. Is flashing now. HUGE thanks to all of the thousands of XDA forums. Helped me out with everything!
Click to expand...
Click to collapse
Thread closed as OP fixed his issue