Question.
I was on 4.0.4 and the phone started freezing on me. Just freezes and becomes completely unresponsive. To reset I have to pull the battery. Now this had happened about once a day for the last week, but today I had to pull about 12 times. Now 4.0.4 was working well until I tried to go to 4.1.99. That was too laggy and buggy so I restored my nandroid backup. So for the past week I was living with the occasional battery pull.
Tonight, I tried to go to 4.1.9999, and now it freezes on me during the initial sign in process, "SIGNED IN! SLIDE KEYBOARD BACK TO CONTINUE". It does not get past this screen.
I'll do a Nandroid restore to get operational, but that level of operability was pretty weak.
I have AmonRa's recovery, but I only did one wipe prior to the two flashes.
ADDITIONALLY, I try to get to the recovery boot screen now after I pull the battery and the phone wont let me. Still goes right onto the Welcome to TMO G1 Android screen, where it proceeds to lock where I mentioned previously.
Any ideas?
****. I get an ERROR PERFORMING RESTORE! TRY RUNNING 'NANDROID-MOBILE.SH RESTORE' FROM CONSOLE!
The **** has hit the fan!
As of this moment, I can't do a Nandroid restore, and I can't get past the above mentioned slide keyboard back to continue screen. How bad is it?
No. You're not bricked.
When you say you came from 4.04, did you put the htc image and the cyanogen rom on? or did you just try to upgrade?
HTC image first, then the ROM. I wiped first, but only one wipe.
As of right now, I have a phone that won't load beyond that screen. Nandroid wont let me restore.
Help, please?
wipe!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I did. No help.
Wipe, reboot and this is what happens:
HOLY CRAP IT WORKED!!!
thanks guys... lets see its functional at least now.
It says its running 4.1.9999... what do I have to do now?
Your done as long as it's working good.
It's not. I have the same problems. Phone freezes at completely random moments. Same ****.
Phone worked well for a short time, then performance degraded again. Now its back to the same. Freezes almost instantaneously after a reboot.
go to recovery
(go to console)
fix_permissions
when done
type
reboot
wait for pause..
and it will reboot!
that booted me into a blank black screen after the ANDROID boot screen. Frozen again.
Related
Hi,
My roger's dream decided to stop working today (i've only had it for like a week). It's rooted, but I haven't done anything major to it. It was running stably for a couple of days after rooting it so I'm fairly confident that it's unrelated.
I wasn't doing much at the time, messing with Klaxon i believe, but it randomly shut off and now whenever it tries to boot, it gets stuck at the splash screen (just playing it over and over).
I've tried booting in safe mode (w/ Home button) and it won't come up. That's about all i know how to do. can anyone help me out with this?
Thanks so much, i'm in a state of crisis right now.
Yea just wipe the phone, reapply the update.zip and it should be good. If that fails. You may need to backup your sd card, wipe that, redo it and put just the apps and apps-private folder back in and link it. (Unless your rom automates that for you)
You can also try in the recovery console from cy the alt-x to terminal, then type fix_permissions and do a fix ext filesystems. That may restore you as well.
Does pressing Power + camera key get you into the fastboot screen?
Recently I wiped my G1 because it became so slow, after I wiped it I just pressed back and reboot it, the it boots to T-mobile and then Theme screen, after a while it just stuck on the black screen and won't boot to Home, and the battery became warm, I need to pull out the battery to turn it off.
What should I do here now??
Thanks for any replies
you needed to wipe davlik-cache not the whole phone. wiping the whole phone will break the rom youre running. u need to reflash a rom in order to get your phone to work properly.,
That's the problem... --'
Thanks Brian. Glad I backed up my Rom with nandroid backup.
I'll remember that next time.
I've tried repeatedly to install CM7.2 and keep getting stuck on a blank screen. I'll see a "CyanogenMod" then "loading..." right below that. Then it goes blank and nothing ever happens after that.
Some background info. I've had CM7 installed on this in the past without problems. Months ago I went back to a rooted stock. Then yesterday I decided to try CM9 alpha. That installed perfectly. But it was too slow, so I decided to try CM7.2.
I used the same CWM 1GB boot SD, copied "encore_CM72-MiRaGe-02012012.zip" along with the Gingerbread Gapps and CWM. Installed in the same order and wipe data/factory reset.
So I got stuck on that blank screen after the CyanogenMod loading... message. I then decided restore to stock. Installed the 1.01 stock image. It also wouldn't boot up, but I powered it on and off 8 times and it did a factory reinstall and then it booted up normally.
Once back at a factory fresh system. I powered it off and tried installing CM7.2 again. Unfortunately I'm having the same problem again. Ugh, why won't it load now.
Hang on... I might be in the process of making a newb mistake. MD5 didn't match on my SD card, probably the ROM.ZIP is corrupted. Trying again with a good copy.
That was it. It's working now. Please disregard my idiot on the Internet moment. Thank you.
You always figure it out five minutes after you finally give up and post for help/venting.
Been there.
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.
Everything worked fine for almost a whole year, then my tablet started acting strange last night. It got really bad this morning so i was trying to install a antivirus thinking that might help, but it wouldn't open. Reports of program failures were popping up like crazy, so i turned it off and back on about five minutes later. Now its been over an hour and its stuck in the cyanodenmod loading screen, its never taken this long.
Is there any program i can use on my laptop to wipe everything on my tablet and install another os? I'm not sure how it'd work seeing as how its stuck loading. Do i need to let the battery die? I really just want to plug it in and wipe the whole thing but i haven't a clue where to start.
Please help?
I took the back off and unhooked the colorful wire thing from it to turn it off, and put it back. It restarted fine and now I'm attempting to wipe everything on it. When i first pushed the erase all button it didn't do anything, then after trying a few more times it restarted to a "teamwin" something (have no idea what that is) and it restarted again, so far its back on the cyanogenmod loading loop again. (I'm a little amazed i even managed to root it in the first place, considering i didn't know what "os" stood for before that. I really need help with stuff like this.)
If i can get it back to the normal screen, is there any program i can use to reformat everything and like an alternative to cyanogenmod for the program?
Which CyanogenMod version are you running ? The teamwin that you saw when it booted up was the recovery you flashed to install custom ROMs like CyanogenMod. Make sure you have the latest recovery before anything . take a look here and let me know when your up to date and we can put you device back in working form
http://forum.xda-developers.com/showthread.php?t=2218796