i put xandroid on my pure, installed, then boot screen, flying androids write xandroid on screen, loop stuck at this point, no boot, no nothing, just flying droids, waited 45 minutes, no change.
what did i do wrong, how do i fix it.
do u have try take out the batt, and repeat the process.
same problem here. taking out the battery doesn't help
Related
I tried to root my US G1 using the Cyanogen guide (http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod) and the phone has been stuck on a screen showing an arrow coming out of a box and a phone for more than an hour. I've rooted using this guide before and this has never taken this long.
After I applied the latest Cyanogen version and tried to reboot, it got stuck on the screen. If I take the battery out and try to restart, will that destroy the phone? I have a bad feeling it's already broken but I want to do something rather than just sit here staring at a screen for another hour.
removing my post, it made sense to me, but maybe not the OP and I cant word it better.
Hi All,
While on a business trip last week, my Tilt 2 (at the time, running the April 14 Energy ROM), my phone--for lack of a better word--crashed on me.
Everything had been working fine, I was sitting there with my phone connected to my laptop via a USB cable, and out of the blue, for no apparent reason, my phone re-booted, and never came back up. It would get to the splash screen, start loading the OS, reboot mid-stream, and get stuck in a loop. Weirder still, if I pulled the battery, let the phone sit, then put the battery back in, hitting the power button did nothing--even with the phone plugged in to power. On top of that, even if the phone was off, after a few minutes, it would power itself back on randomly, and get stuck in the re-boot loop. Very weird.
So, when I got home, before heading to the AT&T store and asking for a replacement, I thought I'd try to restore the phone myself.
At first, I pulled the battery, then stuck it back in, and sat there holding the volume down button, waiting to put the phone into bootloader mode. That worked, but even in bootloader mode, it would randomly re-boot. So, I started the process again, and immediately plugged the phone into my computer while in bootloader mode and ran the Task 29 tool. That completed properly.
At this point, I popped in another battery I had laying around and just let the phone charge for a few hours. Then, for the heck of it, I re-ran the HardSPL tool. Re-Flashed to the .91 radio (it was already on the phone), and then flashed to the latest Energy ROM.
Since then, my phone has been better than ever. Seems faster, battery life is better (Went three days without having to charge it), no dropped calls, and no weirdness with the latest ROM (that I've found so far).
Does it pay to REALLY start fresh from time to time, and re-flash everything on the phone?
Thanks for any input.
I have no idea, but hopefully the WinMo experts will see this and have an idea, so here's a bump for you. Most of my computer expertise revolves around Unix, Linux, and a bit of Windows, not so much these phones.
I do know that task 29 is awesome, though. It seems like DBAN for your phone...
DBAN=Darik's Boot and Nuke. Look it up.
I don't know what happened with your phone, sounds like something broke in the area of booting.
I don't think you should need to re-flash HardSPL radios just for the sake of it, but I'd strongly recommend task29 every time you flash a new ROM.
bricked my TP2
My TP2 seems to have a similar problem which I haven't been able to fix it just yet. The bootloader reboot loop is too short to succesfully run task 29 and flashing it using the microSD gets stuck around 40%
during bootloader mode there's an unreadable errormessage since it's on the same line as some of the usual information.
any thoughts/suggestions would be very welcome since i can't afford to send it to the factory.
cheers.
after doing a little rerading.
I found a link about flashing roms and another about a 3 button download mode.. and that you should check that this mode works... before you even try to flash so after reading it I tried it out...
yes my unit showed the correct screen but thats a far as the topic went..
and thats exactly where my phone sat for quite a while, after about 5 minutes of this screen being on my hone it progressing I figured that since there was nothing for it to download that it would exit out after a few more minutes and not exiting I decided to remove the battery as nothing else seemed to work....
yes I did read do not turn off unit.. however I was not downloading anything as the sim was removed and the wifi was turned off on my router.. so I could not see that this would cause harm..
however now my phone is in a boot loop...
I pulled the batery for another 10 minutes and replaced still the same... can sombody please help me..
I have searched and found nothing....
Well I fixed my issue.. I went intothe recovery mode adn selected reboot system.. the top option.. and all is good.. I would have thought that removing the battery and restarting the system wouldhave been the same but it seems that the system must read stored info. on reboot..
Yay all good I feel I learned something...
I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
GreenMunky said:
I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
Click to expand...
Click to collapse
If a factory reset does not fix the issue, all I can suggest is find the thread "Return to Stock" and follow the instructions to flash the entire stock SBF for your carrier. This should fix any corrupted files, if present. Either option WILL erase everything, so backup anything you need first.
Good Luck
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
KJ said:
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
Click to expand...
Click to collapse
Nope, phone had been off the charger only a few hours, still had 85% or so. I actually tried plugging the phone in while it was booting up to see if an extra jolt of juice would somehow help it to fully boot up... made no difference. After 6-8 failed boot attempts, it finally booted up and has been running fine since... although I have yet to try to manually reboot it.
Well, if it acts up anymore...I'd consider a full wipe and return to stock. Same android version you're on now of course.
Otherwise...probably a fluke. ?
The first time I got my phone was about two days ago. I got the MotoG2 from ebay at such a cheap price ($20), I won the auction and so yeah (26 bids). HOWEVER, this is what the description says from the seller:"This smart phone sells working as-is because screen is cracked, LCD has liquid damage, other components work as they are supposed to. SIM slot/cellular feature has not been tested on any networks. Customer data have been deleted from smartphone. *Battery life and performance on used electronic devices can not be guaranteed. * Entire screen is cracked; there are many scratches and scuffs on the bezels and on the back side. Smart phone sells with battery and non-OEM box.
I finally got it and shipped to my house, on'ed it and everything worked fine the camera, audio, basically it was brand new except for the front screen that is shattered. Later on, i decided to root my Android phone with KingRoot on kingroot.net and it was fast and easy. I didn't know what to do after, my friend told me about it and you can do many things with root. My phone was successfully rooted. I was browsing Google Play untill i saw an app that says "boot animations" I was like "Cool, gonna test it out" so it did install and i opened it. It has a ton of animations and i chose one to be as my boot animation. Unfortuanately, I so stupid forgot to backup the previous original (Motorola boot animation). It now takes a bit longer to boot up (idk whether it was the animation itself, or the fact that my phone is now rooted). I decided to uninstall the root, hoping the boot animation was gone(also kinda blurry). Well it did not, but i was like whatever. Phone still worked fully, and decided to stuck it up with that boot animation.
Now that my phone is unrooted, i decided to root it again since it did not work. I tried to install an app that AdAway and it did work. Ads were gone and i was happy.
Until. A motorola screen popped up saying it has a system update. I forgot what the update is about. All i remember is something do with "stabilizing and other stuff" and takes about 10 min.
So I did install it, phone off'd and on with an android logo with a progress bar. After it was complete A picture of an android lying down with an exclamation mark saying "Error". I was like wtf, what happened. I couldn't boot up my device because of this error. I off'd my phone and then on'd it again. It now says "no command." with the same android guy. I gave up and tried to "wipe data and personalized content" "THIS CANNOT BE UNDONE" so i just accepted it. I off'd my phone and boot it up. There was an infinite boot loop, and tried to do as much as i could. But it always led to this(phone on's then offs a few seconds later then on a few seconds later and a few seconds later An android guy says"Erasing..."few seconds later phone off's again. REPEAT!" It was like this and left it the entire night with a cable charged to it so it will not die. So its now unusable and i do not know wtf i should do. The same friking Android guy saying "erasing" i dont think its erasing because when i hold the (power button + Volume up) it says "data wipe complete". It was just repeating over and over and over again with the say frikin vibration everytime it turns on. Tried to Enter Factory, Recover, normal recovery, wipe data again. Basically i did everything that was reasonable that would fix this boot loop. HELP PLS!
Sorry have bad english.