Related
My Xoom refuses to turn off completely. Every time I do anything related to shutting it down, it simply restarts. CWM restarts it, holding the button restarts it, QuickBoot restarts it. It hasn't always been like this, but soon after I started to root it and such, it stopped shutting down.
It might also be of help to note that I cannot install any OTA update or relock my bootloader. OTA updates simply fail at a screen with an android logo with an exclamation point, and if I relock the bootloader, the Xoom simply won't boot until I unlock it again. I have no idea if any of these problems are related to one another.
I'm currently using the Tiamat Xoom ROM 2.0.1, but it's done this for almost as long as I can remember (probably ever since I rooted the first time). It might also be worth noting that I flashed the wrong images the very first time I rooted it, but I've since flashed all of the appropriate images, so it should theoretically not be an issue.
Athenon87 said:
My Xoom refuses to turn off completely. Every time I do anything related to shutting it down, it simply restarts. CWM restarts it, holding the button restarts it, QuickBoot restarts it. It hasn't always been like this, but soon after I started to root it and such, it stopped shutting down.
It might also be of help to note that I cannot install any OTA update or relock my bootloader. OTA updates simply fail at a screen with an android logo with an exclamation point, and if I relock the bootloader, the Xoom simply won't boot until I unlock it again. I have no idea if any of these problems are related to one another.
I'm currently using the Tiamat Xoom ROM 2.0.1, but it's done this for almost as long as I can remember (probably ever since I rooted the first time). It might also be worth noting that I flashed the wrong images the very first time I rooted it, but I've since flashed all of the appropriate images, so it should theoretically not be an issue.
Click to expand...
Click to collapse
Question, Have you cleared your Dalvik Cache and/or trying another ROM to see if maybe it was not the Tiamat Xoom ROM that could have been corrupted in the flashing process? I am also curious if you have attempted to stock flash and then retry the ROM? You also should know that doing OTA Updates to the android devices that do not have stock ROMs (aka the ROM that you bought with the phone/tablet, no super user and so on) should not be updated with the OTA updates because it can corrupt the ROM that you have. I would suggest, that because Tiamat Xoom Rom 2.0.1 is now labled as [ROM][OMG] Team Tiamat Xoom Rom 2.0.1 Manta Ray [OBSOLETE] (as gotten from the link -- http://forum.xda-developers.com/showthread.php?t=1146153 ) you might want to try a newer version or different rom, OR try to redownload the rom and start over. I would also suggest that if you are going to do that, please clear cache
If I was unable to help you, please let me know and I will try and help you till the issue is solved or someone else has a better answer to help
I've restored to stock and then to the Tiamat rom 2 or 3 different times now, none of which resulted in the Xoom being able to shut off. If memory serves, the Xoom won't even shut off when I'm on completely stock images.
Have you cleared the Devlik Cache and other Cache before each install and as well as after install of the roms? because flashing rom after rom without actually clearing the files could result in residue of older files and corrupting a ROM. I would also look into a different kernal or maybe that your battery/charging cable is bad.
I know with my Ally dev phone it likes to just turn on (with or without a charge/hard boot off) when the phone is plugged into the wall socket (as it is not the normal wall adapter cause I bought the phone off ebay) so the adapter likes to force it online... can you turn off the Xoom when it is or is not plugged in?
Cranvis said:
Have you cleared the Devlik Cache and other Cache before each install and as well as after install of the roms? because flashing rom after rom without actually clearing the files could result in residue of older files and corrupting a ROM. I would also look into a different kernal or maybe that your battery/charging cable is bad.
I know with my Ally dev phone it likes to just turn on (with or without a charge/hard boot off) when the phone is plugged into the wall socket (as it is not the normal wall adapter cause I bought the phone off ebay) so the adapter likes to force it online... can you turn off the Xoom when it is or is not plugged in?
Click to expand...
Click to collapse
The rom install automatically wipes the two caches, so I haven't worried about it. There is no case in which my Xoom has been able to turn off for months, plugged in, not plugged in, or ANY other case. I asked solarnz on IRC about the problem, but he had no idea :/
Athenon87 said:
The rom install automatically wipes the two caches, so I haven't worried about it. There is no case in which my Xoom has been able to turn off for months, plugged in, not plugged in, or ANY other case. I asked solarnz on IRC about the problem, but he had no idea :/
Click to expand...
Click to collapse
You could, in all and all, have a bad device that has a power surge/fault/something where two wires are jumping/something else and just need to contact Motorola and ask them for help (after of course you make sure you reflashed back to 100% stock). These tablets, heck any computer like device, are so fickle to power that they will do anything if there is a right charge... good example is my Dev Phone I mentioned earlier... Plug it in off, and it boots up... you just might have had a bad tablet to start with and it took it a tiny bit to show it's ugly bug filled head... I am sorry that I can't help you any more on this, but I really do think you need to contact Motorola before your warranty is up... it takes only one wire to be solder incorrectly to mess up a whole system... trust me, I have had computers burn up on me and friends because of exposed wires, incorrectly soldered wires, and let alone, DUST of all things...
I hope you can get Motorola to help you out, because I am suspecting that it is a hardware issue... not a software...
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Kopiok said:
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Click to expand...
Click to collapse
Try the solution in the last few posts on this thread. http://forum.xda-developers.com/showthread.php?t=2465695
I hope you get more knowledgeable advice than mine but, were I in your situation, my primary goal would be to get back to STOCK. Forget CM and modding for now. Either through TWRP or through the recovery settings on the phone itself I'd get to where I could do a factory reset. If you're continuously able to boot into TWRP I don't see how your phone could be bricked. My experience is, if I can get a phone to do ANYTHING I've got a shot at figuring out how to get out of whatever mess I've created. I don't know if this could be a factor but I'd put in a different micro SD card too, in case there's something on the card you've got in there.
Just an update. So, I got it to go back to fastboot this morning and I tried using the Razr Utility to flash back stock and stock recovery, but I got a "Failed" line with the reason "Remote Failure". Not sure what that's about. When it reset it got back to the Cyanogenmod boot graphic, but it never started. I left it there for a good 12 minutes.
Right now it's sitting in TWRP. I'm going to let it charge to 100% (it was a little less when I tried all of this) and attempt it again at 100% battery. Thanks for the help so far!
So, I tried using the Razr Utility to flash the system, kernel, radio and for system it was unsuccessful (something about too many threads or strings, something to that effect), but the rest said OK. Now my phone doesn't seem to turn on. My computer still makes the device plugged in sound when it's plugged/unplugged, but I cannot get the screen to show anything or seem to turn on the phone.
Is this it? Is it... bricked!? ;-;
Edit: I ordered the Factory Adapter as a last resort sort of thing. This is lame.
Edit Edit: I've seen the boot logo since my last edit! But... it's not coming back and I still can't even bring up the bootloader. I don't know why it will sometimes turn on or sometimes not. In any case, I'm now hopeful that not ALL is lost.
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
That's the plan! One odd thing happening now... My phone's screen isn't showing anything, so I assumed it was off. I left it unplugged and went to see a movie..... and the phone is still warm. This leads me to believe the phone is still drawing power, for some reason... God this is weird. I'll wait for the adapter and try again. Thanks for the help!
cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
according to the packaging on mine from tbh a chinaman made it, just sayin
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
cellzealot said:
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
Click to expand...
Click to collapse
thanks for making it either way, better to have and not need.
havent had to use it so far
bweN diorD said:
thanks for making it either way, better to have and not need.
havent had to use it so far
Click to expand...
Click to collapse
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
cellzealot said:
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
Click to expand...
Click to collapse
how many thousands, and whats the plan?
I got the Factory Adapter and used RSD Lite to flash stock. And it works! Yay! It's starting up reliably and everything.
Except... it won't start up without the cable attached, and the battery icon has a big question mark on it. It also won't connect to the cell network (but does connect to WiFi). What do I do now?
Edit: So I noticed that while the battery status said "Unknown", it did go from 2% to 3% charge level when I plugged it in normally for a little. My plan at the moment is to try leaving it plugged in for a while and then try taking the OTA update to see if that fixes everything. Good plan?
Edit Edit: Never mind! I just had to let it charge for a bit. It seems to be back in working order, now! Thank you so much for all the help everyone!
That is exactly what is supposed to happen. Congrats on fixing your phone!
The factory cable/adapter does not charge the device but powers it directly, allowing it to boot no matter what state the battery is in or even without a battery at all.
You cannot charge in bootloader, which is why the cable/adapter is so valuable. Once the device can boot/charge normally then you are all set.
Alright, I hate being that guy. You know, the one who posts the same question as 50 other people because he is too lazy to search. But in my defense, I have spent the last three days pouring over thread after thread and still can't find the answer, so please be patient and gimme a break!
So, I'm stuck in CWM 5.8.3.4 loop after flashing Katkiss and not knowing I couldn't use the "boot to recovery" option. I've got no access to my micro SD card and my x64 Win 7 won't recognize the TF101 so I can't put my own recover zip on. Cold boot goes to the screen that lets me boot Android or Wipe. If I pick Android, it hangs (for hours). I've wiped everything and reinstalled Katkiss, Revolver, Revolution, but I have the same problems.
Is there a thread that starts from the BEGINNING of the fix and sees it through? I've found dozens of threads that say, "Just input (code), flash, and you're done!", but I guess I'm not that far along. I've bricked Dinc/Dinc2, Razrs, etc., but never had trouble fixing them like this TF101.
I've got ADB, JDK, Ubuntu, etc. since I've tried numerous times. Also, I've had no luck with the one-touch fixes. I know I'm missing something easy, I just can't figure it out.
Thank you.
Incidentally, I've tried ***http://www.transformerforums.com/fo...ry-bootloop-fix-tested-my-c10-windows.html*** , but the SDK files come in a zip, not exe and none of the files execute/install in such a way that will let me input commands. I know I'm missing something because a soft brick isn't that big of a deal.
Huh. I don't know what happened, but it involved me cleaning the screen, accidentally pushing buttons, and rebooting, and now it works. No clue, but as long as I never shut it off again, I'm set!
You're gonna need to get the PC to recognise it to fix it I'd say
Easiest way would be using Easyflasher to get TWRP recovery installed, it sounds like you have stock recovery installed at the minute
http://forum.xda-developers.com/showthread.php?t=1688012
Few people have needed new cables to get the PC to recognise the TF again, might just be needing the correct drivers though which are also linked on that page
Basically install the drivers, put the TF into APX mode,
(Vol Up & Power from powered off state while plugged into the PC)
Then run Easyflasher as admin and choose to flash TWRP (CWM is probably the reason for the bootloop, it doesn't play nice with JB ROMs)
Once you have TWRP installed, flash whichever ROM you want from new recovery and you should be good to go
I appreciate the suggestion, but that isn't doing it. I have the tab booted up and recognized by Windows, but when I try to update to a different CWM or TWRP, nothing happens. I can reboot into CWM 5.8.3.4 all day, but it won't say anything about any different recoveries I've tried to install, though the recoveries appear to be installing correctly according to the dialog given on the tablet.
I've also tried running NVflash, but nothing happens (apx drivers installed). The BAT file briefly says USB not recognized and closes.
Further, I've tried Easyflasher / one click root+recovery and I just get messages saying "ADB server out of date. Killing." The tab still reboots, but upon rebooting, it gets stuck in CWM 5.8.3.4 unless I force cold boot.
I guess the best way to describe this is to say that no matter what I do with the tab or different recoveries, I can't get rid of CWM 5.8.3.4 and no matter what I do, it default boots into CWM.
It default boots into CWM.... I think that is the key here
I remember something about that from a while ago, having to hold Power & Volume Down to boot normally, as if the OS and Recovery partitions were reversed
Unfortunately I can't remember the solution atm, but if you head over to transformerforums.com or give frederuco a PM from here or over there, Im pretty sure I remember him having a solution some time back
I shot him a message. Thanks for the suggestion.
I swear all I did was root, install Katkiss, and reboot into recovery. Is this a common problem to have THIS much trouble with such a simple process? I know now that booting into recovery can cause a loop, but this seems like way too much.
It's having CWM as your recovery when you flash a JB ROM that causes the problems
CWM & JB = Problems
TWRP is the recovery to use once you get out of this mess, good luck
Just for reference I have a p5113 model.
A while back I put Cyanogen on my tablet. A few months ago I cracked the screen, only a bit on the corner, of course I can't stand cracked screens so I ordered a replacement. When I installed the screen everything connected fine and dandy so I tried to start it up, but when I did the touch function didn't work. I thought maybe it was just a bad screen that I had ordered, so I got another. When I got the second screen in I replaced it, but this time it was doing the same thing as before where the touch wasn't working! I made sure everything was connected okay and also checked for anything damaged, but everything seemed fine. For some reason I thought maybe hard resetting it would help, but it didn't. At this point I was just trying to get the stock 4.2.2 firmware back on it. I downloaded the firmware, used ODIN to get it onto the tablet. When it restarted after the firmware was loaded on, it was stuck in a bootloop. I heard that it may just need to be factory reset again so I tried to get into recovery mode, but only goes into ODIN/Download mode, which is what my final problem is here.
TL;DR Tablet will not go into recovery mode. Only ODIN/download mode.
I haven't been able to find ANYONE else that has had this problem before. So if anyone knows the source of my problem, I would be very appreciative of your help.
Well you could have fried the capacitive touch circuit with a static charge I have no idea what your skill level is also you could have a bad image or you could have bonked the hardware and it doesn't detect critical boot hardware I'm not that well versed in firmware related boot issues but hopefully some helpful nerd can give you a hand you could also just try again aster you download a new IMG
Sent from my toaster
Samwise13 said:
Just for reference I have a p5113 model.
A while back I put Cyanogen on my tablet. A few months ago I cracked the screen, only a bit on the corner, of course I can't stand cracked screens so I ordered a replacement. When I installed the screen everything connected fine and dandy so I tried to start it up, but when I did the touch function didn't work. I thought maybe it was just a bad screen that I had ordered, so I got another. When I got the second screen in I replaced it, but this time it was doing the same thing as before where the touch wasn't working! I made sure everything was connected okay and also checked for anything damaged, but everything seemed fine. For some reason I thought maybe hard resetting it would help, but it didn't. At this point I was just trying to get the stock 4.2.2 firmware back on it. I downloaded the firmware, used ODIN to get it onto the tablet. When it restarted after the firmware was loaded on, it was stuck in a bootloop. I heard that it may just need to be factory reset again so I tried to get into recovery mode, but only goes into ODIN/Download mode, which is what my final problem is here.
TL;DR Tablet will not go into recovery mode. Only ODIN/download mode.
I haven't been able to find ANYONE else that has had this problem before. So if anyone knows the source of my problem, I would be very appreciative of your help.
Click to expand...
Click to collapse
sounds like a damaged digitizer to me.
may as well get a new tablet as digitizers tend to cost almost the same as a new device...
now... recovery...
this may sound redundant but try flashing the firmware again. when it flashes make sure it says "recovery.img" or similar at some point in the Odin log.
be sure to use the correct pit file and the repartition check box when flashing.
there are usually two or more firmwares per tablet so if one fails to boot recovery try the other.
the site I find that has reliable files is samsung-updates.com but be prepared for slow downloads averaging am hour and a half.
Sent from my SGH-T999 using Tapatalk
I have a Asus TF700T and while it was in my car in its case it apparently started on it's own and ran down a full charge to about 10% so it must have been going for hours which would explain why it got so warm. I could not shut it off so it stayed on until there was no more charge. I was then able to charge it. When I hit the start button it starts but just hangs up in the animated boot screen and goes no further. Then I tried the on button with the volume button and got into TWRP. I really don't know anything about TWRP but I looked around and tried rebooting and a few other options but nothing changed. Still stuck on the boot up screen.
So I'm willing to learn about my tablet now that I am forced too. Can anyone please point me to the right solutions and can anyone tell me why it started on its own? You help is much appreciated. Thanks.
More likely some app never shut down and got hung up, running the battery down. Unless you live in Phoenix and had in your car in full sun heating it up to 140 F...
To give you any advice worth a damn you need to provide:
bootloader version
TWRP version
what rom you are running
In lieu of that, and to possibly get the tab out of the stuck boot, you could just do a factory wipe in TWRP.
Choose the Wipe option and swipe the button - let it finish and reboot system. That will wipe all user installed apps and settings, but leave your personal files untouched.
Let us know where that got you.
For general info and to get your PC set up for fastboot/adb you could peruse my guide here: http://forum.xda-developers.com/showthread.php?t=2688891
Thanks for the info. I will charge it back up and try your wipe suggestion.
As far as the other info you need, I'm not sure how I can get that if it won't boot, except probably the TWRP version. Can you suggest a way to obtain that info. As far as what Android version I was using I'm not really sure about that either. I bought this used in early 2013 and the version was whatever was around back then. Geez, I'm a little embassased. It's my most important tool and I know nothing about it. It's as if you asked me my sons name, age, and birthdate and I couldn't tell you. Back when I used a desktop, I knew everything about it but now, shame on me.
The TWRP version would help somewhat. Assuming you have a TWRP version compatible with your bootloader it would give us a hint on what you were running. But if you can boot to the bootloader with Power and Volume Down, just read the tiny script. Your BL version is right there.
But if TWRP is still working you could use it's build-in file manager to copy all your data off internal storage to a microSD.
Then download the latest firmware from Asus, unzip the file once, resulting in another zip and place that zip on a fat32 formatted microSD.
Flash the firmware in TWRP.
That would get you onto the latest bootloader, but would also install the stock recovery and rom.
Next just decide which custom rom you want to run, find the correct TWRP version, flash it in fastboot and then flash the rom.
Who would of thought that a menu option called "Wipe" would get me back up and running? Seems to me that Wipe would just blow away everything. You assistence is greatly appreciated.
Fogot to mention that I,m also going to follow your suggestions with the lastest firmware and custom rom but I have to put that is on hold until I have a backup tablet so I can continue doing my Ebay work and learning more on this terrific website. Thanks again for your help.