Database Users

Temperamental...

My G1 has recently started playing up. The problems first started with cyanogen 4.1.9999 - it would loose signal, but a reboot sorted this out and it may only happen once every two or three days if that. It was an unstable ROM, no biggy.
But then one day, after rebooting, it got stuck at the android screen then just turned itself off. This repeated several times before it just wouldn't turn on. I left it for a while and tried again later, it turns on, boots but no signal. Rebooting did nothing.
I reflashed (without wiping) cyanogen 4.1.999. and everything seems okay. But then the phone started crashing and rebooting rather a lot, and rather unpredictably. So I wiped, flashed the ADP rom and then cyanogen 4.2.1 rom. This process was a massive brainache - plugging in the usb cable managed to crash the phone within 2-5 min guaranteed, it automatically rebooted.
So here I am. Cyanogen 4.2.1 - after a complete sdcard format, wipe, ext3 repair and flash. The problems still persist! But it's temperamental, a lot of the time I loose signal still, it often reboots itself and hates anything plugged in the usb when it's turned on - making charging the thing awkward.
I used the log collector app to get these logs
http://nopaste.info/17b5351296.html
http://nopaste.info/2e98b9d044.html
At some point during those logs, the signal is lost. The log collector doesn't seem to retrieve a very long backlist, these were taken minutes apart but don't overlap, so I haven't caught a crash. I'm not sure if there are better ways to view logs/debug?
But it's all very temperamental. Occasionally it boots up and life is fine. But more often than not it will loose signal and reboot itself somewhere along the line.
Has anyone come across anything like this before? When it looses reception if I manually try an connect to a network it will say
"This SIM does not allow a connection to that network"
Click to expand...
Click to collapse
I've read that could perhaps be a problem with the sim... but the sim wouldn't cause reboots would it?
Any advise would be great. I bought the G1 off ebay just under a year ago, so no warranty.

So many problems with new HD2

Hi
I'm having so many issues with my new HD2 i think i must have the unit they were using for footie practise in the stock room.
Anyway i got my unit from Handtec last week. It has been completely unstable but here's a list of what's happen just this morning...
The Sense music player, previously working fine stops working after i placed some additional mp3s on the sd card - pressing the music icon on HTC Sense results in HTC Sense restarting - every time. Only resolved by a hard reset.
Multiple occurrences of "A problem has occurred with device.exe" , i think generally when i try to turn on the phone connection but i'm not sure of this is always the cause or not.
The phone radio connection goes off and wont turn back on despite going into comm manager and pressing the on/off soft button multiple times.
I press the power button button to bring the phone out of stand-by and it goes back to stand-by a second later, over and over again. I haven't even got time to slide the unlock icon across the screen. Then finally after a number of attempts it will either stay on, or put itself through a soft reset without me having initiated it.
How long does it take for HTC Sense to load on others phones? It can take mine minutes to move from the Loading HTC Sense screen to showing the actual Sense interface.
After a hard reset and allowing the device to fully boot up, i promptly got "A problem has occurred with device.exe" as soon as i tried to turn the phone radio on. this is before doing ANYTHING else after a hard reset.
I then got "A problem has occurred with filesys.exe" when trying to get weather for the first time. then the device shut down. Then it went back to the behaviour of going to stand by 1 second after turning iton. This is all within the first 2 minutes of a hard reset.
I really haven't one anything to this phone. It still has the same ROM that it has when i received it - 1.43.70124 from memory. I would tell you exactly except at the moment its refusing to open the 'Software Information' screen in Settings-About Phone. It just freezes up instead (that's a new bug in the last 5 minutes, woot!)
Does anyone have any ideas? i'm hesitant to put the 1.48 rom on in case i need to return the unit and they refuse due to me changing the rom.
Thanks.

My advise is to flash it with the same ROM version. Maybe the ROM is corrupted. If that still doesn't work, get a replacement.

xdaadam said:
Hi
I'm having so many issues with my new HD2 i think i must have the unit they were using for footie practise in the stock room.
Anyway i got my unit from Handtec last week. It has been completely unstable but here's a list of what's happen just this morning...
The Sense music player, previously working fine stops working after i placed some additional mp3s on the sd card - pressing the music icon on HTC Sense results in HTC Sense restarting - every time. Only resolved by a hard reset.
Multiple occurrences of "A problem has occurred with device.exe" , i think generally when i try to turn on the phone connection but i'm not sure of this is always the cause or not.
The phone radio connection goes off and wont turn back on despite going into comm manager and pressing the on/off soft button multiple times.
I press the power button button to bring the phone out of stand-by and it goes back to stand-by a second later, over and over again. I haven't even got time to slide the unlock icon across the screen. Then finally after a number of attempts it will either stay on, or put itself through a soft reset without me having initiated it.
How long does it take for HTC Sense to load on others phones? It can take mine minutes to move from the Loading HTC Sense screen to showing the actual Sense interface.
After a hard reset and allowing the device to fully boot up, i promptly got "A problem has occurred with device.exe" as soon as i tried to turn the phone radio on. this is before doing ANYTHING else after a hard reset.
I then got "A problem has occurred with filesys.exe" when trying to get weather for the first time. then the device shut down. Then it went back to the behaviour of going to stand by 1 second after turning iton. This is all within the first 2 minutes of a hard reset.
I really haven't one anything to this phone. It still has the same ROM that it has when i received it - 1.43.70124 from memory. I would tell you exactly except at the moment its refusing to open the 'Software Information' screen in Settings-About Phone. It just freezes up instead (that's a new bug in the last 5 minutes, woot!)
Does anyone have any ideas? i'm hesitant to put the 1.48 rom on in case i need to return the unit and they refuse due to me changing the rom.
Thanks.
Click to expand...
Click to collapse
The Sense Music Player on my HD2 crashes everytime it's tab is selected when there are music files on my memory card. Since I need music on my phone, I disabled the Music Tab and got Conduits Pocket Player instead. Works great, and is fast and smooth.
Never had a problem/error message on my HD2.
I'm also using the 1.43 ROM, got mine from eXpansys.
Try doing another hard reset and see how it goes... It shouldn't be spitting out fault messages after a hard reset...

The sense music player seems to have a problem if you load too much music into a memory card at any one time.When I first got my 16 gig microsd card, I decided to fill it up with music, and when the sense music player tried to scan what was on it, the whole sense interface just froze and I had to soft reset ny phone.
I found a temporary solution to the problem by having the computer connected via ActiveSync and just transferring the files over whilst the sense music tab was open. This way, the program can sorta scan each song as it is being added rather than bomnbarding it with a whole heap of songs at once and causing it to crash.
By doing it this way, I've managed to put around 7 gigs worth of music on my phone. I hope htc fix this soon as well as it is obviously another bug with the phone.

Hey, don't be disheartened; my first set was like that as well. device.exe error on the first boot up, and pretty much your experience. Slow Sense UI loading, unstable device, etc. Get a new set if you can.

You only have one option- send it back
It's patently a hardware or initial ROM fault. Don't bother with trying to flash a new ROM, just get in touch with Handtec for an RMA

Xeon said:
My advise is to flash it with the same ROM version. Maybe the ROM is corrupted. If that still doesn't work, get a replacement.
Click to expand...
Click to collapse
Thanks for everyones advice, its appreciated.
Attempting to flash the same ROM onto the device is a good idea, too obvious to occur to me! Out of interest, if I was to flash the 1.48 WWE ROM and it didnt fix anything, would it allow me to downgrade to the 1.43 WWE ROM again? or would the installer scream at attemptoing a downgrade?
It may well be a hardware error though, there's so many things going wrong. But then you would think a hardware error would stop it working at all. Maybe its some dodgy memory... well im going to try flashing 1.43 for now and will wait for advise on the upgrade followed by possible downgrade idea (in case i need to return it - trying to avoid that as im in Oz and trying for a replacement to the other side of the World at Xmas just sounds like a bad idea).
Thanks

stick on 1.43 and just wait until an official update has been released,

Why would you want to put yourself into such situation. Don't mess with the device. If you flash it with 1.48 and fail to downgrade whatever the reason is, you will void the warranty. Flashing 1.43 should tell you if it's a software or hardware error. If it's not a hardware and 1.43 solved the issues, you're free to do whatever you want with 1.48

bungfritz said:
The sense music player seems to have a problem if you load too much music into a memory card at any one time.When I first got my 16 gig microsd card, I decided to fill it up with music, and when the sense music player tried to scan what was on it, the whole sense interface just froze and I had to soft reset ny phone.
I found a temporary solution to the problem by having the computer connected via ActiveSync and just transferring the files over whilst the sense music tab was open. This way, the program can sorta scan each song as it is being added rather than bomnbarding it with a whole heap of songs at once and causing it to crash.
By doing it this way, I've managed to put around 7 gigs worth of music on my phone. I hope htc fix this soon as well as it is obviously another bug with the phone.
Click to expand...
Click to collapse
I also had this problem, found it was nothing to do with the above, there was just one song that it didnt like the file name off. It had % and a few other sybols in it, changed the name it was fine.

Just wanted to update my own thread.
I tried reinstalling the 1.43 ROM completly as suggested and it seemd to solve most of my issues for a few hours then they all started showing up again along with more new ones... but...
I then went and bought a replacement SIM card from my carrier as my old sim was 6 years old. Put it in the phone and hey presto, my HD2 has magically come good! About 48 hours now, and considering i couldn't go more than a few hours previously without having to pull the battery, soft or even hard reset, im calling it fixed!.
Now i have no idea why an old sim would affect parts off the system that are not to do with making phone calls but all i can say is a new sim has solved all off the freezes, glitches, basically evrything. The device is just stable now. So my advise to anyone who thinks they have a bad 'un, at least try replacing your sim before returning it.
Oh and the old camera patch seems to be good as well.
I do love a happy ending.

LOL, windows mobile is never stable, I buy it just for fun.

you might want to edit the title of the thread now that your problem's solved so everyone can learn from your XP

loomx said:
I also had this problem, found it was nothing to do with the above, there was just one song that it didnt like the file name off. It had % and a few other sybols in it, changed the name it was fine.
Click to expand...
Click to collapse
Yep, if there is a foreign letter or some odd character in the title/artist/album of a song, it can cause manila to crash

xdaadam said:
Just wanted to update my own thread.
I tried reinstalling the 1.43 ROM completly as suggested and it seemd to solve most of my issues for a few hours then they all started showing up again along with more new ones... but...
I then went and bought a replacement SIM card from my carrier as my old sim was 6 years old. Put it in the phone and hey presto, my HD2 has magically come good! About 48 hours now, and considering i couldn't go more than a few hours previously without having to pull the battery, soft or even hard reset, im calling it fixed!.
Now i have no idea why an old sim would affect parts off the system that are not to do with making phone calls but all i can say is a new sim has solved all off the freezes, glitches, basically evrything. The device is just stable now. So my advise to anyone who thinks they have a bad 'un, at least try replacing your sim before returning it.
Oh and the old camera patch seems to be good as well.
I do love a happy ending.
Click to expand...
Click to collapse
Thanks for the update. Good to hear you're happy with HD2 now .

[Q] A few issues regarding winmo and android

Good morning all. I have a small amount of knowledge about this device (I’ve read a fair bit) but would still classify myself as a novice user. I am able to flash my device and have had android running for a while now. I have a few issues, and just want confirmation that I’m not doing anything stupidly wrong.
Firstly, I have flashed to a number of winmo roms, all with varying degrees of usability. I found them to be slow compared to android. All my rom including the last two roms, chuckyrom tabtastic and chuckydroid, have given me a few issues of varying degrees. They freeze a lot and require a soft reset or to pull the battery. Sometimes, if I try and restart straight away, the red writing on the first screen doesn't come up and the phone vibrates 4 or 5 times. Further to this, they may restart midway through booting up, or if I am transferring a large amount of data or using my phone as a wireless hotspot the phone also resets after a while. I have noticed the phone gets quite warm during this. Best results for a reboot come after pulling the battery and leaving it for 15-20 minutes.
Secondly, I have used a number of different android builds (all HTC based) and whilst generally the phone does not freeze when it is in idle mode, it freezes up to 15-20 times a day when using applications such as facebook, internet explorer, music etc. Is this normal?? I don't get any force close notifications. When people say it is “relatively stable” what does this actually mean – no freezing, 5 freezes a day, 50 freezes a day?? The device also freezes when syncing all data. Sometimes when I am in a call, if a change occurs on the device (text message or other notification comes in, even when on the move which I’m guessing may be location changes in the system) the phone freezes and emits a “bzzzzzzzz”ing noise (well, I don't know how well the word “bzzzzzz” conveys what I’m trying to say, but you may get the picture). All this in turn leads to me needing to re-boot, which then brings into play the issues of rebooting above.
The other day, I noted that the micro-usb cable had what appeared to be small burn marks on it, and the contacts inside the micro-usb cable were a bit corroded/eroded. I do remember a few weeks ago where my phone froze in the middle of the night whilst on charge and the phone became quite hot, possibly resulting in the damage to the cable. Yesterday, I got a new cable and woke up this morning with the phone quite warm again (battery temp was at 39 degrees). This was all whilst using android.
I have tried a number of different winmo roms and android builds, flashed radio, task29, different micro sd cards, formatted sd card etc. I am thinking of reflashing back ot the original rom and if I still have the same issues then sending away to get it fixed. Problem with this is that Telstra here in Australia claim it will be a month and that no replacement phone will be given to me in the meantime. I think I am paying about $160 a month at the moment – surely this is a bit slack not to give me a replacement phone in the meantime? Can anyone share their experiences with Telstra and/or tips when dealing with them?
Any help with the above would be appreciated. Thanks a lot.

Moto Z Force - Restart Loop

I'm having this issue on my 2 week old Moto Z Force.
I actually noticed a similar issue on a display model in Verizon but chalked it up to just that.. a display model in Verizon and I carried on with my purchase.
I've had a few experiences where it randomly reboots and then it's good to go again. Seems to happen more frequently when the phone is in high use, so I suspected an issue with RAM being full? The restart seems to take place at the same part of the startup animation every time.
TODAY - phone was in pocket while I was on a call for work and I felt it vibrate on a consistent interval. When off the phone, I looked at the phone and it is in a restart loop. The only thing I can do at this point is hold the Volume Down key to get into BIOs (through the rebooting loop) and then I have the following uptions:
1) Start
2) Restart Boot loader
3) Recovery Mode
4) Power Off
5) Factory Mode
6) Barcodes
7) BP Tools
8) QCOM
9) Bootloader Logs
If I sit in this menu inactive for awhile it will timeout and just shut the phone off until I turn it back on and then the loop resumes. I'm beginning to think I need to go with option 5 here... any help is appreciated...
No new apps were recently installed. I barely used my phone the morning when getting to work besides charging it to 90+/- % on my way in.
First I buy a hand grenade of a phone, forced to return, and now I buy a phone that is actually showing me a big issue (it is getting hot too). I'm going to let it sit off before trying a Factory Mode. :crying:
Video of the cycle here: https://www.dropbox.com/s/v7dc6erfydj87ib/Skys Phone.MOV?dl=0

Better ask in a Moto Z Force subforum.

SteveHG said:
Better ask in a Moto Z Force subforum.
Click to expand...
Click to collapse
Thanks Steve. Any suggestion on where would be best? I would have thought the Q&A would be accurate...

I have had this phone for just over two month and have not had any similar issues. I assume that you've already tried options 1, 2, and and 4. Have you also gone into recovery to see if you can clear the cache?
I would personally return it as broken, but I save everything important to my SD, just in case this kind of thing happens.

I had this very same issue. I did a hardware replacement with Verizon and the new phone works great.

broprah said:
I had this very same issue. I did a hardware replacement with Verizon and the new phone works great.
Click to expand...
Click to collapse
Awesome! Glad to hear that it worked out for you. Fingers crossed they don't give me a refurbished model (again, mine was 2 weeks old) and that I have the same luck as you.
rmonjay said:
I have had this phone for just over two month and have not had any similar issues. I assume that you've already tried options 1, 2, and and 4. Have you also gone into recovery to see if you can clear the cache?
I would personally return it as broken, but I save everything important to my SD, just in case this kind of thing happens.
Click to expand...
Click to collapse
I have tried all of the options at this point and none of those work. I can't even get into recovery. Every option does the same thing... reboots, reboots, reboots, etc.
New phone should be here tomorrow. I've got the good old run around on this one though and I'm not happy about it with Verizon and Best Buy. Best Buy's return policy is 14 days and I ran into issues on day 16, no exceptions according to them and off to Verizon I go where I had to purchase a temporary flip phone for the week my phone has been out of commission.
I'm in need of a new SD card before I put anything on there, it has been flaky. The only thing I care about on my phone is the media (photos, videos, and music), all of which are on Google. The crap thing is that now I need to spend another X hours putting all my apps, passwords, etc. on it to my liking. Just did this when moving to the Note 7, then Moto Z Force, and now again with the replacement. Starting to get annoyed.

Update - when switching to the replacement device I found the issue followed to the new phone... Meaning the issue was with the SD card or the SIM card. Found it was an issue with the SD card after switching between the two phones and experimenting. Unreal. Who would have thought?!
I will be formatting the card and keeping this thread posted on if that resolves it or if it's time for a new card (as I mentioned above).

I am very hopeful with your post. My phone has been going crazy with the rebooting mode for two days now. I brought it into Verizon yesterday but all of a sudden (of course) it started working. Now today its gone back to rebooting, over and over and over again. 2nd day in a row I am going to waste my lunch hour and run to Verizon. This time I will ask them about a new SIM card. BTW... I just got a new (refurbished) less then a week ago.

TBabbs said:
I am very hopeful with your post. My phone has been going crazy with the rebooting mode for two days now. I brought it into Verizon yesterday but all of a sudden (of course) it started working. Now today its gone back to rebooting, over and over and over again. 2nd day in a row I am going to waste my lunch hour and run to Verizon. This time I will ask them about a new SIM card. BTW... I just got a new (refurbished) less then a week ago.
Click to expand...
Click to collapse
I just fixed my Moto Z Play by removing the SD card... for the second time... -_- I've had a previous issue where my phone rebooted as part of an update and it stopped seeing my previous SD card. After checking the SD card in various other systems, I found the SD card was completely shot. After some digging online, there is apparently an issue with the new Moto Z's that if your SD card isn't fast enough (somewhere around 85-90+ Mb/s)m, the Moto Z will slowly start to eat your SD card until it fails and causes issues for your phone. In this case, my second SD card failure was that my phone went into infinite booting loops until I removed the card. -_-
This card lasted longer, mainly I think due to the fact that it was larger and faster then my previous one, but it looks like I will need to get a new fast card.
Anyways, I hope this helps you or anyone else who comes across this thread.

About 2-3 weeks ago, the same thing started to happen to me, after that, phone started to act crazy...
-Bluetooth connection was working but glitching,
-Overheat (bottom of the phone) then started reboot in loop (until at start I'm able to turn off wifi). Did everything your supposed to do, clear cache, forget network, deleted my latest app, reboot, reboot in safe mode, remove sd/sim tray... the issues we're still there...
-After a few days of repeating all those steps (or don't know what I did), I finally got rid of the oveheat reboot loop when the wifi is on. But can only see and connect to 2,4g network, no 5g (doesn't see any) and no Bluetooth (turns on, but doesn't see anything), every other device in house works and connect like they should.
-the setting app, and the phone app started to be slow (freezes for a few seconds before the system ask you if you wanna wait or close the app, I choose wait and the app unfreeze)
-Ive tried the rsa (repair system assistant) from verizon without any fix
-finally decide to go for the factory reset. It fixed the freezing issues, works like a charm, but still no 5g wifi nor Bluetooth...
Is there a driver update possible for this ? Or because of overheat it might have damage the device...
I have the phone since September, never had any issues, went through all update, force droid edition xt1650-02, build ncl25.86-11.5, nougat 7.0 (wish verizon would update to 7.1.1 anytime soon), since its gsm unlocked, I'm using it on a Canadian network (Fido)

thanks for this thread. It was able to help me diagnose my wifes phone. The SD card she has been using since her DROID CHARGE (2011!!!) finally bit the dust in this phone. I swapped it out for a new Sandisk micro sdxc uhs-I up to 80 MB/s card class 10 and it booted. funny thing was she was not even storing pictures on the card.

Motorola Droid Z Force restarting (Bootloop)
My motorola z force has started to boot loop restarting again and again ... i have tried following
full formatting from recovery twice, phone starts well but when i turn on my wifi it keep restarting ..
if i turn my wifi off, the phone works good but as soon as i turn on my wifi boot loop starts again and again.......
i guess i need to flash the firmware but dont know how to flash new firmware ....
XDA very big name .. i need help....

alidanwer said:
My motorola z force has started to boot loop restarting again and again ... i have tried following
full formatting from recovery twice, phone starts well but when i turn on my wifi it keep restarting ..
if i turn my wifi off, the phone works good but as soon as i turn on my wifi boot loop starts again and again.......
i guess i need to flash the firmware but dont know how to flash new firmware ....
XDA very big name .. i need help....
Click to expand...
Click to collapse
I've had bootloops happen a couple of times for different triggers, and I still run the phone stock since release date with no updates ever taken. This has worked to correct the issue for me a couple of times. Give it a try:
Let your phone get down below 5% battery life, then plug into the turbo charger. Then fool around with whatever triggers the reboots.
Eventually the phone will not restart because the phone's battery needs to charge a little. When phone charges beyond 10% try to turn the phone back on, and see if boot loop persists. If it persists drain below the 5% battery life and try again. Usually, when I have fooled around with this scenario two or three times the bootloop has corrected itself.
Hope this works for you. Good luck.

Thanku, I will definitle give it a try .... and i am updated to nougat all updates till date installed...

Still restarts.... its been a month... without solution..

alidanwer said:
Still restarts.... its been a month... without solution..
Click to expand...
Click to collapse
A couple of weeks ago, the restart loop happened to me again, and my usual tinkering while connecting and disconnecting Turbo Charger wouldn't work. So I did some research on "stuck power button" or "power button not working".
I did the following:
I blew with my mouth over the power button (kind of like puting your lips in position to whistle)
I also gently tried to clasp the power button using a pair of tweezers, but couldn't. Instead I just kind of lifted/tugged-on the power button from the top and bottom.
I feel like I didn't really do anything, but the phone has been working for over a week now. Maybe pure luck.
Its weird, this made me think it is a hardware issue, but somehow the phone reacts as if it were software related.
Give it a try. Hope you have some luck.

Help - Random Reboot Problem

This is an ongoing, intermittent and devastating problem I have. My phone will be working perfectly fine, then all of a sudden it will randomly reboot. Then it will work for a few minutes or hours, then randomly reboot again. Then for a shorter time and reboot again until the phone basically can't even get through the bootup process without rebooting. It will be essentially bricked for anywhere from 1/2 a day to nearly a week (though it usually manages to get to working for 15 minutes at a time for most of the week. Then, all of a sudden and for no reason I can tell, it will just start working fine again for anywhere from several days to a month. This has been going on for at least 6 months.
It reboots during any manner of activities with the most common being phone calls, texting (I usually use Handcent Next SMS), anything with the keyboard (stock), browsing, swiping on the home screen, etc.. Really anything causes it, including it just sleeping with the screen off. The same problem occurs when in Safe mode, with or without the SD card (using as just extra storage, not phone memory), and with or without the SIM. It doesn't matter if it's plugged in or not. I have noticed what seems to be a greater tendency for rebooting to occur when the battery is low.
I am on T-Mobile (if that matters in any way for OTAs and such) and running the stock ROM without root. I'm about to try a factory reset but that has not been a permanent solution in the past.

so I just did the factory reset and it rebooted during the initial phone info setup (select your language, etc.)... I think it's toast... Does anyone know if this is the sort of thing that can be repaired for <$100 or should I just buy a new phone from ebay?