Hi,
I have a iphone 3gs which i purchased from eBay long back and.. Long story short, now I have multiple problems :
1> The phone doesnt show/have the IMEI # and neither does any other details like firmware etc.
2> The phone randomly gets restarted continuously almost every 1min.
I tried replacing the battery thinking the issue with restart would be with the battery but still it doesnt stop. Due to this issue I am unable to install the IOS software as it gets restart frequently and the installation stops in the middle. I am now thinking it might be problem with the 30pin charger cable (viz., not genuine) that i am using but not sure. Can anyone help me on how to fix this issue of restart and to get back the IMEI# on the phone again. Any help or suggestion would be really great.
Related
Hi Guys,
I've been an owner of a Three-branded HTC Touch Pro in Australia for over a year now, with no major issues with it except for the multitude of WM bugs and lagginess I've grown to accept.
A year ago I loaded SPB Mobile Shell and I have a couple of other apps but not many that I use frequently. The phone is mainly used for calls, messaging, syncing with my Outlook calendar and contacts, and browsing the internet
A day ago the phone began behaving very strangely, with no rational explanation as to the trigger or cause.
The phone has begun randomly and frequently soft resetting itself. This can occur when I'm in the middle of writing a text message, on a call, or browsing the internet (or whilst doing anything else, really). The phone will go blank, the vibrator will vibrate once, then the 'Touch Pro' logo welcome logo will be displayed as it reboots.
The phone will then either:
(A) wait for me to enter my PIN
or
(B) go straight past the PIN screen through to the home screen
If I do not enter my PIN after this (either at the PIN screen or by invoking the PIN screen by selecting the Phone app), the soft-resetting issue doesn't occur. However, this leaves me with a useless brick, unconnected to any networks.
So I have to enter my PIN and then wait for the device to mysteriously and randomly soft reset itself at some point soon. Extremely frustrating.
Interestingly, I've found that the soft resetting issue doesn't occur when the device is plugged into the mains power or to a computer.
Today I upgraded the ROM to the latest available on the 3 website, and then installed the latest version of Mobile Shell 3.5. However the issue still persists...
I've now managed to disable the PIN request so that when the soft resetting occurs, the phone is automatically reconnected to the network but I'm not sure what sort of never ending loop of resetting this will create!!
Any clues???
So as a follow-up to this issue, my phone appears to have mysteriously fixed itself.
It is no longer resetting itself... or at least I haven't witnessed it reset itself.
Could anyone provide a potential analysis of what's going on??
randommonth said:
So as a follow-up to this issue, my phone appears to have mysteriously fixed itself.
It is no longer resetting itself... or at least I haven't witnessed it reset itself.
Could anyone provide a potential analysis of what's going on??
Click to expand...
Click to collapse
Things like this happen for a few reasons, A bad flash, Corrupt blocks in the memory, and even if the device gets too hot, if it happens again i suggest you use a tty program like mtty of putty to format your device before flashing a new rom
I was wondering if I've encountered a common failure mode with my Verizon Galaxy S3 and if there are any possible solutions.
A week before it bricked, the phone was acting rather odd, rebooting itself spontaneously and at random; I didn't really think much of it until the following week. Applications on the phone had been running VERY slow and would often crash or hang; in addition, the phone was rebooting itself several times an hour at this point.
The last reboot hung for a while at the "Samsung Galaxy S3" screen before going to the home screen. At this point I realize there may be something serious going on, so I attempt to SSH into it and retrieve important information off it. Unfortunately, it proved to be too late; login attempts failed with "Argument list too long". A few minutes after my ill-fated attempt to save data, the phone crashed in the app launcher and initiated a reboot again; only this time, the Samsung logo never came up. Since then, I have been unable to power it on, enter recovery, or otherwise get any life out of it.
It's long out of warranty so I'm basically wondering what my options are to revive it and possibly get important info off it. Reinserting the battery does not work and neither does plugging it in. All options to enter recovery or any other sort of mode fails; it essentially acts like there's no battery inside and does nothing. Is this a common failure state for S3 units and is there a known solution? Has anyone ever used JTAG to retrieve information off the storage inside?
WildZontar said:
I was wondering if I've encountered a common failure mode with my Verizon Galaxy S3 and if there are any possible solutions.
A week before it bricked, the phone was acting rather odd, rebooting itself spontaneously and at random; I didn't really think much of it until the following week. Applications on the phone had been running VERY slow and would often crash or hang; in addition, the phone was rebooting itself several times an hour at this point.
The last reboot hung for a while at the "Samsung Galaxy S3" screen before going to the home screen. At this point I realize there may be something serious going on, so I attempt to SSH into it and retrieve important information off it. Unfortunately, it proved to be too late; login attempts failed with "Argument list too long". A few minutes after my ill-fated attempt to save data, the phone crashed in the app launcher and initiated a reboot again; only this time, the Samsung logo never came up. Since then, I have been unable to power it on, enter recovery, or otherwise get any life out of it.
It's long out of warranty so I'm basically wondering what my options are to revive it and possibly get important info off it. Reinserting the battery does not work and neither does plugging it in. All options to enter recovery or any other sort of mode fails; it essentially acts like there's no battery inside and does nothing. Is this a common failure state for S3 units and is there a known solution? Has anyone ever used JTAG to retrieve information off the storage inside?
Click to expand...
Click to collapse
Plug it into your computer, or a wall outlet with the battery out. See if it mounts as a strange drive or the led light flashes for a second.
Oh wow. Yes it does have the red light when I plug it into the wall outlet without battery. Haven't tried the PC as I'm leaving for work and my USB wire is in the car but I'll assume that will work when I try it.
WildZontar said:
Oh wow. Yes it does have the red light when I plug it into the wall outlet without battery. Haven't tried the PC as I'm leaving for work and my USB wire is in the car but I'll assume that will work when I try it.
Click to expand...
Click to collapse
At least it isn't completely fried, this method should work:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure it has no other sign of life first.
If you were on 4.1 then make sure you don't use a 4.3 file and lock your phone. Might have to do some digging around to find them, but they are around here somewhere.
I've got some very strange issues happening since the latest T-Mobile update to baseband G930TUVU2APC8.
The phone is a T-Mobile Galaxy S7 with a Sandisk 200GB micro SD card installed
Whenever I'm on a phone call through a my Jawbone Era (and charging; I haven't tried it unplugged) the phone will behave as if it did a reboot, without actually rebooting, every few minutes. The phone will stop responding for about 20 seconds, then show just the wallpaper for about 5 seconds, then go back to the lock screen. At this lock screen it requires me to enter my password instead of using fingerprint as if it had just powered up. The phone call does not drop through all of this.
The next issue is that some pictures taken from the quick launch are sometimes not saved. I'm not 100% sure that this only happens after the reboot issue above, but I think it does. I have secure startup disabled .
I tried a factory reset which did not fix the issue, contacted t-mobile and was sent a replacement device that still has the problem. None of this was happening prior to the latest update.
Has anyone else experienced these issues? Also, is it possible to downgrade the firmware version?
Thank you,
Matthew
techy101 said:
I've got some very strange issues happening since the latest T-Mobile update to baseband G930TUVU2APC8.
The phone is a T-Mobile Galaxy S7 with a Sandisk 200GB micro SD card installed
Whenever I'm on a phone call through a my Jawbone Era (and charging; I haven't tried it unplugged) the phone will behave as if it did a reboot, without actually rebooting, every few minutes. The phone will stop responding for about 20 seconds, then show just the wallpaper for about 5 seconds, then go back to the lock screen. At this lock screen it requires me to enter my password instead of using fingerprint as if it had just powered up. The phone call does not drop through all of this.
The next issue is that some pictures taken from the quick launch are sometimes not saved. I'm not 100% sure that this only happens after the reboot issue above, but I think it does. I have secure startup disabled .
I tried a factory reset which did not fix the issue, contacted t-mobile and was sent a replacement device that still has the problem. None of this was happening prior to the latest update.
Has anyone else experienced these issues? Also, is it possible to downgrade the firmware version?
Thank you,
Matthew
Click to expand...
Click to collapse
The problem started in PB8 firmware, PC8 firmware has constant wifi dropout issues, you might find even that at 3G connection performing better than fiber optic wifi internet.
Easiest is to update facebook to latest version and see how many "can not connect right now" errors.
Random reboots is normal never mind how many times your factory reset or do a full firmware PB8 flash.
T Mo is not the brightest tools in the shed, it takes 5 visits to their T Mo offices to get the accounts and products purchased + refunds for items payed in cash or freebies refunded etc etc etc.....
Hi,
so for some time now the phone has been crashing randomly (although mostly when sending/receiving messages, calling, using a browser or listening to music) and then rebooting every few days. After the reboot it was alright for a bit
after a while it crashed multiple times in a few minutes, and then today it just kept crashing and rebooting, going as far as not even making it past the booting screen. just crashed and tried rebooting again.
did a factory reset, don't think it helped, but it seems that as long as it's on the usb cable with the pc it boots just fine, and does not crash.
Any ideas?
Edit: nvm just crashed on cable... but it seems a lot more stable and boots every time at least
also no sd card is installed
Update: crashes pretty much every time I want to install or update an app, and then gets into an infinite boot process of crashing and rebooting
While a usb cable (just in the phone, not connected to anything else) doesn't effect it, a powerbank seems more then enough for it to boot consistently so I think the battery might be giving up.
Thoughts?
For anyone in the same boat as me (and because I don't like stumbling over unfinished threads when looking into a problem myself):
Since I got no response I went ahead and got a new battery for 12€, had that now for a week and tried everything to get the damn thing to crash. It looks like the issue has been resolved as no crashes occured whatsoever, so if anyone of you guys has a crashing problem that seems to get worse over time and better when plugged in, you might have a faulty battery on your hands.
Which incidentally is one of, if not the cheapest problems you can have (as long as you have a phone with a removable battery ofc)
Also, is it possible to mark a thread as resolved?
Hi,
My mobile which was working fine till last night. Today morning without no reason its not switching on.
Make and model : Lenovo A7700 (2016)
OS : Android 6
There is no issue with battery or display or any part, it's was just on the table whole day idle. No physical damages.
All of sudden it's not switching on. When connected to charge even the logo needs to come if battery Is drained but its acting like a brick. If the display is the problem then atleast while connecting to charge the vibration needs to come. So there is no problem with display or battery.
Tried all the possible ways to turn on, nothing helped. When connected to PC it says last device you tried to connect was malfunctioned.
What happened actually all of sudden in one night.
I have done nothing recently with my phone nothing absolutely. It was just on the table. Last night I charged my phone and after Charing completed unplugged and kept as it was.
Please anyone help me so many documents are there in the internal storage which atleast I need to transfer to another phone.
Please kindly anyone help me with this ASAP.
Thank you in advance.
P.S : My mobile is not rooted or side loaded with anything. It's just as it is from the start. As mentioned earlier nothing absolutely nothing I done with mobile. My mobile had scheduled switch on and off feature so it will switch off on night 1o clock and turns on morning 6 o clock that was enabled many years ago and till yesterday no problem. But it today it switched off at 1 o clock AM with full charge and when I tried to turn on manually it's is not working.
Please Help me anyone to atleast recover data from internal storage.