I just did a system update on my phone this weekend and found that after the update the phone will not boot, I have tried everything to get it to boot but it just won't boot, I have also attempted to plug it into my computer to re-install the OS but the computer won't recognize it as it doesn't fully load the OS.
I rooted my Samsung Galaxy S4 (SCH-I545), then I decided to install a custom ROM since the default TouchWiz rom is slower than a turtle stuck in a pile of wax. I installed Safestrap 3.71 (TWRP v18.104.22.168) and by mistake flashed my stock rom. Now my phone won't boot into any ROM since that is corrupt, but it still boots into recovery (that's a good thing I suppose). I have tried a number of Safestrap compatible roms (omni, cm, beanstalk) but they either end up giving me a black screen or a very weird looking pixelated blue/cyan screen. I have to remove the battery to reboot my phone. I tried using adb to wipe the data aswell but nothing works beyond recovery. I have to rely on adb to push and pull data to and from the phone.
I recently downloaded and flashed my Qmobile A10 with this ROM URL....
And after flashing it I had a RAVEN ROM first which was getting stuck at boot logo. Even after the flashing I get to see the RAVEN ROM boot logo and then I see the Canvas(The ROM I installed) boot animation. Problem is that I don't get signals. They keep dropping.Further more I don't get to go to recovery again. Everytime I try it just factory resets the mobile.I tried going to Recovery mode by:
1) Holding Vol UP + Vol Down + Power Button > Vol Up 2) Mobile Uncle Tools again 3) ROM Manager 4) Terminal Emulator 5) Some flashbit.bat file I found for my phone 6) SP Flash Tools
All give the same result that my phone is factory reset. Except SP Flash, even after installing drivers it prompts that the drivers may not be installed and a USB error 8100.
The phone will not boot up.Tryed to go to download mode ( doesnt work )
tryed to connect to PC doesnt work
When i go to fastboot mode , on the PC is only fastboot gadget located in devices and printers. can't do anythink with it.I am using win7 x64 ultimate.Also the recovery mode doesnt work it always shows some Yellow triangle with a phone and nothink happens.
Link to the phone: "ahappydeal. com/ product-94000.html" without quotes and backspace
I write because I have a problem with a gt-i5800, the phone will not boot, the pc does not recognize the phone, I've installed the firmware Kirillos for recovery, but the phone never gets started, always goes into recovery mode, loop constant.
I read somewhere that you have to flash the bootloader but I also odin recognizes the phone, then I would get him through the recovery. The file should be in. Zip.
I have a rooted HTC Desire s, I did a software update through "phone, info, check for updates",(android 2.3.5 sense 3.0) now my phone wont boot, it's stuck on the HTC boot screen., I've tried updating from SD card (various custom stock roms) but I always get an error message.
-Revolutionary- SAGA PUT SHIP S-OFF RL HOOT-6. 98.1002 RADIO-38.02.00.11_M eMMC-boot Mar 10 2011, 14:58:38
I try to understand android boot sequence on my JB (under CM10). I found some docs and there should be specific partitions (boot, recovery, system, cache, data).
My understanding of the boot sequence is now:
A) normal boot: 1) Power ON -> 2) bootloader -> 3) boot-partition where i flashed the kernel aka boot.img -> 4a) system-partition with the OS (libs, UI, etc) where i unpacked over CWM my customROM.zip -> 4b) data-partition, where i unpacked google-apps.zip and installed all the apps -> 4c) cache-partition with user data
B) recovery boot (adb reboot recovery): 1) Power ON -> 2) bootloader -> 3) recovery-partition with CWM where i may unpack all the .zip stuff to proper partitions, or restore from sdcard, etc.
Is this correct? I wonder, because i didn't installed CWM into recovery-partition. It cames from install of CM10 (fastboot -i 0xfce flash boot boot.img), so it must be in boot-partition and not in recovery?
So, next confusion: i looked up to /proc/mtd and i don't see neither boot nor recovery partition here:
I did a backup with CWM and loocked the data. There aren't boot, and recovery backups:
# ls -lha /sdcard/clockworkmod/backup/2012-10-04.18.49.55/ d---rwxr-x 2 system sdcard_r 4.0K Oct 4 18:56 . d---rwxr-x 3 system sdcard_r 4.0K Oct 4 18:49 .. ----rwxr-x 1 system sdcard_r 1.6K Oct 4 18:54 .android_secure.vfat.dup ----rwxr-x 1 system sdcard_r 54.6M Oct 4 18:55 cache.yaffs2.img ----rwxr-x 1 system sdcard_r 360.2M Oct 4 18:53 data.yaffs2.img ----rwxr-x 1 system sdcard_r 212 Oct 4 18:56 nandroid.md5 ----rwxr-x 1 system sdcard_r 214.6M Oct 4 18:51 system.yaffs2.img #
So, i think i didn't understand the boot sequence and partition schema corectly.
I have a ~1.5 year old Samsung Galaxy S3 (North American) rooted, with Cyanogenmod 11 installed.
Ever since installing CM11, my phone has been restarting itself with some regularity.
Today, with over half the battery left, the phone seemingly turned itself off. I do not believe this is an issue with the cyanogenmod OS and I also don't believe the issue is related to the restarting I've been experiencing. These restarts, in the vast majority of occasions, started with a brief freeze, then screen turning off, before the phone automatically starting up again. However, this time, the phone did not freeze before the screen went black, and the phone did not restart itself. I repeatedly tried pressing the power button to unlock, and when that didn't work, I tried long-pressing to either turn the phone off or back on. When that also failed to work, I pulled the battery, and put it back in. The Samsung logo came up, and then the Galaxy S3 logo with the Cyanogenmod logo came up, then the screen went black again.
And this is where I'm at currently. After the screen goes black, I can't get it to come back on. Long pressing the power button does not turn it back on. Only when I pull the battery and put it back in, does the boot process start. Every time, during the first few seconds of the boot process, the phone turns itself off. Sometimes it only lasts until the Samsung logo, sometimes to the GS3/CM logo.
If I plug the phone in, with the battery inserted, I briefly see a battery on the screen, but again, the phone shuts down.
If I plug the phone in, with the battery out, the LED turns red, the phone vibrates, but nothing happens, and the LED goes out.
I've read about power buttons getting stuck, but this doesn't seem to be the issues since my phone does not go into a boot loop sequence.
I've tried leaving the battery out for an hour or so, but there is no change.
I've also tried pressing power+home+vol down and power+home+vol up, and they seem to work, until again, the phone shuts off. So one of these combinations leads me to warnings about changing OS before shutting down after about the same number of seconds, and the other leads me to the boot logo with the blue text on the top left corner before shutting down.
To me, this doesn't seem to be an issue with software, but with the phone staying powered..somehow.
I've been trying to track down a solution to my problem, but every solution seems to contain a "Boot into recovery mode" line which I cannot do. I attempted to update a rom that I had installed, and now I am stuck at the google logo with the unlock icon. I cannot boot into recovery with the volume keys and power, and now I cannot figure out how to use adb to recover the phone, as it cannot recognize it.
Is there anyway I can access this phone while it is in this state from my computer and recover it somehow. I tried following leads that people have posted in other threads, but it seems like most suggestions involve "Use adb", yet every adb tutorial involves the phone being in recovery mode. I've tried to uninstall and reinstall drivers via Wug's Toolkit, but when I plug my phone in, I am not able to install the drivers properly. I try to run adb items through the console, yet it does not recognize my device.
Is there anyway to install the necessary software I need and recover my phone while I cannot get past the google logo screen?
I'm currently running Cyda's Stock+ ROM on my Ascend G300. I installed this Volume+ and set the incall volume steps to 100 and rebooted and now my phone won't boot and is stuck in the booting animation. [URL]
I have a new quad-core phone with android 4.2.1, that is now useless. It can not boot, it freeze at second bootlogo, before animation.It is rooted, and i have made some changes to build.prop. It worked fine, but after some time i realized the gallery and camera app was gone.
Then i did following:
Installed updated standard gallery+camera apk found online, both in the same app. from here [URL] Works great, but i wanted to make it a system app, so did that with titanium backup.After that, the camera app is gone. Gallery app is still working.So i tried to change it back to user app, again with titanium, but did not stop working. After some time i took out the battery.Now it freeze before boot animation.
I tried "wipe data/factory reset" and "wipe cache partition", in system recovery but still not booting!
I tried to backup user data from another phone, same model, and restore on this one but says "Error: checksum compare fail".
Do i need to flash a new rom to the phone with my pc? I have not tried this before, and i want to keep stock rom.I have read this page:
But i can not get it in download mode, with those hotkeys?
i have access to other working phones of the same model.
I was removing stock apps from my /system/app folder, and deleted Launcher2.apk by mistake. The phone couldn't boot properly, so I managed to get the apk from the emulator and install it using adb booting the phone on recovery mode.
Now, my problem is, that Launcher only shows shorcuts to the apps from my /system/app folder. Every apk I put or install on /data/app doesn't apear on the apps view. So there is no way to launch any app unles I manualy move it to system.
I think launcher must read a config file to get the installed apps, and it's failing for some reason. What do you think?
I have a six month old Epic 4G, rooted, CWM recovery,. I used Root Uninstaller to remove three of the annoying preloaded apps that I never use. Otherwise, my phone is stock. I'm still on the 2nd to last Gingerbread update, as the one that arrived in late Jan won't apply to my rooted phone. I doubt my problem is specific to the device, though, which is why I'm posting here. I have a 32GB SD connected to the phone.
The problem: I have a very irritating "warm reboot:"
1) After booting, the phone is sometimes (not always) extremely laggy. When I use a system monitor to see what is taking the CPU, it appears to be "System" that is taking all the CPU. If the phone is not obviously laggy when starting up, this problem does not occur. 2) The flash card scans always say they complete. It never reboots before these complete. 3) Although the flash scans have completed, it takes quite a while for all of my app icons to load, suggesting it is still going through the SD card. 4) Within a few minutes after booting, the screen goes black and the four soft keys light up. If the screen is already off when this happens, the screen first turns on briefly, and then goes black! 5) About five to fifteen seconds later, the GUI restarts and it starts scanning the flash.
What else I notice:
* The "uptime" reported is not reset, which tells me there was no actual "reboot."
* Once I can get it to boot without doing this, it's stable for days.
* Using the phone right after it boots seems to increase the chance of this happening, but it's hard to say.
* In the past, if I disabled WiFi and 4G and then went into airplane mode, this would greatly reduce the chance of this happening, but now my phone has been constantly warm rebooting even in airplane mode. The phone appears to be getting less stable with time.
* This does not appear to be correlated with phone temperature. The phone can be cool to the touch or warm to the touch and this will happen.
* I've tried wiping all the various caches before. Makes no difference.
1) Is this a known issue that is not present in a 3rd party ROM?
2) Does moving a lot of apps to SD cause this? With only 1/2 GB of built-in app memory, I have no choice but to move almost everything to the SD.
3) Does having a LOT of files on the SD card cause this? I have many nandroid backups on the SD.
4) Is there a real name for this "reboot" that I can Google for? When I search for "reboot loop" or "warm reboot" I get unrelated failures. I saw one thread where someone mentioned a "sense reboot" but that seems to be an HTC thing?
5) If I clear off the SD card, or somehow signal that most directories are not to be scanned, will this make a difference?
6) How can I figure out what is going on, why the phone is restarting the UI? Does Android have a boot-up problem of being at 100% CPU for a few minutes that automatically causes a UI reset? As I said, once the phone boots without doing this warm boot, it will be stable for days.
Instead of seeing the boring old Android logo or my service provider's logo, I'd love to see the standard text-based Linux boot screen that shows the status of all the hardware and configuration info as my phone boots. My current phone is an HTC EVO 3D running Cool ICS with Sense 3.6 and Revolutionary CWM.
yesterday, I flashed Modaco Switch for HTC One when my battery is low (20%). Now it wont let me pass the "HTC quietly brilliant" screen. I've searched the solution for hours and still, no luck on finding it out. But I see some thread that suggest me to download a new rom and put it in my SD Card, but I cant even pass the HTC boot up screen. Btw, I've relocked and unrooted my device.
After unlocking my phone's bootloader and flashing the kernel:
When I power off the phone, it gets into a state where I cannot control it by itself (black screen, no charging light if connected to a power source, does not react in any way to any key).
However, I am able to access it via adb over USB. Using adb, I can put it into some other state (reboot, reboot bootloader, etc) and again gain control over it (also through its own keys). When I select the "power off" function of the bootloader, it enters this state again.
I can even reboot the phone (also into recovery/bootloader/fastboot) from any state
So I can use the phone, but I can't power it on by itself, which isn't a good situation when I don't have a computer around.
device: HTC One S ROM: CyanogenMod 10 (device is officially supported by CM10; I used the version I found in the Wiki.) kernel: The one included in CM10 (had to be flashed manually via fastboot because of restrictions by the device; I flashed the kernel before flashing the ROM)
I was listening to music as I always do. I didn't realize it but the phone (Rezound) drained a bit faster than expected and died completely. So I went to to charge it, and left it overnight, off naturally, now when I power it on, its stuck on a boot loop.
It goes throught the startup animation, and once it gets to Sense, in the few seconds before the radios kick in and it finds the cell service, it reboots and starts all over again. Only way to get it to stop is pulling the battery out.
I started to do the hard reset, but when I got to the window for it, all I saw was Factory Reset (I guess they are the same) so I selected the option for reboot.
The light to charge does show its charging, and at one point, when I had it plugged in this morning, and managed to swipe the ring to get to my swipe lock screen, it was saying I was at 99%. then it goes all slow and then rebooted.
I used the factory wall charger, and its drained I think once or twice before, and I have done the FoxKat method of calibrating before this. Not sure if its a battery thing, since it will power up, or not.
I'm stock, non rooted, on GB.
I don't really want to do a factory reset as I'd like to have my messages saved. I did save them last week when I saw ICS was available, but i have some new since. I'm pretty sure my pictures and videos will be saved during the reset. I don't think that folder gets wiped. However I was going to try going to a VZW store to see about a new battery. The phone is new since June.
Firstt do a FULL FORMAT of the phone with the scatter file provided here. then flash the files ONE BY ONE.
1. Just filash preloader.img * remove battery and usb cable 2. Flash DSP_BL * remove battery and usb cable 3. Flash pro_info * remove battery and usb cable 4. Flash UBOOT.img * remove battery and usb cable
Once this is done, my phone could not boot. does not display.
So I have a Samsung Galaxy Ace 2 X (GT-7560M) and basically I tried to flash CM11 on it, and when after the reboot, the phone was stuck in a boot loop and I can not access nor the Recovery mode nor the Download mode. I did try a USB jig and still no luck.
I recently bought a used, but in good condition Optimus V. Not a great phone, but it does what I need. However, in the past couple days I've found that when the phone does its auto-timeout, it takes up to ten seconds for it to switch back on. By that I mean that when I press the power button just to get to the passcode screen (not to turn the whole thing on), it takes much longer than it did when I first got it.
I've uninstalled recent apps, but it's done nothing. What to do?