I installed avast mobile security and set everything up as a root user. I'm on the stock ROM and as soon as I was done setting everything up I rebooted and now Im' stuck in a boot loop. It does not boot loop every time... sometimes it boots up and after about a minute it reboots itself, then bootloops.
I removed avast as an administrator / rebooted / then did a clear data and uninstall. Same thing happens so I booted into amon and did a clear cache and dalvik cache.
I've also booted into Amon and wiped all caches. Still no go and I notice that I'm not getting any signal bars (yes, I remembered to put the cover back on). Any help would be greatly appreciated...
Try this.. http://forum.xda-developers.com/showthread.php?t=1394659
sent from ics land
edit: try what the person above me posted first.
Are you on the stock kernel too? I would recommend doing a full nandroid backup and an internal SD card backup and RUU from scratch if you can't get the loops to stop.
I ran avast! for a while with no issues. Could be the link above is what you need.
Thank you all, trying option #1 now. I do have a Nandroid backup I did after I first rooted, and I am on the the stock Kernel.
Holy Cow, it was set to WCDMA Preferred! I'm really surprised that avast changed that setting. I put it back to the correct setting and now my signal is back. I'm rebooting now to see if it sticks.
Thank you all a ton! I'll post back in a few and let you know if that did the trick *fingers crossed*....
Update: Been about 15 minutes and no bootloop or auto reboot so the fix seemed to have worked. Once again, thanks a ton you guys for the help, I appreciate it.
I doubt it was avast that did it. It seems to happen randomly to certain people.
Related
First time I'm posting so hey.
I just bought a HTC Hero today and decided to load a custom ROM onto it.
I flashed it fine, and installed modaco earlier (file name: 2.8-update-hero-modacocustomrom-core-signed).
So when I powered it back on, it looked like it worked fine, but I must of went wrong somewhere.
The phone will boot up, stay on for like 5 seconds, and then restart. When it comes on, I can't do anything cause it freezes on the lock screen then just restarts.
I'm pretty sure I messed up by putting that ROM on a t-mobile UK Hero(which I unlocked). I aint sure as I'm only new to this.
Any advice on how to fix this?
did you do a phone wipe before installing the custom rom?
I formatted the SD card.... I think before I flashed it.
Then just put the ROM on the root of the SD card.
See it looked like it done everything fine with the ROM.
I held in the home/power buttons, loaded the boot menu.
I did a "Ndroid back up" (did I spell that right) - so I could restore in case something like this happened (which I did, since I need my phone lol), then picked "SD Choose", picked the modaco ROM and it seemed to install fine. Took a few minutes. Install complete. I rebooted the phone.
Then it loaded the normal boot screen, and would literally last only 1 second and freeze on the lock screen saying no signal, then it would reboot. And loop this pattern.
Neo-Dragon said:
I formatted the SD card.... I think before I flashed it.
Click to expand...
Click to collapse
A wipe has nothing to do with the SD card. It is essentially resetting your phones internal memory back to "factory" defaults. I take it you have a custom recovery image, as you mentioned making a Nandroid backup - you will find an option to wipe there.
Regards,
Dave
So if I wipe the phone before hand and then upgrade it should be fine?
If I do a nandroid back up, will I still be able to roll my phone back if it fails?
A wipe now may fix your problems with you needing to upgrade again.
My suggestion would be trying this first - if it doesn't help, restore your nandroid backup, wipe, and apply the new ROM again.
Regards,
Dave
Cheers mate.
After the wipe, I re-installed the ROM and it works perfect.
Thanks again.
OK:
Briefly, Running fine on VEGAn 7 RC 1 with Pershoot's latest. When the Tab was running and booting, I made a full backup in CWMod.
Screwed around with some permissions and once I rebooted, ended up at VEGAn Tab pulsating Boot Screen. It would do its thing for a minute or so, screen would go blank and then return immediately to the same VEGAn Tab screen (i.e., not a full boot).
Not a problem, right? I just booted into CWMod, cleared out everything and restored my earlier backup.
No go. Same loop at the VEGAn screen.
I searched the forums a lot, so either I am not very good at searching or this has not been addressed.
Advice would be appreciated, as this is not the first time I have been here and want to learn if there is a way to repair it (obviously, I can reflash ROM+Kernel) restore via Titanium and only have a little manual recovery left to do.
Thanks!
I had the same thing happen to me while i was changing around roms. I know its not the exact thing but regardless. Anyways, try mounting your tab in cwm as USB and pull your back up off the tabs memory. Go back to cwm and wipe everything, then repartition to advised settings. Remount your tab as usb and put the back up back on your drive and restore again. It may work.
Sent from my VEGAn-TAB using Tapatalk
iamjakecali said:
Not a problem, right? I just booted into CWMod, cleared out everything and restored my earlier backup.
No go. Same loop at the VEGAn screen.
Click to expand...
Click to collapse
If its something simple, clearing the Dalvik Cache in CWM might fix it.
I appreciate the ideas. Unfortunately i have tried then all. One of the times this has happened i was messing around with the old two taps xoom. Of i knew anything about the really technical stuff i might speculate something to do with boot loader.
Oh for anyone here who bricks, Don't freak... sometimes i do several times a day and have always come back from it ... mostly using the advice of all the brilliant people here, occassipnaly by messing around with adb, and once i let my monkey push random keys since he had already managed to compose a sonata...
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Mount the SD card either in recovery or on a PC and see if there is a PG05IMG.zip on it. Remove it if so, then reboot.
tqhx said:
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Click to expand...
Click to collapse
You can't install an OTA if your rooted, even if you haven't made any changes. The problem is the custom recovery (e.g. ClockworkMod)
When the update tries to install the updated recovery, it sees that the old stock recovery isn't there, and fails.
As far as recovering from that, I'm not entirely sure.
Seeing as you used the one touch root, I doubt you installed the S-Off eng bootloader. Try what the above poster suggested first.
Thanks for the replies guys. I did have s-off, but yeah ill tell you i tried what he suggested with no luck.
I ended up being ok i made another clockwork backup, did a full restore from a backup before the date of the update, then did just a data restore from the backup i had just made. Phone is back to normal. Thanks for the responses, ill give you both marks for being helpful
I'm in the same boat, except I was silly enough to not have a backup made. I do not see the PG05IMG.zip from recovery. Any other possible ways to fix this? If I have to clear all my data and start again, I'm ok with that though I'd obviously prefer not to do that.
Boot into clockwork recovery and wipe cache only.
Sent from my HTC Thunderbolt
This same issue has happened to me with the Verizon update. Long story on how it i clicked okay to the update. I told it reject at least 3 times already.
Anyway - i was stuck in this nasty reboot cycle. I was lucky to have a backup from March when I first rooted my TB. Not having a more recent backup is my bad.
So I have worked most of today with near factory settings from my recovered backup and now I am restoring todays backup to see if I can fix this reboot BS.
I did the Wipe Cache from ClockMod and when the phone rebooted it gave the prompt to reinstall the update which I cancelled. So success!!! Now I can clean up my junk apps and do a proper backup to protect myself in the future.
I'm a bit stuck here. I've been running MIUI (1.7.9) for a month or so on my OG Droid. I decided that it was time to update. I flashed the latest version (1.9.9), and started restoring apps, data, and system info. Apps and data restored fine. When I restored system information, it just automatically rebooted. Now it gets stuck in a boot loop, where I see the MIUI load screen and then the lock screen. I get maybe 4 seconds before it either freezes or reloads. If I try to reboot in recovery during that time, it freezes during the reboot.
I also can't boot into recover. If I hold down X when starting up, the phone won't turn on. The screen brightens (but stays black) and then goes off. It keeps doing this until I let go of X.
I'm thinking I need to flash an SBF file via Bootloader. I'm a bit paranoid that I'll mess it up. I'm not sure which SBF to use now, and I really don't want to brick this phone if possible.
I would really appreciate any help. Thanks.
how did you solve your problem? i'm in the same situation
irafcummings said:
I'm a bit stuck here. I've been running MIUI (1.7.9) for a month or so on my OG Droid. I decided that it was time to update. I flashed the latest version (1.9.9), and started restoring apps, data, and system info. Apps and data restored fine. When I restored system information, it just automatically rebooted. Now it gets stuck in a boot loop, where I see the MIUI load screen and then the lock screen. I get maybe 4 seconds before it either freezes or reloads. If I try to reboot in recovery during that time, it freezes during the reboot.
I also can't boot into recover. If I hold down X when starting up, the phone won't turn on. The screen brightens (but stays black) and then goes off. It keeps doing this until I let go of X.
I'm thinking I need to flash an SBF file via Bootloader. I'm a bit paranoid that I'll mess it up. I'm not sure which SBF to use now, and I really don't want to brick this phone if possible.
I would really appreciate any help. Thanks.
Click to expand...
Click to collapse
what information did you recover?the info might mismatch because the roms differ.Also try flashing a new recovery like cwm or AmonRa
Also if you restored the system directory when you did a restore, its like building two houses on top of each other, its 2 full houses, so both will crash because of the pressure. It probably just installed the system restore on top of the update, did you do a data wipe? Furthermore, if you look in the folder with your backup data, your should only restore the data portion rather than doing a full phone restore! so in the future, do a full wipe before reporting, and also, store the backup in a remote area, but put your data folder back in the original location and install it!
Sent from my PG86100 using XDA App
I ended up flashing CWR via an SBF file. It seemed like CWR just got corrupted somehow. From that point, I was able to restore from the nandroid that I created prior to updating. Hope that helps.
Htc EVo4g
Rooted EVOlved Rom - Recharged Final
hdmwin Poon kernal
latest radios
This morning I open Titanium to restore an app.
! Updates! Change log first item:
"De integrate dalvik and save rom"
Im often low on rom so yea lets do that.
I find the option in tools. De integrate.
Infinite loop.
I tried reinstalling my kernal.
infinite loop.
cleared dalvik and cache
infinite loop
clear batt stats
infinite loop
plain old 'reboot' from recovery. infinite loop. shut down from recovery. infinite loop.
short rain dance about the living room waving phone above my head. infinite loop
Ran circles in living room so fast as to slow time to a stand still while bp. infinite loop.
I have not reinstalled the rom which is on the card for the ready.
Id like to avoid that if possible.
Suggestions?
I don't think it's avoidable. You are going to have to reinstall the ROM. As a rule of thumb, whenever I make any changes to my system, even if it is something as minor as changing a font or a boot screen, I make a back up.
lowandbehold said:
I don't think it's avoidable. You are going to have to reinstall the ROM. As a rule of thumb, whenever I make any changes to my system, even if it is something as minor as changing a font or a boot screen, I make a back up.
Click to expand...
Click to collapse
I have a nand backup.
...Yea I think you may be right. Its sitting next to me rebooting like crazy while I surf net. damnit.
Hmmm I wonder if the 'save rom' by de-integrating is even gonna work. I assume there is no rom. I figured Titanium, awesome as it is, wouldnt steer me wrong. cest la vie.
Here we go. Reflash. Well I was gonna check for new versions anyway.
I mean I have a nand backup but I also have the rom on my card. Im just gonna straight flash the rom. I wonder if I should be nand restoring instead.
All is well.
Reflashing rom did the trick. I dont have any saved memory though... :/
lol Im tempted to try it again.
Does anyone know anything about integrating dalvik into rom? Does this save memory? Is it worth it?