Hi all
I'm running DeFroST 6.1a, stock DF kernel, and radio 5.11.05.14. Please bear with me because this might be a little long, as I try to explain everything I have done which landed me into a somewhat sticky situation.
A few weeks ago, I flashed the JAMT theme by ClassicalGas, and what I noted was the sudden loss of LED notification (and I don't seem to be the only one, actually). So I poke around, search the forum, and one user said he had gotten the LED notifications to work again by extracting the theme files from the JAMT framework-res.apk into the DF's framework-res and flashing the whole DF again.
I decided to try my hand at it, did a NAND, wiped, then flashed the "modified" DF - which caused my phone to be stuck in a bootloop. No biggie, just have to restore my NAND. I wipe, then when I'm about to restore my NAND, I get hit with
Code:
Error : run 'nandroid-mobile.sh' via adb!
Which, after some googling, could mean a couple of things, like the checksum is wrong, or battery is low, etc. But before I do anything, I hit the wrong button in recovery, then my ROM boots up (wiped). The first thing I realize during the starting phone set up application is that about half of my screen is not responding, but once I get out of the initial set-up, all functionality returns
I power down, charge my phone a good bit, _wiped_, then I did a NAND restore , without any problems this time, restoring my original problem free-state, and everything seemed fine
A couple of days later, on vacation, I was playing a Tower Defence game on my phone, and the whole thing froze on me. I popped out the battery. This is real strange because that game had always worked fine before.
I then try a bit of Zenonia. At certain points, my phone freezes up. Characters on screen, monsters, etc are all still moving around mind you. All EXCEPT me. There seems to be no response from touch whatsoever. I get a little frustrated and press the "home" button as well as the "power" button.
After some waiting, my phone screen goes off. I find out that it has went back to the lock screen, and when I unlock, its back to the home screen, with Zenonia still running in the background.
I inferred that my phone's response has been super delayed for some reason. It happens for over a week, sometimes, seemingly to resolve itself after a good wait, and sometimes never (which requires me to pop out the battery). Sometimes, it "hangs" so badly that my phone itself began force restart. Also, out of all the times it restarted, there was _once_ it was stuck in the bootanimation.
And I also have noticed, if my phone has been on the whole day, at night, my SMS app (stock) seems to move very slowly - in terms of when I type out my reply, the phone seems to lag behind and cannot keep up with my usual typing speed. Even pressing the "reply area" requires me to wait for some time until the keyboard pops out (not stock, but never had problems with it before).
Sometimes, unlocking the phone when I last left it as the SMS screen would also cause some lag when I unlock. Reboots from the power menu seems to clear it up (until the next time it happens again).
Last night I tried some Kongregate Arcade, which needed flash. At some point of playing, whenever I was about to receive an SMS, the phone seem to _not_ response to my touch once again, while baddies on the flash game still continued to move around and hit me.
At first I thought it might have been a problem with SetCPU's governor (does interactive cause problems? Regardless, SetCPU was not a problem before the NAND). No matter, I changed the governor of my screen off AND my "normal" profile, but still no dice.
Also, could it be a memory issue? I doubt it, I hadn't installed anything else before and after the NAND, and I manually clear any unwanted running processes (and I have been, since I've gotten the phone).
So, dear XDA, what exactly is wrong with my phone? I hope its not hardware, and I'm hoping that flashing a new ROM might help, but I haven't done so until I have heard some opinions :/
P/S: Probably at wit's end here...
Edit: I'm not sure if its related, but once when I pressed the home button when all forms of input didn't work (buttons, touch screen) when I was playing Zenonia, Launcher Pro was "about" to FC, giving me the option to kill it or to wait.
le bump with a summarized, easy on the eyes version.
1 )Bad attempt at theming DF 6.1a leads to bootloop.
2 )Wiped in preparation to restore nandroid, but accidentally boot up the device instead (boots to a "wiped" Defrost without all the bells and whistles). Top half of screen during the google account setup, wifi setup, time zone set up not responding. Problem goes away after exiting set up.
3 ) Wipe again in recovery, tried to restore NAND once more, but "Error : run 'nandroid-mobile.sh' via adb!"
4 ) Power down, charge phone, successfully restored NAND.
5 ) Phone is fine until I play games (which worked fine before). Some games totally freeze up the phone, while others are still running (monsters moving on screen and attack my unmoving character), but all forms of input is not recognized (button pressing, touch screen pressing, etc).
6) These "half-freezes" (inputs do not work, but the game still is running) also occur when playing flash games, right around the time I'm about to receive an SMS.
6 ) Whatever commands I pressed while the phone was "frozen" registers when the phone "unfreezes".
7 ) Sometimes freezes cause the phone to reboot, sometimes have to pull out the battery.
8 ) If phone has been on the whole day (regardless of heavy or light usage), stock SMS app seems to slow down and become unresponsive around late evening. A reboot fixes this.
9 ) Once, launcher pro was not responding, and I was given the choice to wait or kill it, when the phone recovered from a "half-freeze" (unrelated?)
Not a setcpu problem, because I have been using the same profiles since I got the phone, but I did play around with the governors to see if that changed anything.
Not a memory issue, because I dont install much, and I regularly manually kill unwanted processes.
Not sure why your phone acts like this and don't know a simple solution. But before tracking down the error, it's mostly and surely faster to install another ROM or just reflash this ROM and only install the apps you want to try - saves you some headaches... Also try to repartition/reformat your sdcard. I too had some issues with lagging system but i was only able to resolve it by flashing another ROM. I don't think it's an hardware related issue though...
Thanks for the response
Just flashed a new ROM. Gonna poke around and see what happens. Will report back.
Whats the best way to repartition an SD? Instead of Gparted of course. I'm not on Linux (my ubuntu installation went bad).
There are definitely thread about this, but before I flashed DF 6.1a (coming from DF 6.0e), I switched my recovery to AmonRa, selected ext2 partition of 0mb (because I had a 256 partition before, and then I wanted a 512mb) and then partitioned it again with a 512mb.
Honestly, it doesn't sound like the best way to do it, but that was what some threads said.
EDIT: Phone seems fine now on GV 1.1 How could a nandroid affect the phone so badly? hrm.
Partitioning with AmonRa's recovery works perfectly fine for me. You just have to set the ext2 partition to the desired size (i use 1024 as recommended on other threads - at least for sense roms). Afterwards upgrade ext2 to etx3 and maybe ext3 to ext4 (i have done this).
I too had to throw away some nandroid backups and start clean. Don't know why. I thought it has something to do with my "experience"...
Related
This is the third time I have had this problem. Randomly my phone slows down to a halt, the data connection does not work, most setting icons take 10 minutes to load if they do at all yet my texts still work.
There are NO apps running in the task manager.
I have removed most of my programs.
My mods are just removing the TF3D crap, nothing serious.
My stock task manager icon is missing from the top right.
and when I rebooted the phone I would get two errors, one with opera and the other with ~pcom-something.exe"
The other times I reset to unit to "factory out of the box" but I am sick of resetting up the phone with my apps, mods and such.
Has anyone seen this before?
What rom do you have on your phone ? What do you mean by removing all the tf3d crap? And have you flashed different roms without using task29 in between? It sounds like its time to task29 and reflash.
Sorry, I removed the TF3D stuff with mostly registry edits. I am still on a stock 6.1 rom.
Well, it could be pretty work-intensive to try and track down exactly whats causing your slowdowns and freezes, and since you have had to keep on hard resetting it, I would think that you dont really have much to lose by flashing a new rom. If you like the stock 6.1, you could just download it from the Windows Mobile Rom Developement subforum. Alls you would have to do is hard spl your phone and then flash it, it should take less than an hour start to finish, including downloading the rom.
Also:
My stock task manager icon is also missing from the top right.
and when I rebooted the phone I would get two errors, one with opera and the other with ~pcom-something.exe"
I can set this back to a stock ROM with the phone itself and I have all my apps on my card. Doing all the registry things is a pain only because I did not memorize them... YET, haha.
Is there a better task manager to see whats eating up resources?
If you're running the ROM that actually came stock on the Tilt II, then the hot fixes for the issues you are describing can be found here on HTC's website.
http://www.htc.com/us/support/tilt-2-att/downloads/
I'm on verizon, will it matter?
Mother F-er.
Just rebooted to try and get the errors again and instead got this:
"The device is unable to boot because either you have turned off the device incorrectly or tired to install an application from untrusted source.
Press Volume Up to reset your device or press any other button to cancel.
The operation will delete all of your personal data and restore the device to it's factory default settings."
I guess my decision is made, but wow I am not happy. This phone may go into a lake.
... edit:
Volume up does not do anything. AWEsome.
Yeah it matters, here are some Hot fixes for you're touch pro II. Don't know if they will help ya though: http://www.htc.com/www/supportdownloadlist.aspx?p_id=250&act=sd&cat=all
I took the battery out again and put it back in. Same message and the volume up did not work again.
So I pressed volume up about 100 times then held down the power button. Nothing changed.
Then.... I slide open the keyboard and closed it. Put the unit down and about 45 seconds later I heard all 100 volume up presses in a row. The stock WM volume menu was over the windows boot screen, and then the task bar showed up. Then the unit shut off and rebooted but took forever. It looked normal , but SLOW.
Now:
"A problem has occurred with Opera9.exe"
then:
"A problem has occurred with cprog.exe"
WTF is going on. I have not installed/uninstalled ANYthing for weeks.
set the phone to factory defaults last night and changed everything back. Meh.
Thanks for the ideas guys and I will be doing those "hotfixes" very soon!
Cheers,
Dan
Well, this phone is doing it yet again.
It barely works.
everytime I press something it takes between 5 seconds and 1 minute to do it.
i have no signal
most programs do not even try to start
resets change nothing (done this about 100 times today)
What the hell is going on with this phone? This was just as random. Was working as normal until around noon and then it just slowed way down and I could not make calls or answer them.
Grr.
so:
when I reboot the phone, I have the green start up screen for ~5 minutes.
the phone does not work after it fully starts up.
I can not open "remove programs"
I do not have the task manager in the top task bar, but when I go into settings and open task manager, there is nothing running.
I run "cleanRAM" on level 3 and there is no change.
It is still very slow I have not installed anything new at all, so this sudden change reasoning is unknown. This may be my last windows phone as I am growing tired of these random major failures.
Well verizon sent me a new phone.
*PHUCK*, its WM6.5 and I hate it.
So since all the other threads revolving around this issue seem to be nothing more than suggestions of things to try rather than trying to determine what the problem is, I wanted to start fresh.
Here's my issue regarding reboots on my Evo (Hw 003). Simply put the phone will reboot (typically under moderate/heavy use, I've not once seen it reboot on it's own, although I can't say it hasn't when I've been asleep).
This issue has persisted regardless of HBoot Version (I've been on 0.76 ENG, 0.97, and 2.10), PRI, Radios or ROM. Trust me, I've tried nearly every combination. It even persists when fully unrooted and returned to stock.
I've obviously tried every type of wipe (both through CW and Amon's Recovery and using Calkulin's WipeAll method in both recoveries) prior to flashing roms and after restart/crashes. I've tried eliminating SD Card issues, and these issues persist regardless of whether the SD card is in or out, or whether it's corrupted or not.
Here's the only things I can definitely say regarding the reboot issue (which I do have to believe is a HW issue, although it may have something to do with the early boot sequence...see my reasoning below).
When the crash occurs, the phone ALWAYS attempts to reboot itself. Very rarely it will do this successfully (but it seems to only be successful in doing so when on customs ROMs, specifically CM7 nightlies, which makes me think that those crash/reboots are unrelated and are actually just software issues with the rom/apps in question and should therefore be disregarded).
If my phone is currently set to S-OFF, the reboots always ends with under 5 seconds on the white HTC Evo screen, then display goes black and I get five vibrates and a flashing green power LED. When this happens and the phone is connected to my laptop via USB, right after the 5 buzzes, I get a Hardware Growl notification that a Qualcomm USB device has been connected.
If the phone is currently set to S-ON, the reboots result in a bootloop that again, shows the white HTC Evo screen for less than 5 seconds, then the screen goes black, phone restarts and starts the loop again. In these cases I don't get the Qualcomm/HW Growl message.
With S-OFF the only surefire way to get a working phone back is to remove the battery for a few minutes (seems like it needs at least 3-4 minutes, which makes me think some form of volatile chip/ram needs to drain to a certain point before working again). I can always get HBOOT/FASTBOOT though, even if I just remove the battery for a second. It feels like I can get into Recovery with the battery removed for less time than it takes to actually boot into the OS, although this may be an inaccurate observation on my behalf.
With S-ON, while removing the battery seems to yield the same results as when the phone is S-OFF, occasionally if I let the bootloop play out, it will eventually hang on the white HTC Evo screen for some time, then restart and boot like normal.
---------Conclusions----------
From what I can tell this whole reboot/crash issue people seems to be having (when it isn't caused by bad flashing or improper use of the phone) can be narrowed down to two areas.
1 - There is an issue with the phone's RAM. This would make sense since there is a difference in the results of removing the battery for a short time or long time when trying to recover from a crash.
2 - It's an issue with the phone's early boot sequence. Perhaps the phone's internal memory (specifically the boot partition or wherever HBOOT/FASTBOOT is stored, not 100% sure where that actually is) has bad sectors or is otherwise corrupt.
I'm leaning towards the RAM being the culprit though, since it seems to be the only thing linking all of the different crash/reboot scenarios. And although I've heard rumblings that it may be a CPU issue, I really doubt this since I can always get into HBOOT/FASTBOOT and because when it crashes and give the 5 buzzes (which some have speculated is a Qualcomm error code for CPU's) it then seems to be communicating on some level through the CPU and USB with my laptop.
While I obviously can't replace the phone's RAM to check this, I just wanted to see what the opinion of those who are a bit more familiar with the phones inner workings than I am have to say about this.
stefpap I have been experiencing the same systems that you describe here. I am currently on the Synergy rom, but I have also experienced this while on myn 2.2 . I have tried multiple reboots/resets and clearing of the sd card except for the rom itself. I want to say that the reboots happen while the GPS is running in maps and navigation. They also seem to happen while watching 15-20 min into a movie.
Have you made any headway on the issue? I also tend to believe that the memory is running away. I have found that the battery becomes a little warm when i remove it for the reset ( I dont know if it has anything to do with this issue)
One last thing, I cant remember this happening when I first received the phone. it also wasnt rooted and had different versions of apps, but who knows.... please let me know if you have found anything about this issue.
Well as an update I uprooted my phone and took it into a repair center, they saw what it was doing (see above) and ordered me a referb. Turns out the main board was causing reboot after getting to hot.
Sent from my PC36100 using XDA Premium App
So about a week ago or so I began, out of the blue, to have power button issues. The power button would turn my incredible on when it was off. It would wake it when it was asleep/screen off. After that it became hit and miss. When the screen was on it was highly unresponsive. Sometimes it took several presses to get it to turn off, sometimes I couldn't turn it off at all. Sometimes a tap would bring up the shut-down menu as if I had long-held it. Long holding it usually didn't work either. A few times I had to do a battery pull just to shut it off. I eventually downloaded quickboot and a screen lock widget just to get that functionality back. The last thing I remember downloading before this started happening was 'reddit is fun'. I uninstalled that after the problems, but to no avail.
Now lets go over what I was set up with. I have an amoled unit. I was at the time using CM7 Final and whatever kernel was included with it. Although I have used it a lot in the past, I didn't have setCPU installed or running this time. The only root-required thing I can remember running was autostarts. No changes were made to autostarts in the weeks leading up to the problem. I have used many roms; Frankenrom, Virtuous, Ruby, ShadowRom, IncDoes AOSP, The New Guy, Warm 2.2, Redemptive, SkyRaider, Evervolv, and several of the CM Nightlies. While using Redemptive my radio completely quit working across the board. Returning it to stock and then re-rooting fixed it. As far as I can remember I had only used SkyRaider, Evervolv, and the CM Nightlies up until I was using CM7 Final.
So after the problem started happening I decided easiest thing to do would be to try and flash a nightly over it. Tried that, didn't work. That was kind of a long shot, and I decided I might need a full wipe. Did the full wipe and installed the latest nightly. The problem persisted. I think I flashed the latest SkyRaider then, still had the problem. This was starting to seem kind of serious so I did another complete return to stock. I booted into the stock rom and used it for a bit, maybe a few hours, it seemed to work. Since things seemed back to normal I flashed the latest CM Nightly again. Seemed to work for a minute, then it was back to the same old problem.
Now around this point I, for reasons I can't remember, remove my 16 GB SD card and put the stock 2 GB one back in. I have SkyRaider on that and I flash it, it works perfectly. In fact it continues to work for a day or two. All this time my old 16 GB is sitting out on my desk. I eventually decide to clean it up, deleting a bunch of stuff I didn't need on there, and throwing it back in. After putting the 16 back in the problems creep back in. Here and there, then only working half of the time, then barely working at all.
About this time I come up with the idea that maybe something on the SD card, or the card itself, is causing this problem. Seems like a long shot, but I can't think of any other reason that would fit. I do not install apps to my SD card.
So I pull the SD card out. I was at work and I didn't have my old 2GB, so I just left the slot empty. It seemed to still be messed up, but over the course of the next hour or so it began to work correctly again.
Now I'm at home and I have deleted everything from my 16GB, and reformatted it completely. I'm about to flip it back in and see how things go.
The strange thing about this whole situation was that the problem didn't seem to just start and stop. It was as if it phased in and phased out over time, but always being caused by certain things. It seems organic if you know what I mean by that.
Feel free to tell me this is a really ridiculous idea. I think it might be. Is there something critical to the android system that could possibly be stored on the SD card?
Maybe its a hardware problem that's being affected by the weather in your area, because you can run android fine without an SD card. You would be surprised how the humidity affects electronics. This is just a crazy thought to a crazy problem lol
Wow, finally there is someone else out there with this problem.
Mine didnt have this problem till i flashed MIUI latest rom....but even after somehow making it into the recovery mode...i was able to restore my previous cm7 build...
BUT....the problem persists....
So I think I am going to pull out the 8gb sd card my friend gave me from his EVO 4g.
It annoying because sometimes i cant get into even hboot with power + volume down.
I know the volume buttons work because i can change volume on phone.
I can still see the power button still being pressed down, its not stuck or anything...it works 50/50
Can you give an update OP, please?
I also have an AMOLED Incredible..and dont want/can afford another phone...
have any of you opened up your phone to see if the button was still soldered to the board?
- i did and it is, same issue.
Hi,
all seemed fine with my new, one week old One V. Till I installed GTA III. First the installer stuck while downloading the datafies. I canceled the download, restartet GTA III, but instead of completing the broken datafiles download (or re-downloading) it just startet the game and crashed the whole phone in the intro animation, that was without sound. I removed and reinstalled it, the download now finished, I could get the intro with sound, but it crashed the phone at the same moment. Since then my phone behaves like it would be very sick or hate me ;-/. After this crash it startet looping the reboot. It would boot, ask me for my SIMs PIN code, then be ok for a short time, then reboot again. This time it would boot into the desktop without asking me for the PIN. All seemed ok, but HTC's audio player forgot all the files I played (Last Played) and did not find any audio files (I have them on /sdcard/Music). It did not find them after several reboots, some of which were initiated by the phone all by itself. I then erased all the caches rebooted twice and it found the files along with the Last Played list. All seemed fine again, except the vibration of the tactile feedback would be less sharp and more wobbely. But only sometimes. Sometimes it was sharp. But besides that, all seemed to have healed itself and I could use the phone, maybe a bit slower, or maybe Avast and some tasker like app, I have running, made it a tad slower.
Then I installed yesterday's (today's ?) HTC update. Since that the phone reboots after two minutes. When I start the Preferences/Applications it takes ages to scan and most of the programs appear with their internal (com.foobar.someandroidapp) name. Just in order to change after a minute or so to their original name. Elixir2 crashes sporadically during use. Again I get the reboots without asking me for PIN.
Also, when I switch it off it shows the orange light for a minute, or so, instead of the green, though the phone is fully charged. It did not do this before. Oh, and in the meanwhile the HTC audio player forgets the MP3 files again I have on /sdcard/Music. Got no idea, what to do, since removing and reinserting the SD card did not help.
Also, I have the feeling, that something in the list of installed apps in the app-database crashes it. Where can I find it?
I can not even reset to factory defaults. At least I tried. It said it's doing it, then rebooted and all my stuff was there again (ie no reset).
It's crap! I need my phone's camera the next days because of some big Open Air event I am on.
See here for a little video about what happens... You need to download the vid (ca 80MB) and turn it around 90 degrees, sorry.
zmix said:
Hi,
all seemed fine with my new, one week old One V. Till I installed GTA III. First the installer stuck while downloading the datafies. I canceled the download, restartet GTA III, but instead of completing the broken datafiles download (or re-downloading) it just startet the game and crashed the whole phone in the intro animation, that was without sound. I removed and reinstalled it, the download now finished, I could get the intro with sound, but it crashed the phone at the same moment. Since then my phone behaves like it would be very sick or hate me ;-/. After this crash it startet looping the reboot. It would boot, ask me for my SIMs PIN code, then be ok for a short time, then reboot again. This time it would boot into the desktop without asking me for the PIN. All seemed ok, but HTC's audio player forgot all the files I played (Last Played) and did not find any audio files (I have them on /sdcard/Music). It did not find them after several reboots, some of which were initiated by the phone all by itself. I then erased all the caches rebooted twice and it found the files along with the Last Played list. All seemed fine again, except the vibration of the tactile feedback would be less sharp and more wobbely. But only sometimes. Sometimes it was sharp. But besides that, all seemed to have healed itself and I could use the phone, maybe a bit slower, or maybe Avast and some tasker like app, I have running, made it a tad slower.
Then I installed yesterday's (today's ?) HTC update. Since that the phone reboots after two minutes. When I start the Preferences/Applications it takes ages to scan and most of the programs appear with their internal (com.foobar.someandroidapp) name. Just in order to change after a minute or so to their original name. Elixir2 crashes sporadically during use. Again I get the reboots without asking me for PIN.
Also, when I switch it off it shows the orange light for a minute, or so, instead of the green, though the phone is fully charged. It did not do this before. Oh, and in the meanwhile the HTC audio player forgets the MP3 files again I have on /sdcard/Music. Got no idea, what to do, since removing and reinserting the SD card did not help.
Also, I have the feeling, that something in the list of installed apps in the app-database crashes it. Where can I find it?
I can not even reset to factory defaults. At least I tried. It said it's doing it, then rebooted and all my stuff was there again (ie no reset).
It's crap! I need my phone's camera the next days because of some big Open Air event I am on.
See here for a little video about what happens... You need to download the vid (ca 80MB) and turn it around 90 degrees, sorry.
Click to expand...
Click to collapse
here is what to do:
format the sdcard
factory reset your phone
Thanks, 1ceb0x, this is what I did. It all went fine. I have now applied the firmware update to 2.08.401.2, that got sent out these days. Seems to work out nicely.
What can I do, that I do not have to reformat in the future? Are there any utilities, that do snapshots of the system over time? Like Time-Machine for OS X does?
It's happening again. This is still the stock ROM, with the official (or was that two cuh?) update(s) a week ago.
I did not install any utilities, from which I think, they could go deeper into the system, like Avira and Automagic. I need a way to analyze, what my system is doing.
Oh, and it is reproducable: Mounting the phone as USB drive on a computer and, after work has been done, unmounting it on the computer, changing the USB mode on the phone. Now it starts. CPU seems to be up to 100% (UI becomes sluggish), apps behave strange (hadphone was in, speaker sounded, today appstore does not install apps, does not even connect, X-plore leaves a notification on screen after I quit, etc.). I had it two days ago, but the I rebooted a few ties, switched it off, took it from the USB cable and used it a little bit from battery. After this all was fine. But now that does not seem to help either.
zmix said:
It's happening again. This is still the stock ROM, with the official (or was that two cuh?) update(s) a week ago.
I did not install any utilities, from which I think, they could go deeper into the system, like Avira and Automagic. I need a way to analyze, what my system is doing.
Oh, and it is reproducable: Mounting the phone as USB drive on a computer and, after work has been done, unmounting it on the computer, changing the USB mode on the phone. Now it starts. CPU seems to be up to 100% (UI becomes sluggish), apps behave strange (hadphone was in, speaker sounded, today appstore does not install apps, does not even connect, X-plore leaves a notification on screen after I quit, etc.). I had it two days ago, but the I rebooted a few ties, switched it off, took it from the USB cable and used it a little bit from battery. After this all was fine. But now that does not seem to help either.
Click to expand...
Click to collapse
Wow, that's an amaizing type of error, I can assume a tad sdcard error, but I'm not sure of that.
Ken-Shi_Kun said:
Wow, that's an amaizing type of error, I can assume a tad sdcard error, but I'm not sure of that.
Click to expand...
Click to collapse
Szia
Yes, that's what I thought, too. I checked the file-system, I also ran a bad-blocks check, though, I am not sure, whether the utlity can do that reliably for an SDcard (since it has been written for a magnetic hard-disk). SDcards have a different technology. I got no reports about failures.
Now, that I hooked the phone to the debugger, I see the watchdog kicking in, but the traces.txt is being written to a directory, only root can access (and I am not). So I am still in the dark. Reports on the net have shown certain Sense devices to hace similare problems, with either too many apps installed onto SD or too many MP3s. The bugs are different. In the latter, the audio-player app of HTC is at fault, this seems to have been confirmed by HTC. Not sure, which Sense version, though, the phone was running ICS, but not a One series.
I'll hunt for the bug for a few more days, then I am going to root, custom kernel and custom ROM. Only convern I have with this, that I do not want to lose anything Sense related, because I love it so far. Ideal would be a ROM, that ported the S or X Sense, since those have more home-screens.
Yep usually clearing your caches returning your phone to factory mode should work, if not use the back nandroid.
Thread moved to.Q&A. Please keep all question related threads there. Thank you.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my HTC One X, using XDA Premium.
[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen
Hello everyone,
I would like to say first of all to the community, thank you for SHARING KNOWLEDGE. That is the key to everyone's success.
Now down to the gritty. My, now, I guess, mess of a LS980. For starters, the phone was running I would say very well considering my abuse. Big overclocks, gaming hardcore, and pushing the storage space hard. I performed a very easy and simple rooting and recovery program installation. If I remember properly, it all started with an app/.apk that sparked my interest with making the phone mine, was Autorec? (red roundish logo?) In some time I decided to install my first aftermarket ROM. I chose and installed without any issues , Cloudys G3 ROM. I cannot however remember the version number. It is by no means recent. I think I installed it last September so maybe 1.0 or 1.2 (sorry so much bad luck with stuff recently) TWRP version 2.7.0.0 is my recovery, and its functional. Unfortunately I do NOT have my apps backed up. I have no space. (just managed to get about 7GB on this PC to try to back them up but there is not external back up option, UNLESS you are OTG cable equipped I am not )
Now, I think, (this has been the state of the phone for about 3 weeks now) this all started to go south when I saw there was a Dorimanx OTA app in the play store. I used his Kernel for as long as I have had the G3 ROM installed. With no problems. So I figure this would be easier for me than button mashing trying to get into recovery mode without popping my screen out the front. LOL Upon using the app, I was informed of an update, I read the included information, and generally knew the deal. I allowed the app to download what it needed and restart and install like a good little computer. And this is where it gets a little grey for me in terms of order and symptoms. I remember checking the status of the install and it read failed! I looked into the reason why, and I was just plain full of junk. I then uninstalled painfully a bunch of rarely if that, used apps and gained back about 2.2GB of space. I ran Dorimanxs app again and let it do its thing and reboot. And again it reported fail! I looked into it more and noticed there were newer Kernels than available on his inter-web. Alpha versions. I located them on my device and rebooted into TWRP mode and selected , then flashed his 10.4.1 Kernel. Everything went fine. Phone reboots, the LG logo is no longer animated, and takes a bit longer to actually boot into a GUI. But it was, luckily.
So now, the phone would be a usable thing for about 3 minutes tops, before a power off, to a reboot. Which at first I didnt notice to be a boot loop. My battery surprisingly went from full to about 6% in no more than 15-20 minutes. I noticed the battery was getting warm like I was running the CPUs maxed under a serious load for a good half hour. Around the range to make someone pull it out their pocket wondering wth? So after the next reboot, power cycle, I jumped back into TWRP mode, and dug around for what I thought was the culprit, Xposed. I was having the worst time with my phone after a major Xposed framework error. I picked up my phone one day and out of the blue the xda framework was telling me that there were so many errors with it and my apps that ran fine, not being installed or activated. Upon looking into it, it was removed from the phone. I belive the order was , stable, 2.5/ 2.6, then I tried the beta 2.7. and thats the version that eventually , either broke, or uninstalled, I think, during those frequent Crashes! I tried to install the previous versions, even going back to the versions that came out last year like 2.4 . But none would install. And the phone grew more unstable in terms of its cooperation with its software. My normal apps and games worked fine. The phone worked the same, the music player, but there were apps that only can work with xposed that I utilize constantly, that were kaput. So I left the phone off. For a while. I had/have no time and really no resources to research and rescue a sunken ship. I come back about two weeks to it and I take a look around in the phones storage and hunt for any kind of recovery and disabler. I found xposed's disabler and flashed it. Same luck as before. About 3 minutes on, then dump.
I dig some more and found a ccc71 back up folder with some hearty backups that I didn't know were still there (no wonder I was always loosing space) and found another xposed installer.zip . I figured well , it didn't make any sense trying to disable something that wasnt enabled in the first place. (thats why I walk away and come back . fresh mind to tackle what stumps me) So I flashed the installed zip and reboot. Same thing, but now it started to loop around one minute. I power down. Found the recovery.zip that was saved on the beater PC and adb pushed it over the the phone. Im not good enough to adb install it. So TWRP'd it and rebooted, and d'oh! Now we just have the motionless LG ball, but flashing blue and green LED. And after about 2 minutes it would black screen, but be on. Not hung or anything. I connected to the PC, it never finds the right stuff but I used adb to verify state. And it said device. It still could communicate and push. I had it dump its debug, surprise! as it flashes that crap as fast as it can up the screen. But Im a PC guy so it was a fun, pause/break over and over till I found something useful. I saw some things that I could recognize like, failed starts, and longer than normal (for a speedy experience) function or call times, but nothing that slapped me with a red flag.
And that ended that nights attempts to fix thanks to the slowest no ram having box I was using to try to learn how to have the debug save to a .txt file on my PC so I could take a good look at the results.
Upon reading forum after forum, I came to something that looked promising, telling me that, that particular boot issue was due to the wrong radio being installed. So I hunted, and hunted, and laaaaaged my arse off and finally found it. Great I thought. Powered up ten or twenty times, finally get into TWRP, tried to flash it. BBBBBAAAAAANNNNT! nope. Downloaded another copy of the file and tried it again. No luck. ( I must say not until roaming around in these forums tonight did anyone bother to mention that you dont flash that radio. You instead have to inject it via LGFlashTool, which I have used before, and its a pain in the butt.
But before I go any farther, make anymore mistakes. I need some help.. I would really LOVE to be able to flash this , slap that, curse its name then hug it and get her working, without having to ditch my 492 apps. If I would have to say goodbye to happy times, I would like to say good riddance to ugly and annoying G3 ROM. I like not flat UI. My phone was depressing me every time I had to do any navigating around inside it. So I would love to go back to KK Stock LG ROM if push came to shove. But if possible I would just like to "repair, and regain access into the phones GUI system". So I could backup my apps. And eventually labor back to OEM Kitkat.
I apologize for the length of the post. But I just dont see the point of ping ponging with partial exchanges of information. I hope I have made my situation clear, and someone knows of someway, I can get my GUI/phone working again. Thanks to all in advance.
"a non functional smartphone, is an oxymoron"
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
strangely enough
siggey said:
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
strange thing,
just about 5 minutes ago, the phone, which I left on sitting at the LG screen by accident yesterday after posting the above, changed screens and presented me with the Launcher selection screen.
I immediately noticed that it looked wrong. Like if the resolution was way off. Like an old low res screen, very dull, sort of blurred looking.
I figured what the heck and tapped the screen and it of course did not immediately respond. It took its sweet time , about 30 seconds to show a change. The menu disappeared and a error message along the lines of , android system UI has crashed.
That is not the message verbatim, it was gone to fast for me to take it all in. And now its sitting at the blank powered on and repeating blue/green LED.
I havent done as you suggested yet. I kept getting results from Norway and other places and didnt understand a thing. But I found a TWRP update from Dorimanx, there was a link to it. And now I have to find my version of the OS. And to be clear, were you suggesting doing a re install, basically a file overwrite? And if so, when doing something like that, do you wipe the Dalvik cache ? Or do you just "dirty flash" it?
Thank you ,
I think that your screen is overheated. Never let the phone in bootloop for long time, it can destroy the screen.
About the cache, is better to clean it, but if I remember well the rom installer alredy do this.
_____________________________________Read more write less and be smart