Ok it seems my curse is still upon me, after losing GSM on my old phone then rushing through a guide which helped over night my phone gave up its go for life. Trying to do jtag (great guide scholbert and thanks for the help) I bought a second hand pda (another Mda Vario II) as a fresh start.
Down to the problem, after my experience with my last phone I replaced it with the same model and decided to keep away from flashing the bootloader/radio as that was what screwed me the last time (ironically a stock rom did the deed) and noticed after 1 hour of using my phone it would randomly enter bootloader when I switched it on. After a couple of resets though it did finally boot so I decided I could live with that. I then flashed payes rom (as its os only) yet the problem still lived on like I expected.
Removing the storage card has not worked yet sometimes I notice the phone flashes up with image not found which is weird but not all the time
The problem is very annoying as sometimes I will be resetting the phone for ages (an hour is the record) or will boot after one reset, I have also tried set 16 0 and set 14 0 with no luck, I am on Windows 7 so I have to use nueTTY instead of MTTY yet with access to MTTY it still has not worked.
Any ideas what to do next?
Sorry if I have explained in too much detail causing some people to not understand, I can explain again if your confused.
Thanks
Related
Hi there,
I have this strange problem with my HTC Elf. The problem existed with the original ROM (5.0) and after my upgrade to 6.5 as well.
It started once a Month, but now it's twice a day.
If i receive or make a call, receive or send a SMS the device just shuts down immediately. (like a hard reset).
The device then automatically starts up, i get the "Smart mobility" screen and then it starts over again. The boot cycle runs endless, until i remove the battery and start again. Sometimes i need to remove/replace the battery 3 or 4 times to get it booting up again. (Doing this booting drains a lot of battery power)
If i remove the SIM Card, everything works fine for hours and booting isn't a problem at all. So I believe accessing the SIM Card somehow craps the device out. The boot-cycle seems to happen in the last stage of booting, when the device first tries to access the SIM card. (That's something i have to suspect, cause there is no way to log the booting).
I don't believe that it's connected to the ROM Upgrade to 6.5 i did, as the problem happened in 5.0 as well... (btw. everything is much faster and more light-weight since the 6.5 upgrade. It's just great.)
Here are my questions:
- Is there something, I could log the boot process, to see what's the last action when it starts over again?
- Is there something like an event log in windows, where I see the last action or even failure / exception, before the device restarts while doing a call / writing an SMS?
- Did anyone see this happen before?
Thanks for any input!
Hi
Have you tried to change the Sim card or use another one just in case the sim is the problem?
Hi Tito,
I plan to swap SIM's next weekend. But i don't get how a SIM can crash the whole thing. I would understand getting errors like "Can't read SIM" but auto-resetting the whole device?
Anyhow, I'll post an update after trying another SIM. The whole thing is, that it's not reproducible by a specific action one could take. So if the device keeps up even for 2 days with a spare SIM - that doesn't mean the SIM's chip is the problem. Just an indication...
Thanks,
mc
Hi
Please do post the result
I had the same problem (endless reboot) on my Elf. I solved it by replacing the battery.
Hi,
well it's like always. If you need the problem, you cannot reproduce it.
The device wasn't crashing even once on the weekend.. Either with my own SIM or with another one.
The battery thing is interesting. As soon, as the problems start reoccurring, I've got now a spare SIM card to test. If this fails, I'm able to test with another battery in march.
I'll post any results.
thanks,
mc
I have the same problem...and also struggles to find a signal. Did you solve the problem yet?
same problem
I have the same problem and !!!!!!!!!!!!!!!!!
well, the thing is i upgraded to the HD2 and didn't use my elf pretty much lately.
I changed my provider and got a new SIM but that didn't solve the issue. So I can exclude the fault being in the ROM or the SIM card.
When the elf was crashing I couldn't start it up. It was booting, and as soon as it tried to register itself in the Network, it crashed again. However, when connecting it to a power source (charger or pc) and booting it up, it went fine through and was able to register in the network.
That brings me to the idea, the even if the battery is full at 100% it might have a flaw and doesn't bring enough energy, when the device is scanning for the available networks.
So next time, I'm in china, I'll get a new battery pack for my elf - however, it's no more that important as my HD2 is running pretty fine.
Hope it's something which can help you.
cheers,
mc
I've got two main problems with my galaxy s.
1) Today at around 1pm I had to force close something (I don't even remember what it was. I had just woken up the phone and went to check my mail, so I assume Launcher pro or something). It kept prompting me to force close, so I just took out the battery and reboot it. The phone can no longer get passed the initial screen (before the S). I've tried to reset to factory defaults, and it still doesn't work. I assume I can re-flash (not home yet) - but I'm wondering what would cause this type of behavior. FYI - I've been running 2.2 JPH with Rombie's mod)
2) I get really bad reception. I constantly will have my phone go from no service to 3-4 bars while sitting in the same spot. I also have a problem in busy areas where I'll lose my connection completely (whereas other people with different phones seem to have no problem right beside me). Is there anything that could be causing these issues?
Side note: When I originally upgraded to 2.2 JPH I had efs issues for a while, and it took me a while to get it up and running. It's working now (phone and data) - I'm just worried there's some residual effects of a mildly corrupted efs or something.
Update...
Things have gotten worse and I really need some suggestions.
I've tried flashing about 5 different firmwares and I can't get the thing going.
The closest I've come is with the stock jh2 firmware. It boots and it goes to a black screen after the S logo. I know this has been brought up but I have not had success with solutions I've found in other threads. I've tried it with pit512 513 and 803. I've tried it with repartition checked and unchecked.
When I try a 2.2 rom (such as the latest jpk) and upon resetting in the recovery mode, I receive an SDCARD failed to mount error (although one time I also received a failed to load DBDATA error). It also won't let me format the sdcard in this screen as obviously it can't mount it.
The closest I've come to getting the sdcard working is on the jh2 firmware i can "load update.zip" from my firmware, and it seems to actually load - unfortunately that update.zip is completely useless (as it's just an unlocker update i believe) - and I can't change the update.zip as I can't access the sdcard.
Please help if you can!
I had the same problem. My phone was working fine and then it just turned off and froze. I resetted it a few times and it would go to the S logo and then the screen would go blank and the buttons would light up. Resetting it a few more times made it work once but then when i started it again the phone would go back to the same problem.
I tried a ton of rom on it and some worked (but my internal sd card wouldn't mount). The problem got progressively worse by it's self and my phone wouldn't even start now. I recently send it back to Bell to get it repaired and hopefully they don't ping me saying it was my fault for ****ing around, which I doubt they will find out at this point since the damn thing doesn't even turn on.
I researched this a fair bit (2 full nights) and found out that it had something to do with me flashing Jp3 and that set my internal sd card as read only somehow. It's a bug and if you google it a lot of people have had this problem but none had a working solution and everyone of them had to send it back for repair.
Edit: I am also Canadian with a bell phone.
If I end up sending it back to bell, will flashing back to something like JH2 help cover my tracks?
Any idea how long it takes? I can't really go without a phone for more than a couple days =/
fuffalo said:
If I end up sending it back to bell, will flashing back to something like JH2 help cover my tracks?
Any idea how long it takes? I can't really go without a phone for more than a couple days =/
Click to expand...
Click to collapse
Honestly, it is a very frustrating process. They quote you a 2 - 6 week window and do not give you any hard time table and to top that off they don't have any loaner phones that are smart phones. The loaners cost $25 and $250 down.
I had to go out and find one from a friend and even then they wouldn't let me use a CDMA phone since i had a HSPA+ data plan and it some how ****s with their system. The only way you can use a phone on their network is using a HSPA+ phone if you need data. Luckily a friend had a HTC magic that was unlocked so I am using that now.
You can try to load up the default rom that ships with it and then send it in for repair.
Is the default rom JH2?
I believe it is this one I9000UGJH2
Alright so I can adb in to my phone when it's in recovery mode.
Does this help at all? Can i try anything from here?
first of all: my reboot problem is kind of unique so the search didn't help.
problem: like the title of this thread says, my hd2 rebbots itself. i could not find out a specific pattern, it does this things (to me) completely at random: sometimes it goes 5-7 hours straight without rebooting but then three times in only one hour.
it first happend when i got a new sim card and therefore a new provider. i thought the sim card didn't work properly so i asked for a new one, but the problem still existed.
i changed ROMs and Radios, formatted the sd card, changed backed to stock rom, but without success.
BUT here are things that might help you help me:
1.) i DID NOT have the issue with the WP7 build (with android i DO have the issue)
2.) it only reboots itself when in standby, i have never seen it happening while i was using it
3.) the new provider uses the network from another provider, so it is always in roaming.
i really do appreciate all the help i can get!
please excuse me for my english
Same here
I've got the same problem, it does happen aswel in wp7 rom but it takes more time for some reason, I think it's a hardware problem, I seem to recall flasing back to the standard rom so the telehpone would be like out of the box but i got a restart after 40 minutes .. aswell in standby.
Sir Schwanzelot said:
first of all: my reboot problem is kind of unique so the search didn't help.
problem: like the title of this thread says, my hd2 rebbots itself. i could not find out a specific pattern, it does this things (to me) completely at random: sometimes it goes 5-7 hours straight without rebooting but then three times in only one hour.
it first happend when i got a new sim card and therefore a new provider. i thought the sim card didn't work properly so i asked for a new one, but the problem still existed.
i changed ROMs and Radios, formatted the sd card, changed backed to stock rom, but without success.
BUT here are things that might help you help me:
1.) i DID NOT have the issue with the WP7 build (with android i DO have the issue)
2.) it only reboots itself when in standby, i have never seen it happening while i was using it
3.) the new provider uses the network from another provider, so it is always in roaming.
i really do appreciate all the help i can get!
please excuse me for my english
Click to expand...
Click to collapse
Greetings all. I'm a recent Focus user having a frustrating issue. When my phone has been on for 12 or more hours (meaning it has been 12+ hours since I booted it from an "off" state) I stop receiving text messages. When I restart my phone they all appear at once, as if they were stuck somehow. I then can receive texts normally until it happens again, always within 24 hrs. This has happened on the locked stock rom as well as the unlocked custom rom I am currently using. The only thing I can think of is that somehow the SD card (SanDisk 8gb class 2) is not completely compatible (I used my own card. I purchased the phone used so it didn't come with the factory card) Any advice on the proper course of acting leading to resolution would be appreciated. Thanks for reading
Try running the diagnosis app, entering *#32489#, Back, Back, 7 (Network Control), 1 (GCF), 3 (Setting Cancellation), End. That operation has been effective in clearing up my own SMS oddities such as delayed messages. Thanks goes to somebody on this forum for it originally.
Thanks! I gave it a try. Unfortunately it will take a day or so to test. I appreciate the help and will post the results.
It has been several days now without a restart and the problem has not ocurred again. Thank you for the tip!
Hi
With help from this forum I upgraded my Chinese Axon 7 to Build A2017V3.0.0B17 back in the autumn. It's now on Build A2017V3.0.0B23. I think it did that update a month or so back.
Anyway for some weeks, which I don't think coincided with the update (but it may have done), I have apps freezing on startup. E.g. Uber splash screen comes up and sometimes it goes to the next (white) screen before it freezes, and sometimes not. In Chrome I have a number of tabs, sometimes it starts properly and opens them all and sometimes it freezes before it's opened them. (With Chrome , if I keep closing it down and restarting eventually it works).There are lots of apps like this, although there are also lots which are still working OK.
So last night I took the plunge and set it back to factory. Iv'e been reluctant to do this because I am on such a steep learning curve on rebuilding phones and I wasn't sure what it might do.
The outcome was that it reset just fine, still on B23, and so I started putting back my apps. Only to find I still have the issue.
So... should I put it back to B17 and see what happens, or can anyone advise anything else to look at before I do?
Thanks
Oh well, over the weekend I took the plunge. I used EDL method to put on A2017G onto my A2017 phone. It took a couple of attempts, and I think I have one or two outstanding gremlins, but by and large the phone seems at least as good as before. I need to check out making and receiving calls - tested it once with my partner and all was fine but a later call seemed to conncct but nothing heard by me. Using it as a phone is a small part if it's existence but it's important.
I have got back some of the Google stuff which didn't work after the last update, like Timeline.
However I don't seem able to get back into FTM mode or to get my PC to recognise the phone any more (except as a disk device) so I guess next time round I'll have to splash out on a new phone...