Develop Bugs

Random Reboot. Help

I charge my phone overnight everynight. There are times when i wake up in the morning my phone is just stuck on the splash screen. What could be the problem?
-I'm Running on CM6.1.1
-I have a customize splash screen and boot animation
-I used unrevoked root and unrevoked s-off
-I noticed that the random reboot happened when wifi is on (noticed this twice, not sure about the other times)
-And this started to happen (from what i remember) when i tried to flash something over my recovery (toast or something like that, i can't remember i was just following a tutorial for me to able to put a new splash screen. It was for fast reboot to work) then i got stuck on a loop in bootloader. Then i flashed CM6.1.1 to get an image.
Help please?

A clean flash of cm 6.1.2 should not give you any issues. Are you using a custom kernel?

ald3n3 said:
I charge my phone overnight everynight. There are times when i wake up in the morning my phone is just stuck on the splash screen. What could be the problem?
-I'm Running on CM6.1.1
-I have a customize splash screen and boot animation
-I used unrevoked root and unrevoked s-off
-I noticed that the random reboot happened when wifi is on (noticed this twice, not sure about the other times)
-And this started to happen (from what i remember) when i tried to flash something over my recovery (toast or something like that, i can't remember i was just following a tutorial for me to able to put a new splash screen. It was for fast reboot to work) then i got stuck on a loop in bootloader. Then i flashed CM6.1.1 to get an image.
Help please?
Click to expand...
Click to collapse
Random reboots are usually always caused by a custom kernel that your phone does not like.. I could be wrong but that is my experience anyway...

i had the same exact thing except i actually had 6.1.2 clean with no custom stuff. the only thing custom would be the galaxy s theme i put on it.
i would be trying to go to sleep and i would feel my phone vibrate and then i noticed its rebooting, the rebooting is pretty frequent.
i wiped and restored my original backup and installed all the new stuff (radio/wimax/etc.., except hboot)
right now im gonna install a clean 6.1.2 and see how it goes

No custom kernel. Maybe i just need to manually flash cm6 so i can wipe data 3 or 4 times. I kinda don't trust the rom manager and clockwork work recovery method i feel like it doesnt really wipe everything clean before installing.
Sent from my PC36100 using XDA App

How do you un-install a custom ROM
I installed a custom ROM and now (a month or two later) I'm getting reboot after reboot. How do I get rid of the custom ROM?
Also, what does it mean when the phone reboots, then vibrates 5 times and locks up?

To get rid of the custom rom just do wipe through recovery...
And the the locking up? I have no clue why that is... sorry
Sent from my PC36100 using XDA App

[Q] incredibly re-engineered v2.20 wont boot

I flashed the incredibly re-engineered v2.2 rom a week or so ago and it worked great till today it was giving me a force close on a bunch of apps, so i restared it and it still didn't help. Did a *228 and when it restated it just goes to the black screen that says htc incredible Loading then after several seconds it flashes blank for half a second then says same thing. I used rom manager to flash it. I've also used virtuous and skyraider 3.5. I'm good at computers but android is new to me as i've only had this fon 2 months. I have to do a battery pull to restart it. Any Ideas on how to fix this? I can boot into recovery but havn't been able to do anything... Never used it so not sure what to look for but like when i click recovery or factory reset, nothing happens. Oh, and i did a search but didn't come up with similiar problem.
htc incredible s-off
radio 2.15.00.07.28

Flash a different rom.
sent from my Dinc

How do I do that? When I boot in recovery mode I have option of fastboot, recovery, clear storage, simlock, and factory reset. When I select recovery it goes to bootloader, reboot, reboot bootloader, and power down, with reboot highlighted. Wen I select that it boots like normal than gets stuck on boot up screen.

Try fixing permissions through Rom Manager first, if not I would reinstall the rom. Be sure to do a full wipe, don't just flash over your previous rom.
If neither of those work, I would follow this thread
http://forum.xda-developers.com/showthread.php?t=786436
Flash back to stock 2.2 and see if your phone starts acting the same way. If so I would take it back to verizon. If everything seems ok, re-root and flash JUST the rom and apps that you want, no kernel, themes, anything extra yet. See if that fixes the problem.

I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.

mennotech said:
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
Click to expand...
Click to collapse
I would re-download a different ROM (making sure you don't have a corrupt download), check the MD5 SUM's to verify integrity of your download, mount USB Storage in Recovery to transfer the file to your USB card (when phone is off, hold down the Power and Volume Down buttons at the same time), wipe all user data/factory reset and Dalvik, and then reflash the ROM of your choice.

mennotech said:
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
Click to expand...
Click to collapse
Go to that link in my post, download the PB31IMG from the 2.2 Stock OTA, put it on the root of your SD card, boot into the bootloader and let it update. You will go back to being completely stock and unrooted. Root it and then try installing the rom again.

Failed to Load! :(

I am currently running Domination CM10 build 6 and was previously using the kernel that came with the rom.
Just updated to latest bricked which first just wouldnt boot (flashed kernel via fastboot and zip via recovery as normal) either normally or load recovery so used viper flasher to do kernel and modules (replaced ones it came with to latest ones from the kernel zip)
Now phone boots fine but after a few seconds it comes up "Failed to Load! " in a box at bottom (similar to boxes when something is given root access, checked and phone still rooted and that side working fine) but the box never seems to fade away so stays stuck over top of everything.
I only have 2 widgets... clock & calendar both of which load up fine, boots into recovery now if I boot normal and then use rom "reboot into recovery" but whenever I try to use it the phone just reboots, if I hold volume down when powering on it just boots as normal and dont load hboot
Any ideas? Know its not major issues and can probably be fixed with a wipe but tbh was lazy and didnt backup before flashing kernel thinking I wouldnt need it so hoping someones had similar and knows a simpler fix which wont involve wiping

ViaraiX said:
I am currently running Domination CM10 build 6 and was previously using the kernel that came with the rom.
Just updated to latest bricked which first just wouldnt boot (flashed kernel via fastboot and zip via recovery as normal) either normally or load recovery so used viper flasher to do kernel and modules (replaced ones it came with to latest ones from the kernel zip)
Now phone boots fine but after a few seconds it comes up "Failed to Load! " in a box at bottom (similar to boxes when something is given root access, checked and phone still rooted and that side working fine) but the box never seems to fade away so stays stuck over top of everything.
I only have 2 widgets... clock & calendar both of which load up fine, boots into recovery now if I boot normal and then use rom "reboot into recovery" but whenever I try to use it the phone just reboots, if I hold volume down when powering on it just boots as normal and dont load hboot
Any ideas? Know its not major issues and can probably be fixed with a wipe but tbh was lazy and didnt backup before flashing kernel thinking I wouldnt need it so hoping someones had similar and knows a simpler fix which wont involve wiping
Click to expand...
Click to collapse
try to reflash stock kernel, maybe it will be ok again, in worst case you'll have to wipe

[SOLVED] Booting Failure

Hi!
So just a quick background. I have S-OFF'd and flashed a custom ROM on my mates Desire HD few years back and have a bit knowledge about the device.
Today I showed him some of the 4.1-4.2 ROMs available for DHD. In TWRP I did a nandroid backup of his current Blackout ICS and flashed CM10.1. Everything went just fine, but the ROM was not the right for him, so I tried Venom Sense 4.1. I did a clean install on the Venom ROM and wiped everything in Aroma.
Apparently I was not focused enough and the Aroma installation failed with just the wipe. No ROM installed. Phone rebooted with no ROM and the caught stuck while booting. I thought this was no biggie and I would just restore the backup from TWRP.
Then all suddenly went to hell in a hand basket. Phone was/is unable to boot into bootloader with any vol+/- combination. It won't boot into recovery ether. Just straight into the ROM, which is not there -> bootloop.
TL;DR No ROM installed, unable to boot into bootloader or recovery. ADB/Fastboot showing no signs of connection.
Did I just buy myself a dead DHD and an angry friend?
EDIT: SOLVED. So, issue was solved by 1000 times randomly pulling the battery and pressin vol up and down. 999 tries straight booted into the OS, but 1000th try somehow got me into the hboot. No idea why or how.

[Q] Problem with boot loop

Hi guys,
I've got a big problem with my Gnex. I was running AOSPAL Paranoid SaberDroid ROM with Dirty V kernel and Nephilim's settings. Just the read ahead buffer was set as default so it was 512 I think. I think I just forgot to change it. Everything was ok and then I changed RAB to this value about 4000 (max). I started antutu benchmark and while it was running the phone restarted and got into boot loop. I don't know if it was the reason of the issue, but I wanted to tell you all the circumstances. When I tried to turn it on the Google logo appeared and then the system loading animation started, after about 3-5 seconds it restarted and so over and over again. I was able to enter recovery mode, so I wiped cache and dalvik cache. Nothing changed. I flashed Dirty V kernel again, thinking that settings would turn back to default, but it also didn't change anything. I flashed franco kernel, and also nothing happened. I returned nandroid backup but it also didn't help with this boot loop. Then I wiped cache, dalvik cache, system, data and clean flashed SaberDroid ROM with stock kernel and PA gapps. Nothing. I plugged my phone to computer and flashed Google factory image using WugFresh Toolkit, so it wiped everything unrooted my phone and flashed stock clean 4.1.2 android and everything. I thought that will solve my problem, but also it didn't help. Nexus is still in boot loop - it keeps restarting when there is nexus logo animation. I was scared at that moment. I forgot to mention, that I could get to fastboot mode, recovery and the battery logo was showing correctly when phone was plugged to charger. Then I locked the bootloader so it is completly stock right now, it just doesn't turn on...
I read the topic about omap flashing, but as I understand it is for those devices, which can not turn into fastboot mode (and mine does) and then the solution is to flash google factory image, what I did... When phone is turned off and plugged to computer the device menager shows for 2 secs omap4440, and when it is in fastboot mode and plugged to comp it shows normally as Android Phone (Google Galaxy Nexus BootLoader Interface, because I had drivers installed to use the Toolkit.
It is all what I could do and I don't know what else could be done to ressurect my loved Gnex .
Do You guys know what's going on?
Please help me.

I think I have read somewhere in the Dirty V thread that some bug in the kernel was causing the Google logo boot loop. Have you tried using 0sm0sis' Emergency Kernel Cleaning Script listed in his signature? I remember him telling someone to use that script in the kernel thread.

osm0sis's zip only restores kernel tweaks and settings to default. I didn't try it, but now I don't have to, because I don't have any custom kernel right now. My phone is pure stock.
Yesterday I tried omap flashing, and it run properly, but also didn't change anything. I also flashed Google factory image again after omap flashing.
Any other tips? It doesn't look optimistic ;/. Maybe it's hardware? But I thought reboot loops are connected to software and it is soft brick, which can be repaired.