Database Info

[Q] Xoom won't turn on

I recently tried to root my xoom and got to the point where I need to flash the images. The already mounted USB storage space was not big enough for me to copy the files over (only 3mb and I needed at least 5mb), so I reset the xoom.
It doesn't respond to Power + Vol Up, Vol Down, or any of the above combinations. The only response I get is the charging light when its charging.
What else can I try before attempting to send this in?
Any help is appreciated.

Any luck on getting up and running? I would say try it unplugged, try it with the USB in, and try to wee if its caught somewhere in the boot process by running ddms or seeing if yu can adb reboot....but it would be helpful to explain your exact steps you took to attempt to get root. Did you have a custom recovery image or were you in fastboot when it jacked up?
Sent from my Xoom using Tapatalk

dhemke17 said:
Any luck on getting up and running? I would say try it unplugged, try it with the USB in, and try to wee if its caught somewhere in the boot process by running ddms or seeing if yu can adb reboot....but it would be helpful to explain your exact steps you took to attempt to get root. Did you have a custom recovery image or were you in fastboot when it jacked up?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
No luck at all. I've tried it with USB in, plugged/unplugged. I was in CWR while I had the USB storage from my Xoom mounted, but like I mentioned earlier it only gave me 3mb of space. I used the procedure on this post http://forum.xda-developers.com/showthread.php?t=1083739 It messed up after i flashed CWR and was about to flash the kernals

Make yourself a factory cable, or cough up 50 bucks for one... people posting results with those.

Unless there's another place for me to buy them besides TBH, I guess I can try to make one.
Anyone know of reliable sellers on eBay?
Sent from my DROID2 using XDA App

had same problem i let the battery run down took it back to Bestbuy said it would boot up how long you had it one other thing if you plug it in and do a adb devices does your computer see it cause i can walk you thru that own a couple of units and if you dondt know adb yet i can help with that

A little more than a month ago from my local Verizon store.
Really trying to get this fixed before I deploy
Sent from my DROID2 using XDA App

on the comp question plug it in and bring up your adb and see if the comp sees it dos or shell depending what you on you can push a file while it is asleep

Tried that, adb devices doesn't see it
Sent from my DROID2 using XDA App

dont take poor on your command promp are you in the folder of your platform tools and is sdk up and running what OS are you on
also
http://forum.xda-developers.com/showthread.php?t=970665
same across just to give you more info on the volume up holding power for a bit
fellow floridian to bad your far from me i love went things dont work and fixing them

SDK is up, I was in my tools folder. On Windows 7.
And I'm not even in the state right yet, only get to visit when the Army says I can haha.
Sent from my DROID2 using XDA App

[Q] Help with Broken Nexus S

Hey I'm in need of some serious help. My power button no longer works. It's as thought the phone thinks its constantly being held down. (Put battery in phone boots up by itself). I'm pretty comfortable with flashing roms etc and I need to get the bootloader locked for my warranty. I've tried multiple ways (I've done it in the past for friends). The 'fastboot oem lock' in fastboot via cmd doesnt work. It appears to be due to the power button being held down. It wont progress any further. It is not physically jammed (trust me ive tried fidgeting with it lemme tell you). I'm at a loss. Any ideas?

Have you tried taking the phone apart to see what could be holding the power sours down?
Sent from my Nexus S 4G using xda premium

Esteway.619 said:
Have you tried taking the phone apart to see what could be holding the power sours down?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I thought about it but it appears perfect. Looks and feels like it normally does. That's why at first I thought it was software related. Nope alas it was not. I tried pulling it with tweasers and there is no response at all

Same thing happened to me and I sent it in for warranty with the bootloader unlocked. Samsung fixed it and no charge.

garu12 said:
I thought about it but it appears perfect. Looks and feels like it normally does. That's why at first I thought it was software related. Nope alas it was not. I tried pulling it with tweasers and there is no response at all
Click to expand...
Click to collapse
Dang. I hope u can fix it.
Sent from my Xoom using xda premium

Thanks for the replies. It's impossible to relock in this state! I did manage to unroot and install a stock rom so at least it's gonna look somewhat legit when I bring it in. Going to the Samsung repair center tomorrow (there is one not far from me so I dont need to send it). I'll let you know how it goes. Wish me luck!!

So I went in today to the Samsung repair center and 2 hours later my Nexus is good as new . Pretty classy of them. That's really good service. They didnt even question the unlocked bootloader and it was covered by the warranty. This makes me want to stick with Samsung. When my Nexus One power button died it took like 4 weeks to get it back

Does anyone know how to force my Nexus s into recovery? Its stuck in boot screen
Sent from my Google Nexus S using XDA App

I have an entirely different issue but it involves me sending in my phone to samsung with an unlocked bootloader. My phone won't boot past the google screen and I can't relock the boot loader via adb. I've already sent the phone but didn't mention anything about it being rooted when I called customer service. Think there's a good chance they'll fix it no questions asked?

bradmikd said:
Does anyone know how to force my Nexus s into recovery? Its stuck in boot screen
Sent from my Google Nexus S using XDA App
Click to expand...
Click to collapse
In CMD if you have adb installed type "adb reboot bootloader"
It will get you to fastboot and then select recovery. Or you can just hold the volume up and power on the phone (I'm assuming that doesnt work)

garu12 said:
In CMD if you have adb installed type "adb reboot bootloader"
It will get you to fastboot and then select recovery. Or you can just hold the volume up and power on the phone (I'm assuming that doesnt work)
Click to expand...
Click to collapse
or just adb reboot recovery

Is my phone dead?

Hi All
Hoping someone can tell me if I've completely killed my phone. It was working absolutely fine with no problems whatsoever until earlier today when it froze. Without looking around at what to do I just held down Vol + & Vol - & power. This restarted the phone and it went through the T-Mobile logo and then just sat there. I then took out the battery, put it back in and held vol - and hit power, got into the clockworkmod menu and used the recovery option to wipe then restore an earlier backup, this all seemed to go fine and I used the power off option to restart the phone.
Nowwww though it just vibrates 7 times and stops, if I then pull the battery and replace it and hit power it vibrates 7 times again and then nothing unless I pull the battery again.
Am I screwed?
The phone is S-Off and had clockworkmod installed. Has the clockworkmod boot loader thingy some how been damaged? Anything I can do?
Appreciate any advice. Thanks

can you get into recovery? if so try wiping everything and then doing a fresh install of something
Sent from my Desire HD using XDA App

dont keep pulling the battery if you dont already have emmc failure you will soon if you continue to pull the battery!

Yea I didn't realise pulling the battery was that bad. I haven't done it since reading this forum. But no I can't get in to recovery any more since that time I wiped everything and restored a backup. Since then it just vibrates 7 times when I push the power button and that's all.

can it connext to adb? if so, id try flashing an ruu via fastboot. that will set everything back to stock. then you can reroot and flash a rom, and id get rid of that backup
Sent from my Desire HD using XDA App

Is there a guide for adb anywhere? I haven't used it before, but I've tried plugging the phone in by USB and Windows doesn't say new hardware found so I assume that's a bad sign?

rlzzzz said:
Is there a guide for adb anywhere? I haven't used it before, but I've tried plugging the phone in by USB and Windows doesn't say new hardware found so I assume that's a bad sign?
Click to expand...
Click to collapse
theres tons of guides but if you give me a few minutes ill upload a auto installer for you, so then you just have to add the path in
Sent from my Desire HD using XDA App

I looked for adb guides and they all seem to show how to install the drivers etc but my phone doesn't even get detected as a new device in Windows so I assume it's not going to show up?
I mean it looks completely dead right now, won't turn on or even vibrate. Unless I was to pull the battery again I think it would probably then vibrate 7 times when I push the power button for the first time and that would be it again.
Do you think the clockworkmod boot loader got overwritten some how when I did the restore?

rlzzzz said:
I looked for adb guides and they all seem to show how to install the drivers etc but my phone doesn't even get detected as a new device in Windows so I assume it's not going to show up?
I mean it looks completely dead right now, won't turn on or even vibrate. Unless I was to pull the battery again I think it would probably then vibrate 7 times when I push the power button for the first time and that would be it again.
Do you think the clockworkmod boot loader got overwritten some how when I did the restore?
Click to expand...
Click to collapse
it could of, and its worth a shot, it might be recognized. just get adb working, and install the drivers. plug the phone into your computer, and wait a minute or 2 and the screen should turn on but be black. then just boot into the bootloader and flash the ruu via fastboot
Sent from my Desire HD using XDA App

So I installed Java JDK, then Android SDK, then downloaded the HTC adb drivers but it says to install the drivers plug in your phone and wait for Windows to detect it... which is as far as I can go because Windows doesn't detect the phone.
I don't even seem to be able to reset the phone by holding Vol + & Vol - & power at the same time. It's not looking good.

In fact you say about the phone going to a black screen, it did do this after I initially restored the image. But it was just after that that I pulled the battery and now it doesn't do that anymore.
I assume basically what has happened then is first some thing froze and corrupted my normal install, so to fix this I tried the restore and the restore image somehow overwrote clockworkmod but at this point the phone was still recoverable via adb? but then I pulled the battery and now it's definately dead?
Seems like an unfortunate string of events but at least I know now to avoid pulling the battery next time! Thanks for all your help stumpyz9 and djisgod, I don't suppose you know why pulling the battery can so easily kill the phone?
Btw if anyone would like to jump in and make my day by saying nooo everything is fine here is a quick fix please feel free

my only guess of why pulling the battery killed it is when you where restoring it and then pulled the battery, it was restoring something very essential to even turning the phone on. i dont know why windows wouldnt detect your phone, it has derected my DHD even in the worst scenarios. and were you saying the drivers wanted you to hook the phone to the computer? if so dont and try to continue installation, because if you can get it hooked up to your computer and have adb recognize it, then tyere is a very good chance you can recover it. if not, then im sorry to say you have yourself a very pretty paper weight. if it is a paper weight, id say maybe check to see if a dev could use it or basically part it out on ebay and sell the lcd, digitizer, housing, camera and you can probably make some of your money back.
Sent from my Desire HD using XDA App

The ADB HTC drivers I downloaded are not an installer file, you need to plug in the phone so Windows will recognise a new device and ask you to select the location of the drivers but I can't because it doesn't detect the phone being plugged in at all.
I've also been reading around a bit more and found a thread about a fried eMMC chip. I was actually getting the same errors they mention in that thread when I did the restore from clockworkmod.
"E:Can't open /cache/recovery/log" etc etc

dont use that, install htc sync, then plug the phone in and tell me if that works
Sent from my Desire HD using XDA App

Yea I just gave that a go after reading someones adb guide and even with HTC sync installed when I run "adb devices" it lists nothing.
It's strange I thought once I had clockworkmod installed nothing could go wrong because I would always be able to restore from an old backup. I always assumed that clockworkmod would be sat on the boot partition and never touched even when restoring a backup. I can't understand how it went so wrong lol.
Although right now the phone seems so far gone maybe I could get away with a warranty repair as they won't be able to tell it was S-OFF.

yah if all of the chip has been fried and it wont power on, i think that would be your best bet, seeing as they probably wouldnt be able to tell.
Sent from my Desire HD using XDA App

Ok well thanks for your patience I appreciate your help.

rlzzzz said:
Ok well thanks for your patience I appreciate your help.
Click to expand...
Click to collapse
no prob, alwsys like to help out when i can
Sent from my Desire HD using XDA App

[Q] I killed my sensation

Unfortunately I flashed this kernel http://forum.xda-developers.com/showthread.php?t=1878506 on my sensation.
Don't ask how I was absolutely idiot.
android revolution hd run on it without any problem but after flashing that galaxy kernel and rebooted from 4ext
not booting even the H-boot either. fastboot says for "adb devices" command " after I connected the sensation via usb cable to windows "List of devices attached" but nothing appear
I tried power + vol down power + vol up power+home power+back but nothing just a dark flash for a sec after nothing.
:crying:
Would be able someone to give me any advice what should I do .
Thank you

Yes. You killed your sensation. It sounds like a hard brick, although you can always try the unbricking project here: http://forum.xda-developers.com/showthread.php?p=23078349
I really don't think it'll work, but you've got nothing to lose at this point. If the phone won't boot at all (not even in bootloader) and adb doesn't recognize the device, you may have to get your motherboard replaced.
I hope the link works for you, but prepare to spend some money fixing your phone.
Sent from my HTC Sensation

AndroidSupporter318 said:
Yes. You killed your sensation. It sounds like a hard brick, although you can always try the unbricking project here: http://forum.xda-developers.com/showthread.php?p=23078349
I really don't think it'll work, but you've got nothing to lose at this point. If the phone won't boot at all (not even in bootloader) and adb doesn't recognize the device, you may have to get your motherboard replaced.
I hope the link works for you, but prepare to spend some money fixing your phone.
Sent from my HTC Sensation
Click to expand...
Click to collapse
Thanks Brother for the quick response! I don't know it will work or not but I will try out. After 6 hours of nervousness you gave me a glimmer of hope.

Good luck! Let us know if the unbrick project works.
Sent from my HTC Sensation

AndroidSupporter318 said:
Good luck! Let us know if the unbrick project works.
Sent from my HTC Sensation
Click to expand...
Click to collapse
Hi unfortunately I ended in failure at the first step.
In that suggested way my sensation not recognise.

lalicapri said:
Hi unfortunately I ended in failure at the first step.
In that suggested way my sensation not recognise.
Click to expand...
Click to collapse
Motherboard needs a JTAG I guess, take it to a repair shop
Sent from my GT-I9305 using Tapatalk 2

Yea, if PC can't even recognize your phone, then your only option is to replace motherboard
Sent from my HTC Sensation

Hello guys! Thanks for everyone to try to help me. Finaly JTAG could solve my problem now running Android revolution hd again.
but I keep thinking about how to change the wifi mac adress.

Firewater S-Off method not working?

ADB sees my phone, everything is getting pushed to the phone and when I run firewater, it goes through all 12 bottles and then says it can't complete. Anyone else have this problem? Any ideas?

slide83 said:
ADB sees my phone, everything is getting pushed to the phone and when I run firewater, it goes through all 12 bottles and then says it can't complete. Anyone else have this problem? Any ideas?
Click to expand...
Click to collapse
i havent had this happen but i know some have im sure someon can help but till then you might want to hit up firewater team on irc #firewater

You're not using a Windows 8.1 PC or a USB 3.0 port, are you?

Mike02z said:
You're not using a Windows 8.1 PC or a USB 3.0 port, are you?
Click to expand...
Click to collapse
For what it's worth I did use a 3.0 port on a z87 board with 8.1 64bit installed with no issues to report. It completed on the first bottle.

Ditto. I used Windows 8.1 and a usb 3 port (is all my laptop has), and everything worked fine - 1st try.
I know that doesn't help op, but would also hate to see him chasing extraneous things that aren't the problem.

slide83 said:
ADB sees my phone, everything is getting pushed to the phone and when I run firewater, it goes through all 12 bottles and then says it can't complete. Anyone else have this problem? Any ideas?
Click to expand...
Click to collapse
I had this problem. I simply rebooted and redid firewater and it went thru. I also wasn't using a pc, just term emulator from within the phone
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Same thing happened to me. Gotta make sure your also using the most current version of adb.
Sent from my HTC6525LVW using xda app-developers app

Also make sure your screen is awake and doesnt have any type of lock screen. I just had slide to unlock and it didnt work first time, disabled it and made sure screen never went to sleep and worked 2nd time no issues.

slide83 said:
ADB sees my phone, everything is getting pushed to the phone and when I run firewater, it goes through all 12 bottles and then says it can't complete. Anyone else have this problem? Any ideas?
Click to expand...
Click to collapse
Also did you be sure to chmod firewater after you pushed it
Sent from my HTC6525LVW using XDA Premium 4 mobile app

izzaeroth said:
Also did you be sure to chmod firewater after you pushed it
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this. this is key

Cant get mine to work either. After adb reboot command, phone reboots and i wait for the "root achved" message and enter adb wait-for-device push firewater/data/local/tmp and cursor goes to next line and just blinks.

Mine was blinking and I didn't uncheck fastboot
Sent from my HTC6525LVW using XDA Premium 4 mobile app

are you guys watching the video
http://forum.xda-developers.com/showthread.php?t=2697957

jmcamz2899 said:
Cant get mine to work either. After adb reboot command, phone reboots and i wait for the "root achved" message and enter adb wait-for-device push firewater/data/local/tmp and cursor goes to next line and just blinks.
Click to expand...
Click to collapse
Got it working. I closed my cmd session. Rebooted phone manually. Waited for root achieved and started over. Only this time I skipped the adb reboot step. All is good now. Also used usb 3.0
Sent from my HTC6525LVW using xda app-developers app

Tried a different USB port, new version of ADB from the how-to video, waiting till root achieved, still goes through all the "bottles" and can't acheive s-off....

I love that most all developers are alcoholics

Any other ideas?

slide83 said:
Any other ideas?
Click to expand...
Click to collapse
Try the adb shell commands directly in terminal emulator
Sent from my HTC6525LVW using XDA Premium 4 mobile app

jmcamz2899 said:
Cant get mine to work either. After adb reboot command, phone reboots and i wait for the "root achved" message and enter adb wait-for-device push firewater/data/local/tmp and cursor goes to next line and just blinks.
Click to expand...
Click to collapse
Mine did the same thing. Adb wasn't recognizing me phone after adb reboot so I unplugged it and plugged it back in. Entered adb devices to makes sure I could see my device and then instead of typing
adb wait-for-device push firewater/data/local/tmp
I typed
adb push firewater/data/local/tmp
And everything went through fine.
Sent from my HTC6525LVW using Tapatalk

can anyone help
Yes
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********