Hi All,
I have been running Cyanogenmod 7 on my Milestone for a while. I recently tried out the Supercharger and upon reboot, I'm getting a bootloop. When it boots, I get to the Cyanogenmod7 boot logo, eventually I hear the camera focusing but the logo is still there. If I put it on the dock, it kicks it out of the boot screen and lets me into the phone (phew). If I push where the unlock button is on the screen, I can hear it sliding unlocked but again, nothing. Anyone know what happened? I don't really want to flash it back to stock as I have it all setup nicely. Also, I even "unsupercharged" it and it still is doing this. Right now, I'm able to use my phone since I have the dock but if it randomly reboots, I will be in trouble .
Thanks!
Jon
Do a Nandroid Backup via OpenRecovery.
Flash it back to Stock.
And restore the important things (not the whole system).
That's what I figured. Thanks!
I ended up just backing up what I needed and flashing HO!NO! Only problem is that I can't seem to get the settings to stick on reboot.
Related
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.
Please help me, I couldent find a similar problem, (unless its boot loop, never actually described)
I have a stock N1, latest build 1.2.3
I was just using it as normal, was deleting all my texts using go sms pro, but for some reason they wouldent delete. when I restarted the boot animation played continously, ocassional staggering then starting again.
Im not sure whats wrong.
I can boot into recovery (vol+power right?)
Any help would be appreciated.
-----
Edit: sorry for the trouble, figured that i might be a app gone rogue, so cleared data, all good now.
I wouldn't use that app anymore, in case it messed up phone
While in the bootloop, pull battery, reinsert, and pwr on--sometimes works
If you are not rooted, not sure--If rooted, you can do a restore
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.
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.
Hey all, hopefully someone can help me out. Ill post the full story and the tl;dr version at the end.
So, my Xperia TL (LT30at) has been rooted for over a year and a half. Since i rooted it it never charged when turned off. I did research and couldnt figure out why, so i left it and have lived with it for the last year and a half. However, i just updated my phone to JB 4.3 by Dark Lord (Ultimate Pure XT ROM) so the model number is actually Xperia T (LT30) Anyways, the phone dies a lot quicker than before so the other day it died and because it wont charge when it is off i usually wrap a rubber band over the power button so itll charge enough to turn on and then charge by itself after that. However, it would only charge enough this time to boot, but then turn right back off. I did this for well over a day and got sick of it not working so i tried messing with things. In the process, I was in recovery (it was philz cwm or something like that, by the way im quite a noob when it comes to all of this, hence why im having problems) and i flashed the xposed disabler zip, thinking it would get rid of cwm because i didnt know what I was doing. It did end up getting the phone to turn on, and its charging great. However, the system UI crashes, and the "unfortunately the system UI has stopped working" pops up repeatedly so you cannot physically do anything on the phone. I tried going back into recovery to flash my backup to fix everything, but it was downgraded back to an older version of cwm, the version i origonally had on it before the 4.3 update. its like 6.0.3 or something, by david marcos or something. Anyway, itll go into recover but a bunch of error messages come up, like unknown volume path, no etc/recover.fstab, stuff like this. There is no way to flash any recoveries because it basically says it cannot find the paths. It will not backup, restore, wipe anything, flash from sideload, nothing. Ive tried all i can think of. Basically cwm comes on but i cant use it for anything. Instead i tried reinstalling cwm to try to fix it, but when i do it says "system cannot find path specified" so it wont download.
tl;dr version, cwm wont work at all after flashing xposed-disabler.zip. i cannot flash any recoveries or install anything through the usb. What do i need to do to fix this? because the system ui keeps crashing my phone is basically useless. thanks for dealing with a numskull..thanks in advance.
You can flash a stock rom with kernel using flash tool and then flash recovery and restore your backup.
Sent from my Xperia T using cm12
arniks8 said:
You can flash a stock rom with kernel using flash tool and then flash recovery and restore your backup.
Sent from my Xperia T using cm12
Click to expand...
Click to collapse
why i didn't think of that, i dont know.
This worked as far as getting the phone to boot and whatnot, however the phone died and because it doesnt charge when it is off, i cant turn it on. it will boot and itll get all the way to the home screen but it immediately shuts back down, even though it is plugged in. Is there any way to fix this charging bug? i did some research and found it is linked to cwm, however now that i flashed the stock rom i no longer have cwm on the phone, so why does it still not charge when off? Thanks for the help by the way..