I'm currently facing the strangest problem with my himalaya ever since i bought it 1.5 ago.
I upgraded 2 weeks ago to the WM2005 edition. everything was smooth and fine until today. i decided to do a normal reset so that i can "Refresh" the memory. after the reset the startup screen showed up as usual. then the screen went white (or black after the backlight turned off).
nothing on the screen what so ever.
I tried to do a hard reset (to reformat the rom) but my attempt failed. actually the files on the rom were NOT erased.
I thought to myself , reinstalling the WM2005 rom from my pc would do the trick. i connected the device after putting it in (USB) mode (pressed power+ Reset+ DPAD).
twenty minutes passed as usual and it showed the congratulations screen. i did a hard reset again and again the same problem (it didnt even erase the rom).
I then downloaded version 1.75 rom from buzzdev, did the procedure again, it did install and format this time correctly , but still i'm getting the blank screen after the startup screen.
Note: the phone is fully functional in the background, i recieved calls and sms's without being able to see anything. it seems like a screen problem, but the initial startup screen is showing so that doesnt make any sense..
any help ppl is really really appreciated !!!
HardReset with WM5
This is the way to HardReset
Click Here
thx, but i have done that already
and guess what!!!
It just worked!!
god knows these devices have minds of their own
thx alot
it just stopped working again
back to square one
Please help me, I played around with BBs yesterday and lost radio, so installed a stock FW with FlashTool, and got radio back again, but on some 4x BB.. Wanted the new 58 BB, and found out that a .. ..0.16 FW would give me that, so installed the polish one (found no other), and after that no response when touching the screen!
xRecovery is of course gone after "stocking" (also rooting?), but I have tried a number of FWs for FlashTool, and even FW directly from S-E using Update Service, but still my phone is next to bricked.. I am n00b and could very well have done something wrong unknowingly, and/or overlooked something, but what might that be, and what are my options?
Sounds like corrupted FW. Not a big deal cause without a cracked Bootloader, you realy can't screw the phone up.
Turn phone completely off.
Pop Battery - SIM card - Micro-SD card out.
Let it sit for a few minutes.
While your letting it sit, take your Micro SD card and Format it using your PC.
"not saying this is your issue but I have had the phone lock up and appear to be unresponsive due to a corrupt file on the SD Card and it fails to mount and gets stuck." If you have any files you want to save, copy them to your PC Hard Drive.
Reinsert your SD Card - Sim Card.
Plug your USB cord into your phone " LEAVE THE BATTERY OUT "
Start up SEUS " Sony Erricson Update Service ".
While holding the back button, reinsert the battery.
Follow the instructions and restore the phone to factory settings.
I hope this works for you as this should elliminate any problems that could have or would be occuring prior. If it doesn't, shoot me a mail and I will get with you on messenger for trouble shooting.
_-_- Press Thanks if its useful-_-_
Nope, didn't do it, touched the thanks-bottom anyway, because on my PC I can...
PM'ed xKrisx, but everybody are welcome with suggestions as I'm completely lost without my phone!
Edit while waiting, hoping:
Followed instructions above several times now, except
xKrisx said:
.. .. .. and restore the phone to factory settings.
Click to expand...
Click to collapse
no such option, wouldn't that be S-E-Android 1.6 ? In fact I see no other options in SEUS than accepting (or not) uneditable choices towards an update -and done-, so I suppose that's what was meant(?)!
Have tried a number of slight variations including SEUS update without sim and SD at all (was actually allowed that), but most noticeable difference was that first boot pre-choose English instead of Danish (my language), and still no response from touch screen, so can't select anything at all!
My phone shows evidence of "moderate physical pressure" (bought second hand with one corner missing), so I can't totally reject the possibility of a sudden HW digitizer breakdown though I think that would more likely have occurred while phone in use than while sitting on my mouse-pad.. No matter what, I would really like to exclude any SW related errors before moving to torx-driver surgery! Plz help guys!
Hi seek4
Did you ever find a solution for your touchscreen?
My Samsung Galaxy S Vibrant keeps restarting over and over. Its getting irritating that my phone can just be sitting then all of a sudden its rebooting up. Im running firmware 2.3.4 gb and Simply Honey 5.1...Can someone please help me with this problem..Thanks
Need a little more info. Are you Overclocking, Underclocking, and/or Undervolting?
We may have the same problems, sir, though we may have a very slight difference on the device we're using. I haven't tried using Galaxy S so I can't really vouch on this to work on your device.
Recently, I have experienced that too on my Galaxy S II. Here's what I did:
1) I cleared my browser's cache from the application...
2) I formatted my SD card using the SD Formatter from this link...
3) I installed WatchDog just in case something goes wrong.
4) I move all my apps to my phone. No more apps on my SD.
It was quite hard to narrow down which one was the culprit because I did all the abovementioned procedures at the same time without testing which of them works or not. But ever since I applied those procedures, I never got any random reboot up to this point yet.
User Theonew also mentioned that it might be #4 that caused it. If it won't take much of your time, you can give it a try. But I suggest you apply #4 before trying the rest.
Another thread also mentioned that Dolphin HD browser was the culprit on their device. I cannot comment on this because I was having random reboots when, in fact, I don't have Dolphin HD on my device.
Galaxy SL keeps Restarting..
Hi Guys..
I too had the same problem. My GT-I9003 suddenly started restarting and it keeps restarting untill battery drains. If I remove the battery or manually start it back again.. It will ask the setup and all my contacts, messages are lost. I tried several troubleshoots and of no use.. I gave it to samsung authorised service for three times and finally got the mother board replaced. But again the problem started on the same day. I faced this issue for around 2 weeks and thought of
throwing my phone away.. but finally one day I found the cause and solution for this issue..
The main reason for this issue is, our phone got bricked..(99% of chance for Soft Brick and 1% of chance for hard brick).
I tried the following troubleshoot.. (This is the resolution for Soft Brick Issue)
1. Turnoff the phone..
2. Press the Volume up key on the left side of the phone and Home key simultaneously..
3. Holding those two keys.. Press the power on key..
4. Now your phone enters into recovery mode
5. There select the option to Factory reset and do the factory reset. I remember it as 3rd option..
6. After the factory reset, clear the partition cache which will be the 4th option in recovery mode..
7. After doing both these, there will be an option to reboot the phone.. select and let the phone restart..
If your phone is Soft bricked.. the issue will be resolved.. as like mine. Still if the problem exists, then the phone might got hard bricked(u r d unlucky 1%) and try replacing the internal sd card..
Hello guys,
At first, sorry for the long text but, that's the odyssey that leads to my problem. If you don't want to read everything, jump to the summary.
It all started when my S3 got wet inside my backpack while it was raining. I know that the first thing we need to do is to pull out the battery when you realize it is getting wet and let it dry for days before turn on. However, I was drunk so I tried the opposite turning it on at the end of the day and it didn't work. Then I pulled out the battery and let it dry for weeks. I've also opened the device and disassembled it. I could see some parts with some kind of white dust. So, I cleaned with a toothbrush and rubbing alcohol. After doing that, I tried to turn on the device without success. One or two days later that battery got stuffed and then I sent it to repair.
There, I pointed that it could be a problem with the main board. The guy performed a fast check with voltmeter and said he could be repaired. He took the device and returned with the S3 turned on in less than 15 minutes. Then, he asked if he could reset the device and where I bought it because it didn't have the stock rom (I changed it to Neatrom). Since it was "working" I said I would take it and do the rest of the job restoring the rom.
When I got home, I charged the phone for ~8 hours following the technician instructions since it was a new battery. The strange thing is that the icon for battery was not the green one, but the white one with the round arrow the whole time. Ok, then I did a clean and restore through CMW menu keeping the neatroom. It started autorebooting. Also tried CM12 but got bootloop. The next day, the battery got stuffed so I pulled it out and waited to whole week and sent to repair.
There, he gave me another battery (which now seems to be original). The battery worked and I did a reset through CWM recovery. At first minutes it was ok then it started rebooting. I thought it could be something with the room since It was not rebooting in recovery menu. Anyway, I also took my notebook there in order to restore the stock rom and, in case of errors, I could give the phone to the technician in the same day. The problem is that the process took forever when it got to the point of booting up the phone after restarting it and then I ran out of battery and had to turn it off.
When I got home, I applied the stock rom again and it booted ok but with the common efs/csc problems (Can't recognize sim card, IMEI/Baseband unknown....). Also, menu and back button seems to be not working. No leds or function. It's probable hardware but I check it later.
Well, I have a efs backup I've created with kTools (efs.img 20mb + efs.tar.gz 0kb) which I tried to recover but it didn't changed nothing. I also have another efs.tar.gz file alone with 1kb which I'm not sure if it's a backup but I think I generated that with Backup_EFS.bat. Tried Restore_EFS.bat but got stuck in * daemon not running. starting it now on port 5037 * * daemon started successfully *...
I've already tried odin through PDA and CSC. My country is Brazil and I already tried the open region Stock Rom (PDA:I9300UBUGNK1 and CSC: I9300ZTOUGNK2) and rom from an specific provider.
Summary
- I9300 got wet (rain)
- ~3 weeks drying disassembled + mainboard clean with toothbrush and rubbing alcohol
- Battery stuffed 2 days after assembly and test without success.
- Sent to repair. Something was done there and it revived.
- Phone autorebooting then battery stuffed again.
- Sent to repair. Changed battery
- Tried to apply stock rom (odin). First boot took forever and had to turn the device off.
- Second attempt worked but got IMEI/Baseband unknown, sim card recognition problem
- Tried ODIN through PDA and CSC
At this point I'm downloading A.S_id's rescue firmware and try it's troubleshooting. Later I may try to restore IMEI with -efs rebuild using android SDK....
So many things happened that I'm not even sure what to ask but, if you have a luminous idea on something I've never done, Id kindly ask to let me know.
Did I do something wrong when trying to restore efs? BTW, I also have a full nandroid backup generated by CWM philz touch recovery but it seems it doesn't contain efs partition.
Also, I ask you guys if the IMEI,Simcard,baseband problem can be a hardware problem? I've even seen topics saying about "burning the baseband", is it possible?
I'm just trying to gather all information possible before going to the technical assistance again.
If you read everything, I appreciate your patience and I'd be grateful for any reply.
try to restore the efs.img with PhilZ recovery via custom restore... :good:
Welp,
I've gone & done it again. My 2nd z3v came from Amazon a few days ago, refurbished, like new. Got the 200GB card for it, went to Verizon & got the SIM, swapped it with my work phone (iPhone 4s) line.
(Now I have 2. But the 1st one was replaced for being in this same situation.)
Got home, swapped the phones back cause I really still wasn't sure I wanted to mess up this z3v with my job (landscaping = lots of dirt).
It had 4.4.4, and I let it update to the latest two part Lollipop to see what the hubbub was about (nothing).
Decided I wanted to make it basically a clone of my primary z3v, so I rooted from the update directly using GigaSPXs guide.
Successful rooted 509 achieved, but with one problem; it kept telling me I had no space left, even though the internal SD had 21 GB left. Peculiar.
Made a recovery file on my #1 z3v's SD. Copied everything from #1 SD to #2 SD, and attempted to "clone" #2 z3v by installing that latest zip copied from z3v #1, but Recovery kept saying "No File Found".
Checked all 5 recovery points I had on there, and each said the same thing. Checked other things on the SD card, and it showed them, but when I tried to open them, it said "No File Found".
Mounting problem? Made sure everything was mounted, etc. Still, same problem.
Tried wiping Dalvik 3 times, but also accidentally wiped System Cache.
Now it sticks at the SONY Xperia logo. I can get to the Sony Recovery options, but Factory Reset doesn't do anything.
Was it System Cache wipe that killed it, and can anything be done?
This time, I took some notes as I went. I was confident, but I've done this before (bricked), so I decided to list what I did as I went along. I highly recommend everyone take notes for when they screw up. LOL!
AddictedToGlass said:
Welp,
I've gone & done it again. My 2nd z3v came from Amazon a few days ago, refurbished, like new. Got the 200GB card for it, went to Verizon & got the SIM, swapped it with my work phone (iPhone 4s) line.
(Now I have 2. But the 1st one was replaced for being in this same situation.)
Got home, swapped the phones back cause I really still wasn't sure I wanted to mess up this z3v with my job (landscaping = lots of dirt).
It had 4.4.4, and I let it update to the latest two part Lollipop to see what the hubbub was about (nothing).
Decided I wanted to make it basically a clone of my primary z3v, so I rooted from the update directly using GigaSPXs guide.
Successful rooted 509 achieved, but with one problem; it kept telling me I had no space left, even though the internal SD had 21 GB left. Peculiar.
Made a recovery file on my #1 z3v's SD. Copied everything from #1 SD to #2 SD, and attempted to "clone" #2 z3v by installing that latest zip copied from z3v #1, but Recovery kept saying "No File Found".
Checked all 5 recovery points I had on there, and each said the same thing. Checked other things on the SD card, and it showed them, but when I tried to open them, it said "No File Found".
Mounting problem? Made sure everything was mounted, etc. Still, same problem.
Tried wiping Dalvik 3 times, but also accidentally wiped System Cache.
Now it sticks at the SONY Xperia logo. I can get to the Sony Recovery options, but Factory Reset doesn't do anything.
Was it System Cache wipe that killed it, and can anything be done?
This time, I took some notes as I went. I was confident, but I've done this before (bricked), so I decided to list what I did as I went along. I highly recommend everyone take notes for when they screw up. LOL!
Click to expand...
Click to collapse
Use Flashtool to flash it back to 4.4.4. After that, don't try to do your attempt again. They're two separate devices and they are both uniquely different internally.
OK, how do I use flashtool? The PC doesn't recognize the phone as anything hooked up to it. Flashtool doesn't recognize it's there.
AddictedToGlass said:
OK, how do I use flashtool? The PC doesn't recognize the phone as anything hooked up to it. Flashtool doesn't recognize it's there.
Click to expand...
Click to collapse
IIRC, hold down the down (or up) button and hook the phone to the computer. I think it should trigger recognition from there.
GigaSPX said:
IIRC, hold down the down (or up) button and hook the phone to the computer. I think it should trigger recognition from there.
Click to expand...
Click to collapse
If that doesn't work and you have connected your phone to your computer before try removing all related Sony drivers from the computer. If you are OK with registry edits you could look for any instances of your phone there too.
Komet1 said:
If that doesn't work and you have connected your phone to your computer before try removing all related Sony drivers from the computer. If you are OK with registry edits you could look for any instances of your phone there too.
Click to expand...
Click to collapse
Don't I need the drivers installed?
Yes,, reinstall them preferably from outside your computer. You are wanting the drivers on your computer to be overwritten by fresh drivers, even if they have the same version numbers. You want the computer to "think" this is the first time the phone has ever been connected to it.
Where do I get th drivers for re-installation?
AddictedToGlass said:
Where do I get th drivers for re-installation?
Click to expand...
Click to collapse
Try this. If you do take this route don't be discouraged if it doesn't work the first time. I have had something similar happen and on occasion it has taken a few tries. Windows doesn't like to let go of drivers that are already installed.
Xperia Z3 drivers
"Phone driver for Xperia Z3 (D6603, D6616, D6653, D6643, SOL26, D6708, SO-01G, and 401SO) (Microsoft Windows™ XP 32bit/64bit and later). Use drivers for debugging, or when erased from phone."
DLed the replacement drivers, but Flashtool isn't recognizing the z3v. I know I'm doing something wrong because it isn't recognizing my other (functioning) z3v, either.
So I Googled driver installation on Windows 8.1 because I remembered that it won't allow unsigned drivers without manual installation, and I needed a refresher course for all the steps. I am uncertain I successfully removed all of the previous ones, though. What I did find out, but did not know, was that putting 8.1 into that mode (where it'll install unsigned drivers) is a temporary situation. According to a poster on a blog (for whatever that's worth...), once the PC is restarted, it comes out of that "test mode", and unsigned drivers no longer work again. I usually keep the PC on, but it has restarted since I last messed with Flashtool.
Obviously I need to figure out where I'm going wrong on this to even begin work on the phone. (I miss XP.)
Details about the z3v behavior:
The screen is stuck on the SONY XPERIA logo.
Pressing the power button by itself has no effect, no matter how long I hold it.
Pressing the power button with the volume down will power it off, but it just powers back on by itself.
Pressing the power button and holding both the power button and the volume down while it cycles back on gets me into the Android Recovery menu.
From Recovery;
Selecting "Power Down" USUALLY powers it down, but sometimes it immediately restarts.
Selecting "Factory Reset" cycles it through the logo and into an attempt (Droid animation with blue bar rolling) for about 5-6 seconds, and then it restarts into the SONY XPERIA logo again.
Selecting "Safe Mode" simply restarts it the same way.
Selecting "Continue Power Up" obviously does the same.
All that is while not tethered to the PC. NO color LED comes on, except for an occasional orange while it's hooked to the PC.
Got a couple of suggestions about the PC connection:
Try a different USB cable.
Have you looked in Device Manager and removed any reference to the Sony there as well?
Here is a blog post about an Xperia S that wouldn't connect, the steps should be the same:
Connect the phone via USB and go to the Device manager on the computer. Check if you can locate the phone or any Unknown/New device that could be the phone or if you perhaps see the phone as a device. Right click it and select to uninstall.
Still in Device manager open the list for USB controllers (Universal Serial Bus Controllers) and right click each one of these controllers and select to uninstall.
When all of this is done reboot your computer and before connecting your phone again repeat step 2.
You should of course not have to do this every time you connect your phone to your computer but hopefully this could remove any error causing your phone not to connect properly.
I'M BACK!!!
And here's a lesson from one noob to all others; Never overlook the simplest things.
Komet1, your suggestion of trying a different cable struck me as desperate, but when I looked at what I had been using, I realized it was the cheap cable Amazon sent with the phone (It didn't come with a Sony charger and cable, just a crappy generic set).
I swapped cables and viola!, I now have 4.4.4 back.
I'll not be making the stupid mistake of swapping restores from one phone to another again.
Thanks all!
Important lessons for beginners...
Take notes. I'm glad I did this time because last time I bricked I couldn't remember what I had done to brick it, or what I had tried to unbrick it. It helps when you can provide detailed info, otherwise it becomes too frustrating for those who can help. It can also help keep you from panicking and going in circles.
AddictedToGlass said:
I'M BACK!!!
And here's a lesson from one noob to all others; Never overlook the simplest things...
Thanks all!
Important lessons for beginners...
Take notes. I'm glad I did this time because last time I bricked I couldn't remember what I had done to brick it, or what I had tried to unbrick it. It helps when you can provide detailed info, otherwise it becomes too frustrating for those who can help. It can also help keep you from panicking and going in circles.
Click to expand...
Click to collapse
Awesome! Been there, done that with the bricking. It's a wonderful feeling when you watch the phone respond and realize you just solved the problem.
Sure is!
DOH!!!!