Hello Peeps,
I was trying to flash a rom yesterday and had something strange happen to me.
The rom featured Aroma installer and I had flashed this particular rom roughly 5 or 6 times with no issues.
Yesterday, I did a full wipe and tried to do a new install of this rom.
There was an option screen in aroma that allows you to choose your own mods and features or use the developers defaults.
I was on this screen trying to choose the developers defaults option and Aroma simply froze up.
It would not let me choose with version to flash.
The touch screen wouldnt respond and I didnt know what to do.
I searched google and found nothing.
I decided to do a battery pull.
I know that a batter pull during a flash is something we should never do as it will brick our phones.
In this case, as the flash had not actually started yet I decided to try it.
I pulled battery and booted into recovery and was able to restore a nanroid.
I am just curious if anyone else has had this issue?
How dangerous was it to pull my battery?
Could I have bricked my phone?
Phone has been working just fine, I am just wondering if there is another way to resolve an issue with Aroma like that?
Thank you,
I never had that problem as for the pull battery it is fine as long as you're not flashing.
I was installing a ROM on my sister's s3 when the aroma installer completely froze. I pulled the battery and it boot looped but wouldn't go into recovery until around the 10th or so time (vol up + home + power). Flashed it again and it worked fine...really weird.
As for bricking your phone I agree with above poster, it should be fine if you aren't flashing anything.
Sent from my SCH-I535 using Tapatalk 2
I've had this same issue happen a couple of times. It usually happens when I try to install the Jelly 'Beans' rom...sometimes it will work, sometimes it will freeze. I usually have to do a battery pull and recovery will come right back up. I've noticed this seems to happen the most when the phone has grown hot...so maybe it has something to do with RAM, etc.
Related
I love everything about the SK4G but the constant reboots is it's only Achilles Heel. I've tried installing the Glorious Overdose V2 ROM on it, and the phone has seen overall improvement but the reboot problem has not been fixed and everytime I open an application or playing games it will freeze and then reboot. Can anyone suggest a ROM they're using that has helped with the reboots occurring all the time?
Try GingerClone, it's one of the lighter roms.
trying a different rom might help, but chances are if you flashed a rom and the problem persists, then flashing another rom may not help. I had the same problem with the stock rom. my phone rebooted every 15 minutes to a half hour for almost a whole working day. finally I shut the phone off, booted into CWM recovery, clicked on advanced, and ran fix permissions. I suggest that you not use a program or script to boot into CWM, because I have tried that and it doesnt work. after I ran fix permissions, the endless rebooting stopped. if you like the rom you're on, try fix permissions and see if it works. you really dont have anything to lose. if it doesnt work, just flash another rom. I recommend fix permissions a lot, because it has worked for me many times.
I got the device two days ago and rooted it the night I got it but remained stock to get use to it a little (came from MT4G) and still not use to the lack of physical menu buttons.
Anyways, after rooting and going through the process CWM, SU, ect. everything looked good for a while but today I had two random reboots from locked screen (went to unlock the device and it rebooted, the same way both times but not full reboots they were short and quick) and I was wondering if anyone else had this same issue and if so how to correct it.
There was another thing, when I boot into recovery it loads fine but when I reboot back to ROM it says there was an improper boot and wanted to send crash log to HTC. Not sure if this is going to be the normal thing but if anyone else is having this every time they go into recovery is there a way to opt out of it by default?
Thanks for reading.....
Orical said:
I got the device two days ago and rooted it the night I got it but remained stock to get use to it a little (came from MT4G) and still not use to the lack of physical menu buttons.
Anyways, after rooting and going through the process CWM, SU, ect. everything looked good for a while but today I had two random reboots from locked screen (went to unlock the device and it rebooted, the same way both times but not full reboots they were short and quick) and I was wondering if anyone else had this same issue and if so how to correct it.
There was another thing, when I boot into recovery it loads fine but when I reboot back to ROM it says there was an improper boot and wanted to send crash log to HTC. Not sure if this is going to be the normal thing but if anyone else is having this every time they go into recovery is there a way to opt out of it by default?
Thanks for reading.....
Click to expand...
Click to collapse
If you boot into recovery or hard reset by holding the power button. It will always ask to send crash report
OK cool so it's normal, thanks for the information.
the short story- my htc inspire is frozen on white htc startup screen and wont go anywhere.
the long story- i got my htc inspire 4g stock (used) beginning of this summer. it was almost perfect except some annoying apps and features. so i successfully rooted it using advanced ace hack kit. it was great. but the battery life sucked and so did the speed. so i decided to flash to new rom so i can overclock and undervolt. i then backed up my rooted stock rom onto my sd card. i then installed android revolution 7.3 and overclocked to 1.5ghz and undervolted -50. it was great now, battery life was way better and phone was faster. it was almost perfect except one issue- every once in a while, it would randomly just shut down and restart, then get stuck in a bootloop displaying htc white screen then the beats audio, then repeating endlessly until i pull the battery. that solves it until it happens again randomly (not that often but still annoying losing my data) i tried different settings in setcpu and daemon tools and same problem.
i then decided its time to revert to stock rom and try a new rom and see the difference and if i like it more, ill keep it. so i loaded recovery from rom manager (because my power button dont work) and i wiped to factory default and did all the steps of clearing the cache and the dalvik cache, etc it said it did it fine. i clicked install from zip and chose dirty unicorns rom that i found on this site for my phone.
it said it installed without any problems. cool, i clear caches again and reboot.
but this is the wack part: when it restarts, it still loaded android revolution... all the data on internal memory was gone from wiping it and my superuser was gone. (rom manager stayed) i thought that was weird. i tried a couple more times and same thing. and then i put the backup i made of my stock rom before i flashed anything onto my sdcard-> rom manager-> backup.
but when i went to rom manager-> backup, my backup wasnt there. i then went to manage backups and restore. it said no backups found. i then thought maybe it has to do with superuser gone? i plugged in my phone and loaded ace. i noticed it had a load stock rom option on it. awesome, i clicked that, chose first one (htc inspire at&t) and it started doing its thing. but it said it had a problem downloading some package or something? it said it connected to th site fine but kept coming up with that error and a prompt saying "do you want to continue[y/n]" and i type y hit enter and same error. i tried another one but same error. oh well. i went back to menu and chose option 1 for rooting it, it did its thing with no errors. rebooted my phone. except now, its on htc start screen and wont go anywhere. its just forever stuck there. i did figure out just now that since my power button dont work, i could load hboot by taking out battery, and holding volume down while sliding battery in. but it wont go up and down on the menu with the volume keys. since my power button dont work i cant select one anyways but i should still be able to go up or down right?
well thats what happened and i feel like a retard.. if anyone might know whats wrong please help
ok i solved the issue after constant reading. i had to reformat my sdcard to fat32 and put stock pre rooted rom since i still had s-off. then it was just load hboot and it loaded files from sd card automaticly (took a moment, i thought it wasnt going to work) but it said found file (only file on the card now) and then accepted install. now im back to stock pre rooted rom. im so happy i didnt completely ruin my phone <3
im sorry for wasting everyones time. i should have read more before posting, as the thread that helped me solve this was on this site.
>>>> http://forum.xda-developers.com/showthread.php?t=1396229
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.
bweN diorD said:
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.
Click to expand...
Click to collapse
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?
SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
In all likelihood, this is not a LiquidSmooth issue. I would suggest a clean install as the previous posters suggested. The latest stable version of LS is now at v2.10 for Android 4.3
LS 2.10 must be installed as follows, according to the devs:
New Flashing Instructions
wipe data/factory reset
wipe cache partition
wipe dalvik cache
format /system
Install ROM, NOT GAPPS YET!!
Reboot system, first boot may take a few minutes, don't panic ;-D
Setup your phones settings, anything that isn't Google related
or let your phone sit for 5 minutes
reboot back into recovery
wipe cache and dalvik
then flash gapps
reboot and enjoy
Click to expand...
Click to collapse
For the xt926, the download page for LS 2.10 is here: http://d-h.st/users/jsnweitzel/?fld_id=15202#files
gapps 8/13 or newer are supposed to be used with this ROM. dl from here: http://d-h.st/users/jsnweitzel/?fld_id=21058#files
The official ROM page is over at G+ https://plus.google.com/u/0/communities/117452480298315341829, if you have any additional questions.
Give it a whirl, and let us know what happens. Good luck.
SELind01 said:
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?
Click to expand...
Click to collapse
you are wiping very well, i was just confirming you wipe everything possible short of the external sd.
the wipe im talking about in twrp is wiped when you wipe "data", the one where you have to type "yes" before it will wipe. in cwm, in the formatting section (i forget what its called), there is an option that specifically says "data-media /internal sd" or something close to that.
as for the latest recoveries, here is a tool by Tucstwo that i have been updating lately http://www.mediafire.com/download/2o061zcmzlaycb5/Razr_HD_Recovery_Flasher_V8.rar
also, twrp 2.5 doesnt have all the selinux bugs worked out, you need 2.6.3.0, which is in the above utility.
So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.