I have just flashed my Desire S with Bindroid ROM after EXT4 Wipe. Now phone only shows HTC screen, Now Im very carefull about emmc issue...its neary 30 minute as it is hanging. I have read all the threads and in this situation
1) I can not pull my battery coz it fires my emmc
2) Pressing Power+vol down is not working, power+vol up+vol down is not working
3) Connected phone to pc and ADB is not reconizing my phone
Now what should i do?
Hope that this will
Code:
sagarda7 said:
I have just flashed my Desire S with Bindroid ROM after EXT4 Wipe. Now phone only shows HTC screen, Now Im very carefull about emmc issue...its neary 30 minute as it is hanging. I have read all the threads and in this situation
1) I can not pull my battery coz it fires my emmc
2) Pressing Power+vol down is not working, power+vol up+vol down is not working
3) Connected phone to pc and ADB is not reconizing my phone
Now what should i do?
Click to expand...
Click to collapse
For a start don't panic (just yet)
[Questons]
Do you have a safe Nandroid Backup that you can restore to?
You obviously have a custom RECOVERY (which one?)
Do you know which eMMC card you have?
Options Left
[1]
Pull Battery (which is risky - if you do - then pull evenly and quickly and do not re-insert for over 10 seconds)
Assuming that you have a Nandroid Backup then:
[2]
Let battery completely run out until phone shuts down on it's own.
plug into power supply for a hour or so (until battery full (green light)
Restart and force entry to bootloader (volume down + power)
Restore safe point backup from RECOVERY
Reboot
If you have no backup
[3]
Download another (safe) Custom ROM and place on SD card
Let battery completely run out until phone shuts down on it's own.
plug into power supply for a hour or so (until battery full (green light)
Restart and force entry to bootloader (volume down + power)
Ensure- that you manually WIPE SYSTEM, DATA, CACHE, , DALVIK CACHE, SYSTEM
flash new ROM
Reboot
If you don't know which eMMC chip that you have, then once you device is booted you should run the following commands from you PC to find out (you don't want these results, which is what I have) as this is run that fails:
Code:
C:\Program Files\Microsoft Support Tools>adb shell
# cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
[B][COLOR="Red"]M4G2DE[/COLOR][/B]
#
I'll be online this morning, so will be able to assist......
- Did you activate "USB debugging" mode in the menu Settings-Applications-Development?
If NOT so you can not connect by the ADB command.
- Did you press and hold down VOL UP and VOL DOWN first, and then press Power button?
If none of the above method is working, the only option for you is pulling the battery out. Remember to not re-insert so quickly.
Thanks, My chip M4G2DE or like that Coz forgot. I am sure it is the faulty one. Anyway problem its solved, thanks again
sagarda7 said:
Thanks, My chip M4G2DE or like that Coz forgot. I am sure it is the faulty one. Anyway problem its solved, thanks again
Click to expand...
Click to collapse
How did you solve it? Reboot by ADB? by Vol up/Vol down/Power combination or pulling out the battery?
Yes, how did you solve it? So that people will know what to do when they're in this situation. Thanks!
Probably adb reboot recovery command thru terminal.
Sent from my HTC Desire S using XDA Premium App
Been there myself
I went down the same rabbit hole a couple of days ago brother. Exactly the same problem you were having.
This is what saved me... Read.
how I solved it
vndnguyen said:
How did you solve it? Reboot by ADB? by Vol up/Vol down/Power combination or pulling out the battery?
Click to expand...
Click to collapse
First of all I think my Emmc may be good one or I'm lucky for that being labeled as M4G2DE. I had already nandroid backup in my sd card.
A) I waited and waited till battery was completely zero.
B) after phone turned off, waited for 2 minute.
c) connected phone to the charger and charged for 1 hour
d) opened recovery by pressing vol down first, then pressed power and released power and after getting hboot screen, released vol down.
e) went to clockwork mod and restored nandroid.
You downloaded the wrong Rom, according to your post in the other thread.
You want a ROM for the DS, not DHD
Sent from my HTC Desire S
Please provide me the link for desire s
sagarda7 said:
First of all I think my Emmc may be good one or I'm lucky for that being labeled as M4G2DE. I had already nandroid backup in my sd card.
A) I waited and waited till battery was completely zero.
B) after phone turned off, waited for 2 minute.
c) connected phone to the charger and charged for 1 hour
d) opened recovery by pressing vol down first, then pressed power and released power and after getting hboot screen, released vol down.
e) went to clockwork mod and restored nandroid.
Click to expand...
Click to collapse
Tks for your explaining, however I didn't ask for restoring procedure to stock backup.
As you've said in your 1st post, your DS has hang on the HTC screen. How did you do to bypass this issue and recharge your phone? Wait until the battery completely discharged itself?
sagarda7 said:
Please provide me the link for desire s
Click to expand...
Click to collapse
Simple - go to this page and download this one - BinDroid DS 2.3.5 GB V1.0.
But there's an imminent update, so prob better to wait.
Peace
vndnguyen said:
Tks for your explaining, however I didn't ask for restoring procedure to stock backup.
As you've said in your 1st post, your DS has hang on the HTC screen. How did you do to bypass this issue and recharge your phone? Wait until the battery completely discharged itself?
Click to expand...
Click to collapse
Ya, waited till battery is discharged completely
sagarda7 said:
Ya, waited till battery is discharged completely
Click to expand...
Click to collapse
This is not a good idea, because the risk is the same as you pull out the battery. And this will also affect the battery lifetime (because of completely discharge).
Related
Hi, i've got a big problem...
After a system crash i pull-out the battery and then pull-in to reset the device.
after that now when i turn on the telephone it remain stucked on the white screen with htc logo. tryed to factory reset but remain stucked after i press on it.
my htc has original rom. no modification. what can i do? i don't really want to spend 3 weeksfor htc assistance.
Thanks
Semi-bricked phone E:Can't mount /cache/recovery/command
[solved]BRICKed: inside eMMC's dead, with E:Can't open /cache/recovery/log
For everyone who Bricked their phone - Help prevent the others
[Guide] How to brick your Desire S
Have i to flash a stock rom? how can i do without remove warranty? in the case it does'nt work i have to take it to htc center
You probobly fried your EMMC chip when you removed your battery.
it would be best to return it in for repair.
I think you may have same problem with me before. No choice but to bring it to repair.
Sent from my HTC Desire S using XDA App
It was s-off before? Can you boot 2 recovery?
It's unlikely your chip is fried. This happened to my phone. You need to get into recovery - restart holding volume down button - and reflash a ROM, any one should do. The phone should reboot from there.
Edit: thus assumes you have a ROM stored on your phone, and you have Clockwork recovery or similar. If not, you can use adb to push a ROM to your card and reflash that. Adb comes with Android Developer Kit. Search!
Peace.
Sent from my HTC Desire S
chris5s said:
It's unlikely your chip is fried. This happened to my phone. You need to get into recovery - restart holding volume down button - and reflash a ROM, any one should do. The phone should reboot from there.
Edit: thus assumes you have a ROM stored on your phone, and you have Clockwork recovery or similar. If not, you can use adb to push a ROM to your card and reflash that. Adb comes with Android Developer Kit. Search!
Peace.
Sent from my HTC Desire S
Click to expand...
Click to collapse
Same problem as topic poster, i,ve been messing a lot with custom roms on win 6.5 phones, but I havn´t done anything fancy on my Desire S , as to rooting or custom roms. (work phone!) Now I´m just curious as how I get a recovery going, when the PC doesent recognice the device when USB connected.
The eng-off file (mine is ON) with the .bat file cant connect to phone, and maybe im better off sending it to repair, but my pride wants me to solve it myself.
-Damn phone just went AWOL last night after an marked Angry Birds update, rebooted it a couple of times, because of a lot of process errors, and then all dead. (white HTC screen on -until morning)
Have the latest FOTA (DK, Nordic)
ROM: SAGA PVT SHIP S-ON RL
Hboot: 0,98.0002
Radio: 3805.06.02.03_M
Are there any ninja tricks or is it just a "bite down", send in?
/Psudo
psudo said:
Same problem as topic poster ....
Are there any ninja tricks or is it just a "bite down", send in?
/Psudo
Click to expand...
Click to collapse
Maybe best sending it in if that's a viable option.
You say it's not rooted? With stock ROM? If there is a ROM on the sdcard that you can boot then try that - power + volume up + volume down will reboot the phone, try pressing volume down as it reboots to get into recovery.
If you can't (by pressing volume down) then power off and restart (holding volume down). I had to do a battery pull to power off - if you do this while the phone is off as it reboots, and leave it out for 30 secs you should avoid any danger of bricking the phone (which has happened with some people when removing battery while phone is in this state).
Good luck!
Peace
chris5s said:
Maybe best sending it in if that's a viable option.
You say it's not rooted? With stock ROM? If there is a ROM on the sdcard that you can boot then try that - power + volume up + volume down will reboot the phone, try pressing volume down as it reboots to get into recovery.
If you can't (by pressing volume down) then power off and restart (holding volume down). I had to do a battery pull to power off - if you do this while the phone is off as it reboots, and leave it out for 30 secs you should avoid any danger of bricking the phone (which has happened with some people when removing battery while phone is in this state).
Good luck!
Peace
Click to expand...
Click to collapse
"ROM on SDcard": what format would that be in? RUU.exe or?
I can get into recovery menu (HBOOT) but chosing recovery option results in "a green recycle icon with an arrow on black background" screen, a few seconds then it virbrates 6-8 times, and then fades to black, so to speak!
Factory reset option: Locks the HBOOT screen and nothing but a battery pull, will change that.
I MAY have pulled the battery and not left it out for the 30 sec bricking danger senario, that I wasn´t aware of, until resently.
So the diag. is that is probably bricked!
Thanks for the reply
/Psudo
Rom on sdcard would have to be *.zip to be flashable. If you're unrooted + stock then you won't have Clockwork recovery or similar.
Tough that factory reset doesn't give any joy. These devices.....
Looking like masonry then, unless someone else can help.
Peace
Sent from my HTC Desire S using xda premium
surprisingly i got the same issue yesterday after i installed proxuser's official htc rom. Everything started fine went through setup so i assume it's not because of the rom because i don't think the phone would've started up in the first place. Anyway i am about to try and install some different roms and have also copied a backup over from my other desire s.
Will let you guys know if it worked.
when i was on runny v1.1 rom,i tried to flash unity v4 kernel,and it's very unstable,i had no other choice but to reflash the rom to get the kernel back.
the rom has wipe code in it's updater script...
the device hanged at "formatting nand with ext4 alignment" for like half an hour,...
having read the danger of pulling battery...i decided to gold the volume buttons and power button...the phone then rebooted and vibrate for 7 times...what can i do?i tried adb,but the computer cannot detect the device/...
If you don't want to pull the battery leave it run flat and then pull it. Charge it while the phone is off and then see if you can boot into hboot. If you can get to hboot then no you almost certainly haven't bricked your phone.
have you tried holding down the volume down button then holding down power at the same time? this should take you to the bootloader. from there you can go to recovery and format system, data and cache then install a previous backup or a new rom
i used the button method to reboot...and after that it rebooted and vibrates for 7 times...when i pulled my battery,and i tried to open it with volume down and power button held,all it does is just vibrates for 7 times again..
tcchuin said:
i used the button method to reboot...and after that it rebooted and vibrates for 7 times...when i pulled my battery,and i tried to open it with volume down and power button held,all it does is just vibrates for 7 times again..[/QUOTE
can you get your pc to connect to it? does charging light light up?
if not try connecting wall charger and see if it will charge?
Click to expand...
Click to collapse
no to both questions...
how much charge was in the battery before this happened?
the only thing i can think to try now is a new battery. im getting out of my depth a little now...
After powering it on have you tried to see if adb recognises the phone and if it does does it respond to commands?
You'll find adb&fastboot within my sig, alongwith some HTC drivers download and install both onto your PC (assumong that you don't already have them). then plug the phone into PC by USB. Run a CMD, go to the directory where you extracted adb files and try
Code:
[B]adb devices [/B] [COLOR="Green"]-- [I]just to see if it recognises [/I]device?
[/COLOR]If it does then try :
Code:
[B]adb reboot recovery[/B]
[I]if no response then try[/I]
[B]adb reboot-bootloader[/B]
report back and good luck
it was like around 90%...
it cannot detect the phone...
O dear!
tcchuin said:
it was like around 90%...it cannot detect the phone...
Click to expand...
Click to collapse
It's look like a visit to the local HTC service centre is next step, based on the complete lack of reponse from your phone. Although I'd obviously never advise any one to tell lies , it's probably not a good idea to meantion S-OFF etc when returning the phone and you'll most probably get a replacement unit or at least a new motherboard!
Hi, I've got a little sceary problem with my desire s.
I installed reaper v 1.2 ROM, configured it, everything was ok. But now phone is not responding. Only black screen. I tried vol up/down and power button configuration - nothing happend. I connected phone to the charger and led turned on, I tred the same configuration - nothing happend. I discconnect phone - led is still on and phone is not responding.
I downloaded latest android sdk tools, latest htc drivers, installed, connected phone to computer, run sdk tool and type adb reboot recovery - error device not found.
When I connect phone to computer it found Qualcomm CDMA Technologies MSM, I try to install soft automaticly but comp find nothing.
Wha else I can do? I don't want pull battery. I have never done it.
Help, please.
adix631 said:
Hi, I've got a little sceary problem with my desire s.
I installed reaper v 1.2 ROM, configured it, everything was ok. But now phone is not responding. Only black screen. I tried vol up/down and power button configuration - nothing happend. I connected phone to the charger and led turned on, I tred the same configuration - nothing happend. I discconnect phone - led is still on and phone is not responding.
I downloaded latest android sdk tools, latest htc drivers, installed, connected phone to computer, run sdk tool and type adb reboot recovery - error device not found.
When I connect phone to computer it found Qualcomm CDMA Technologies MSM, I try to install soft automaticly but comp find nothing.
Wha else I can do? I don't want pull battery. I have never done it.
Help, please.
Click to expand...
Click to collapse
Don't panic brother. I've been in a similar situation many times. Whatever you do... DO NOT PULL THE BATTERY till the phone is switched off!!
Just disconnect the phone from the laptop or wall socket (remove the usb cable from the phone) and leave the phone. Don't sit and stare at it, and don't try to reason it into rebooting. Also, stop pestering God...he doesn't do phones. (I think) Just relax, and go watch T.V. or something.
One out of two things may happen :
1. It may reboot on it's own. Has happened to me... Sometimes it happes in 5 mins, sometimes in 20, and sometimes, never.
2. The battery will eventually run out of charge and your phone will switch off by itself. Now remove the battery, reinsert after 2 mins and boot up into recovery. From here, you can restore your previous nandroid backup.
P.S. If you do not have a nandroid backup, just reflash the ROM after a full format ("format all partitions, except sdcard" option in recovery). Note that if you have unlocked using HTC site, this will not work until you manually flash boot.img (you can find it in the ROM (Reaper_v1.2.zip) file) from fastboot.
Let me know what happens.
Now I' still waiting, without phone touching. Led is ON (orange colour). Phone is disconected (and me too ). Battery level was 13% before this insydent.
When LED will turn off (I don't know when) I'll reinsert battery and let you know what's up.
I hope, I did't bricked it...
adix631 said:
Now I' still waiting, without phone touching. Led is ON (orange colour). Phone is disconected (and me too ). Battery level was 13% before this insydent.
When LED will turn off (I don't know when) I'll reinsert battery and let you know what's up.
I hope, I did't bricked it...
Click to expand...
Click to collapse
Don't worry. I am virtually a 100% sure you have NOT bricked it.
Just don't panic and let the phone switch off first.
BTW, you didn't say if you unlocked your bootloader with HTC Dev site or Revolutionary?
Do you have a Nandroid backup of your previous ROM ?
How new are you to all this (flashing etc)?
Is this the first custom ROM you have flashed on this device?
enigmaamit said:
Don't worry. I am virtually a 100% sure you have NOT bricked it.
Just don't panic and let the phone switch off first.
BTW, you didn't say if you unlocked your bootloader with HTC Dev site or Revolutionary?
Do you have a Nandroid backup of your previous ROM ?
How new are you to all this (flashing etc)?
Is this the first custom ROM you have flashed on this device?
Click to expand...
Click to collapse
My phone was s-off by xtc clip (I did't use revolutionary), boot loader was unlocked on HTC Dev site.
I flashed at first CMW recover, than 4EXT Touch recovery and used it.
I tried a lot of roms, virtuous, endymnion, runny. The best for the beast was CM7.1, nightly. I flashed it month ago and updated succefully. Two days ago I decided to try REAPER. I wiped cache and dalvik's, than flashed reaper v 1.1. Today I updated it to 1.2 version (the same way as always) and I had a problem with dialer, so I wiped everything. Format all ex. sd card was done and I flashed reaper 1.2. I confogured it, just I like (set a new gov reaper, freq 118 (I don't remember) low and 1074 high) and thats it. I tried laucher, sms, phone and thats all.
adix631 said:
My phone was s-off by xtc clip (I did't use revolutionary), boot loader was unlocked on HTC Dev site.
I flashed at first CMW recover, than 4EXT Touch recovery and used it.
I tried a lot of roms, virtuous, endymnion, runny. The best for the beast was CM7.1, nightly. I flashed it month ago and updated succefully. Two days ago I decided to try REAPER. I wiped cache and dalvik's, than flashed reaper v 1.1. Today I updated it to 1.2 version (the same way as always) and I had a problem with dialer, so I wiped everything. Format all ex. sd card was done and I flashed reaper 1.2. I confogured it, just I like (set a new gov reaper, freq 118 (I don't remember) low and 1074 high) and thats it. I tried laucher, sms, phone and thats all.
Click to expand...
Click to collapse
Well in that case, don't worry your phone is safe. Just wait for it to switch off. Then after booting into recovery, just restore the last working ROM backup that you have. Don't flash the Reaper 1.2 that you downloaded till you have confirmed that the md5 checksum matches the one posted by Lowveld.
Hmm. Strange.
Phone turned off - LED was off, so I pulled battery, wait 2-5 minutes (without battery) and tried to turn it on. I saw a black screen. I press vol up/down power buttons, phone vibrated 3 times (quick) and I saw a green LED. I tried turn it on (with vol down button and without it) - nothing. I waited a while then a Led turned off.
I pluged device to the charger - orange led started blinking, so I tried to on phone - nothing. I restarted it (3 buttons) - it vibrated 3 times quickly and the same story from my first post.
Phone is unplugged, orange led is on (not blinking) and no react.
Any ideas??
Can you still boot to recovery?
adix631 said:
Hmm. Strange.
Phone turned off - LED was off, so I pulled battery, wait 2-5 minutes (without battery) and tried to turn it on. I saw a black screen. I press vol up/down power buttons, phone vibrated 3 times (quick) and I saw a green LED. I tried turn it on (with vol down button and without it) - nothing. I waited a while then a Led turned off.
I pluged device to the charger - orange led started blinking, so I tried to on phone - nothing. I restarted it (3 buttons) - it vibrated 3 times quickly and the same story from my first post.
Phone is unplugged, orange led is on (not blinking) and no react.
Any ideas??
Click to expand...
Click to collapse
Well, the blinking signifies inadequate charge for a bootup. Wait till the orange LED stopsa blinking and turns on constantly... then boot into bootloader (Voulme up and Power button - don't let go of the volume button even after releasing the power button) - I don't want you to restart by using three button combo...otherwise you'll be back to the same problem, trying to boot into a broken OS... Just disconnect again and wait for it to switch off.... then reinsert battery, connect to charger, then wait for the LED blinking to stop. Have a little patience! and DON"T RESTART with three button combo. Just boot into bootloader with Voulme up + Power key.
You have to follow these instructions carefully, exactly as i have written. Report back what happens.
enigmaamit said:
Well, the blinking signifies inadequate charge for a bootup. Wait till the orange LED stopsa blinking and turns on constantly... then boot into bootloader (Voulme up and Power button - don't let go of the volume button even after releasing the power button) - I don't want you to restart by using three button combo...otherwise you'll be back to the same problem, trying to boot into a broken OS... Just disconnect again and wait for it to switch off.... then reinsert battery, connect to charger, then wait for the LED blinking to stop. Have a little patience! and DON"T RESTART with three button combo. Just boot into bootloader with Voulme up + Power key.
You have to follow these instructions carefully, exactly as i have written. Report back what happens.
Click to expand...
Click to collapse
I did it exactly like you've written. Waited till phone, switch off, connected it and charged till led stopped blinking, disconnect, and try to boot it into recovery (vol up + power). Phone wibrated 3 times (screen did't react) and the same story. Now waiting for discharging and I'll try again.
Anyway thanks for your help and interest.
What else I can do? If the phone is not responding I can send it to warranty service. Meybe they will honour it... If not...ehss very expensive play.
adix631 said:
I did it exactly like you've written. Waited till phone, switch off, connected it and charged till led stopped blinking, disconnect, and try to boot it into recovery (vol up + power). Phone wibrated 3 times (screen did't react) and the same story. Now waiting for discharging and I'll try again.
Anyway thanks for your help and interest.
What else I can do? If the phone is not responding I can send it to warranty service. Meybe they will honour it... If not...ehss very expensive play.
Click to expand...
Click to collapse
Well, it that's not workin, Wait till the phone switches off again. Then configure adb, make sure it detects your device (use the command: adb devices) and then type the following at the cmd prompt :
adb reboot recovery
This should take you to recovery.
Ok, what can I say? Youe last thread worked!! I restared device, connect to computer - it was found as usb disk. In sdk tool divece was also found, this time as my ds Just restarted a recovery. First I saw an error in 4ext recovery, but it started with orange letters. I wiped all, formated all, recover old system, restart phone. And it works! Now I flshesd last jorgens CM7 and starting to config my phone. But a heart attack was close... Thanks man
adix631 said:
Ok, what can I say? Youe last thread worked!! I restared device, connect to computer - it was found as usb disk. In sdk tool divece was also found, this time as my ds Just restarted a recovery. First I saw an error in 4ext recovery, but it started with orange letters. I wiped all, formated all, recover old system, restart phone. And it works! Now I flshesd last jorgens CM7 and starting to config my phone. But a heart attack was close... Thanks man
Click to expand...
Click to collapse
You're welcome brother! And Congratulations!!
I know what you must have gone through till you reclaimed your phone. I remember the first time i was in a situation like yours... had to figure out this discharge the phone, LED blinking etc... thing on my own..., everyone else said battery pull was my only option. But i sitll didn't do it. I had around 60% battery remaining before this happened, so you can only imagine how many sleepless hours i spent waiting for the damn battery to run dry. http://forum.xda-developers.com/showthread.php?t=1271360
The important thing is to resist the temptation of pulling battery. Everything can be salvaged if you don't do that, but once you fry your eMMC, there is nothing anyone can do without physically repairing the phone.
May I suggest you edit the topic your OP and add the word [SOLVED] to the title. This will ensure anyone in trouble can easily locate this thread out of the cacophony on xda!
I flashed a UOT tweak that didn't go well. The DS is hanging on the bootscreen.
I made a backup, so I'd like to restore that.
However, I don't want to pull the battery if I can prevent it.
Is there a key combination to restart the DS?
[edit]
I can reboot using volume + , volume -, powerbutton holding...
But after that I can't get into recovery. Holding volume - , powerbutton right after that does not get me into recovery.
Any ideas?
1. Setup adb
2. Connect phone to pc
3. Type "adb reboot recovery"
If you can use the three key combination you can pull the battery out in that short period of time when the phone is out. Leave the battery out for a while and then put it back in. Then use volume down and power.
Try eyahl's method first though.
yes dan-fish, thats the only way that helps...
dan-fish said:
If you can use the three key combination you can pull the battery out in that short period of time when the phone is out. Leave the battery out for a while and then put it back in. Then use volume down and power.
Try eyahl's method first though.
Click to expand...
Click to collapse
Did that few weeks back when accidentally wipe everything(including sd card) and was stucked at HTC logo. I am glad to know that i didn't dmg the phone by pulling the battery. :silly:
eyahl said:
1. Setup adb
2. Connect phone to pc
3. Type "adb reboot recovery"
Click to expand...
Click to collapse
will save this in my notepad for future reference.
rain987 said:
Did that few weeks back when accidentally wipe everything(including sd card) and was stucked at HTC logo. I am glad to know that i didn't dmg the phone by pulling the battery. :silly:
Click to expand...
Click to collapse
From everything I've read, the problem isn't actually caused by pulling the battery - but by reinserting it quickly afterwards. If you do this then there is still latent charge around and that is when the damage actually occurs.
Having said that, it's obviously always better to not just pull the power on any electrical device if you can avoid doing so.
SimonTS said:
From everything I've read, the problem isn't actually caused by pulling the battery - but by reinserting it quickly afterwards. If you do this then there is still latent charge around and that is when the damage actually occurs.
Click to expand...
Click to collapse
Was just about to post it, refreshed and saw your post.
:good:
My Motorola Xoom won't turn OFF and stuck on M logo. Please, can you help me ?
I assume battery drain has turned it off for you by now. In the future, pressing the power button and volume up at the same time should help.
LaserChicken said:
I assume battery drain has turned it off for you by now. In the future, pressing the power button and volume up at the same time should help.
Click to expand...
Click to collapse
My tablet is OFF only when the battery is empty, it is normal, but the same thing happens when you get the power back.
By pressing the power button and volume up at the same time, not helping me. Just a quick restart ...
Thanks !
Minolta2003 said:
My tablet is OFF only when the battery is empty, it is normal, but the same thing happens when you get the power back.
By pressing the power button and volume up at the same time, not helping me. Just a quick restart ...
Thanks !
Click to expand...
Click to collapse
Can you go to recovery?
superbay said:
Can you go to recovery?
Click to expand...
Click to collapse
Yes, in recovery menu I accessed WIPE DATA/FACTORY RESET and WIPE CACHE PARTITION
I tried to REBOOT without SD Card also
Nothing change !
Minolta2003 said:
Yes, in recovery menu I accessed WIPE DATA/FACTORY RESET and WIPE CACHE PARTITION
I tried to REBOOT without SD Card also
Nothing change !
Click to expand...
Click to collapse
As far as i know your Xoom might be romless. Try flashing any rom from your sdcard and lets see what happens
superbay said:
As far as i know your Xoom might be romless. Try flashing any rom from your sdcard and lets see what happens
Click to expand...
Click to collapse
Can you teach me how can I flash the rom through Fastboot because ADB is not recognized by the computer, cannot install MTP driver.
Minolta2003 said:
Can you teach me how can I flash through Fastboot because ADB is not recognized by the computer, cannot install MTP driver.
Click to expand...
Click to collapse
Im sorry i cant. Im not familiar with such way since flashing from sdcard is more simple for me. Computer not recognizing device because of MTP driver is known for common issue though. Dont you want to try flashing from sdcard? Its easier if one is present.
superbay said:
Im sorry i cant. Im not familiar with such way since flashing from sdcard is more simple for me. Computer not recognizing device because of MTP driver is known for common issue though. Dont you want to try flashing from sdcard? Its easier if one is present.
Click to expand...
Click to collapse
Yes, shure, the sdcard is present, and I want to know how to do this, step by step. Thank you !
Minolta2003 said:
Yes, shure, the sdcard is present, and I want to know how to do this, step by step. Thank you !
Click to expand...
Click to collapse
Just copy the rom and gapps to the sdcard and simply flash them from the recovery. Or if you want to update the revovery, you can also put it in the sdcard and flash it before you flash the rom. Wipe cache lastly
superbay said:
Just copy the rom and gapps to the sdcard and simply flash them from the recovery. Or if you want to update the revovery, you can also put it in the sdcard and flash it before you flash the rom. Wipe cache lastly
Click to expand...
Click to collapse
This is my recovery menu:
Android System Recovery <3e>
reboot system now
apply update from USB drive
wipe data/factory reset
wipe cache partition
1. Please tell me how can copy files, flash or update from recovery with this options ?
2. You know the download links for rom, gapps and update files ?
Thanks !
Minolta2003 said:
This is my recovery menu:
Android System Recovery <3e>
reboot system now
apply update from USB drive
wipe data/factory reset
wipe cache partition
1. Please tell me how can copy files, flash or update from recovery with this options ?
2. You know the download links for rom, gapps and update files ?
Thanks !
Click to expand...
Click to collapse
Gee so sorry. I thought you have custom recovery like cwm or twrp. Apparently you still have stock recovery there. So i guess you need to download the stock image for your Xoom and, yes you are correct, flash them from fastboot then. Long long time ago, i ever did this but i dont really remember all things. But all i know is that I followed steps from here http://androidforums.com/xoom-all-things-root/653230-return-your-xoom-stock.html. Pay attention for post #37 since all commands i applied are from there. If you need different version of image, you can try looking which fits yours here http://forum.xda-developers.com/showthread.php?t=1049485. As i told you before, ive done this long time ago so i dont remember what i did at that time but i succeeded by following the steps. However, im here to help you as far as i can. Keep me updated with your process there
superbay said:
Gee so sorry. I thought you have custom recovery like cwm or twrp. Apparently you still have stock recovery there. So i guess you need to download the stock image for your Xoom and, yes you are correct, flash them from fastboot then. Long long time ago, i ever did this but i dont really remember all things. But all i know is that I followed steps from here http://androidforums.com/xoom-all-things-root/653230-return-your-xoom-stock.html. Pay attention for post #37 since all commands i applied are from there. If you need different version of image, you can try looking which fits yours here http://forum.xda-developers.com/showthread.php?t=1049485. As i told you before, ive done this long time ago so i dont remember what i did at that time but i succeeded by following the steps. However, im here to help you as far as i can. Keep me updated with your process there
Click to expand...
Click to collapse
Your advice was definitely the solution, but I did not get to do anything because my Xoom is stuck in black screen and cannot power it on
I do not know the cause. It's incredible what happens !
Suddenly started to reboot itself, then stopped completely. It was only connected to the original charger and USB, ready for install drivers and flash.
The power led is ok (white and green, after few minutes) I removed the battery, the voltage is correct, and nothing ...
Do you have any idea?
Minolta2003 said:
Your advice was definitely the solution, but I did not get to do anything because my Xoom is stuck in black screen and cannot power it on
I do not know the cause. It's incredible what happens !
Suddenly started to reboot itself, then stopped completely. It was only connected to the original charger and USB, ready for install drivers and flash.
The power led is ok (white and green, after few minutes) I removed the battery, the voltage is correct, and nothing ...
Do you have any idea?
Click to expand...
Click to collapse
Well that's new for me. Did you have that after you do the whole process? when did you get the black screen? Cant go to fastboot either?
How are you charging? wall charger how long? Which Xoom do you have?
Sent from my Motorola Galaxy s3 using xda app-developers app
superbay said:
Well that's new for me. Did you have that after you do the whole process? when did you get the black screen? Cant go to fastboot either?
Click to expand...
Click to collapse
No, before, when my tablet was with my initial problem (Won't turn OFF and stuck on M logo).
Suddenly it started to reboot itself and stuck each time at M logo, then stopped completely, after 4-5 cycles.
During this time, I followed the steps in this link till the point 6 (reboot your computer, plug in your Xoom and allow the drivers to install), with WiFi Xoom Restore downloaded files.
Black screen, no fastboot, no android recovery, nothing, just a green light when charging with original wall charger (SPN5632B)
Chadwick108 said:
How are you charging? wall charger how long? Which Xoom do you have?
Sent from my Motorola Galaxy s3 using xda app-developers app
Click to expand...
Click to collapse
With Original Motorola Wall Charger SPN5632B, no long time because my tablet was almost always connected to the charger.
The battery has 8 volts and charger 12 volts.
If I disconnect the charger and hook it back, the white light stay bright about 10 minutes, then turns green.
Motorola XOOM Wi-Fi - MZ604
From what I remember, last days when charging, the Xoom jacks area was warm, now is cold. Maybe it is normal to be cold if the tablet is fully charged now, I don`t know exactly if this is a good indication for helping me...
Minolta2003 said:
No, before, when my tablet was with my initial problem (Won't turn OFF and stuck on M logo).
Suddenly it started to reboot itself and stuck each time at M logo, then stopped completely, after 4-5 cycles.
During this time, I followed the steps in this link till the point 6 (reboot your computer, plug in your Xoom and allow the drivers to install), with WiFi Xoom Restore downloaded files.
Black screen, no fastboot, no android recovery, nothing, just a green light when charging with original wall charger (SPN5632B)
Click to expand...
Click to collapse
Green light indicates that the battery is full. Your case is not an ordinary one though. What happens if you press volume up+power button? Does it even boot? At least to the fastboot?
Anyway, previously you said that you removed the battery. Did you tear up your Xoom?
superbay said:
Green light indicates that the battery is full. Your case is not an ordinary one though. What happens if you press volume up+power button? Does it even boot? At least to the fastboot?
Anyway, previously you said that you removed the battery. Did you tear up your Xoom?
Click to expand...
Click to collapse
Yes, it is very difficult to understand what happened in this case. No logo, no boot, no fastboot, is power off
Now (Volume up + Power) = Nothing, same black screen
Before (Volume up + Power) = Reset
Yes, I tear up my Xoom
Minolta2003 said:
Yes, it is very difficult to understand what happened in this case. No logo, no boot, no fastboot, is power off
Now (Volume up + Power) = Nothing, same black screen
Before (Volume up + Power) = Reset
Yes, I tear up my Xoom
Click to expand...
Click to collapse
Im afraid i could not give you further suggestion other than removing sdcard and trying booting it up again with any means or keep pressing the volume up+power button for at least a minute. If it doesnt give you any good, well then sorry im done by this point.
Any history about the tablet? The one that pushed you to tear up the device maybe? What happened before the tablet's gone weird?