Tag Info

New answers tagged

0

Have you tried this app from Chainfire? https://play.google.com/store/apps/details?id=eu.chainfire.liveboot From the description, it shows a logcat of the boot process over the boot animation.


0

If you have been waiting an excessive amount of time for your phone to boot (eg. leaving it overnight to boot) but it is still at the boot animation, you may be in bootloop. This is when the phone fails to boot due to some errors in the /system partition. As a preliminary measurement, you should perform a factory reset (or wipe /data) to see if that helps. ...


2

Real Reboot Works on Android 2.1 - 4.2.1 No Root 4.2.2 and up needs root. For a PC method you will be using Android Debug Bridge, commonly called ADB. Here is a link for a download. It's from the XDA Forums. Read the page while your there and get some good insight on ADB. After installed to the computer, open a command prompt (L shift + R mouse click) ...


-1

If you're rooted : Just search for any app that restarts the phone. Just search on play store - "Restart". That'll do the work... If you're not rooted As HasH_BrowN told, adb is the solution. The first step is to have USB debugging turned on, which you have. Now, follow these steps : Install adb and your phone's drivers on your PC/Mac/Linux ...


0

I dont know what happened but surprisingly the tablet booted on its own. I did not do anything new. It is showing in Device manager as Alcatel ADB Android Device and I was able to see the memory card contents in My Computer too. Battery level was 74%, battery charging blue LED came back on, phew! The only negative thing I saw was that it gave a message on ...


1

Try this: Install ADB and fastboot. If you already have the Android SDK, you can find these tools in dir_to_sdk/sdk/platform-tools/. If you don't have the SDK, here is a direct link to Minimal ADB and Fastboot (for Windows). Install your device drivers if applicable. Run the following code from your ADB/fastboot directory: fastboot oem unlock fastboot oem ...


1

If it is stuck in bootloop, I suspect corruption in /system. You should either reinstall the stock ROM or install a custom one. The first thing you will need is a custom recovery. According to this post by flowish at XDA-Developers, you can do this by follwing these steps: Download the recovery (recommended latest build) extract and put to your ...


0

The initial input is read by the bootloader to see which partition to boot. Vol- will trigger bootloader, while no input will trigger ROM partition. The bootloader is initially installed by your OEM. No matter what version of Android you have, you still have the same bootloader until you either update your bootloader or install a custom bootloader. The OEM ...


0

Yes, you can boot into recovery without build.prop. You can, in fact, boot into recovery without anything in /system (actually, recovery and bootloader are the only things you can boot into without anything in your /system.); build.prop and /system are only used when the ROM is loaded.


0

Boot into recovery mode by holding the Power & Volume Up buttons on your phone. (if Volume Up doesn't work, try Volume Down). I've used this method to get an unresponsive device to respond.


0

I believe I have a similar problem and shall update this answer as I find more information. What variant of Samsung Galaxy S II do you have? These steps could help: Fresh reboot by pulling battery, SIM card and any external SD card out for a while (some sources I have read say to wait over an hour). Clear the cache partition (this is safe, no data loss): ...


2

Posting this not so much for the asker, since it was asked ten hours ago, but for others who find this question: Lollipop's first boot can take a long time. On my Nexus 4, after the OTA update from 4.4.4, it took about half an hour. At least 10 minutes of this was spent in the "flying colours" boot screen. I'd make sure it has power, and leave it for at ...



Top 50 recent answers are included