My S620 is stuck at the startup screen showing just the window mobile logo and won't go any further. Anyone know how I can fix this?
hussnainahmed said:
My S620 is stuck at the startup screen showing just the window mobile logo and won't go any further. Anyone know how I can fix this?
Click to expand...
Click to collapse
I have reset it 3 to 4 times using two soft keys on button and the green button and waited for half an hour each time but the problem still exits
also i have updated the rom but every time it resets, htc s620 stuck on the windows mobile logo....................................................
please help me.....
Have you considered to re-flash your device?. This has been addressed so many times and many threads are open to discuss this issue. Please, post in one of these opened threads this will avoid cluttering the forum from same topic. Thanks for understanding.
On that note, this thread will be closed.
Yesterday, when I tried to use my note 2 in the middle of the day, I found the phone stuck at the Samsung galaxy logo. I took the battery out, then put it back. This time I won't even able to see the note 2 logo when trying to turn on the phone. All I have seen is a relative grey screen with white horizontal stripes parallel to each other and some dots in different colors randomly scattered on the screen. Tried to hold VOLUME + Home + Power, I was able to enter the warning screen and see the warning clearly. So I don't think it is something wrong with the screen. Installed odin on my PC, but it seems the phone is not detected by odin.
Questions:
1. Have I lost everything on my phone?
2. What can I do to fix the problem?
3. If I lost all the data and apps, how do I get all the apps back after I can restore/reinstall the android?
Thanks for any help in advance. And suggestions, helpful links are appreciated.
stanzauid said:
Yesterday, when I tried to use my note 2 in the middle of the day, I found the phone stuck at the Samsung galaxy logo. I took the battery out, then put it back. This time I won't even able to see the note 2 logo when trying to turn on the phone. All I have seen is a relative grey screen with white horizontal stripes parallel to each other and some dots in different colors randomly scattered on the screen. Tried to hold VOLUME + Home + Power, I was able to enter the warning screen and see the warning clearly. So I don't think it is something wrong with the screen. Installed odin on my PC, but it seems the phone is not detected by odin.
Questions:
1. Have I lost everything on my phone?
2. What can I do to fix the problem?
3. If I lost all the data and apps, how do I get all the apps back after I can restore/reinstall the android?
Thanks for any help in advance. And suggestions, helpful links are appreciated.
Click to expand...
Click to collapse
Is your phone Rooted?
Have you ever been able to see the phone with Odin?
What happens when you try to enter recovery?
Yes....
We need information...
Are you able to see the device storage while connected to PC ??
If yes....then your data can be saved...
Please tell us what rom....kernel....and other info....g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
me too
Hi, I am in the same boat here. Rooted SGH-i317 running Jedi x2 on T-Mobile. It froze one day while searching in chrome browser. I pulled the battery, and now it only boots to the same white screen, with squiggly horizontal lines, it never even gets to the Samsung logo. I can get into download mode, but not recovery. Kies won't recognize the device but Odin does. I have tried flashing the most current official at&t KitKat build and a couple others, but it fails with a "no pit file". When I try to repartition with the pit file it fails as well. Wtf!
Thanks for any suggestions.
guruvince said:
Hi, I am in the same boat here. Rooted SGH-i317 running Jedi x2 on T-Mobile. It froze one day while searching in chrome browser. I pulled the battery, and now it only boots to the same white screen, with squiggly horizontal lines, it never even gets to the Samsung logo. I can get into download mode, but not recovery. Kies won't recognize the device but Odin does. I have tried flashing the most current official at&t KitKat build and a couple others, but it fails with a "no pit file". When I try to repartition with the pit file it fails as well. Wtf!
Thanks for any suggestions.
Click to expand...
Click to collapse
Sounds like hardware failure.
creepyncrawly said:
Sounds like hardware failure.
Click to expand...
Click to collapse
That's too bad. I was going to give this to my kids to fool around with. I guess it's a mixed blessing since Tmob screwed up my insurance, and ended up giving me a $300 discount on a new Note4.
Hi guys
This is my first post here and to be honest I probably don't have the right words and phrases etc. to explain what my problem is but I really hope you guys can help.
I recently changed the screen on my Galaxy Note II (GT-N7100) and although it was working with the smashed screen when I changed over the screen all it does now is stay stuck on either the Samsung Note screen or an empty battery screen. I know it was sitting up for a week before the screen arrived so the battery probably went dead but I didn't think that would be such an issue, I left it charging all night but the empty battery logo is still there. I rechecked all the connections and all are seated properly.
I went online and people were saying to go to recovery and restore it to factory settings in recovery mode which I did but all that is coming up is red lines of code say things like E:/cache cannot be found / recovered etc. All the red lines of code start with E:/ so I take it that's the operating system.
I then tried Oidn3 and I couldn't find the Firmware for my network here (Three Ireland) so I tried the Firmware for Meteor Ireland another network over here. When I used that Odin went through all the motions and Success appeared in green but when the note tried to start the little green android robot starting blue spinning but the. He was on his back with a red exclamation mark over him.
Again I went into recovery mode and tried to set it back to factory settings etc. but the red lines of code all appeared again.
I replace screens a lot so I know I didn't damage the motherboard so I am really at a loss as to why the happened by just changing the screen or was it because the battery drained. The main question I'm asking here guys is there anyway to get my Note back going again. It seems to be fighting me every step of the way. So I taught I better ask for help from the experts so if any of you guys can help me I would much appreciate it.
Thanks a million guys
Just got a D855 from a friend, she told me it wasn't booting and thought the screen broke (not very tech-savvy).
I somehow got to the point where it cycled between green and blue light on the LED, and managed to copy some files from /sdcard/.
I know the screen isn't broken because I saw the LG logo once.
I tried to boot into downloadmode, it just shows the box for a split seconds and disappears instantly.
I really have no idea what to do, anyone please help!
Jisifus said:
Just got a D855 from a friend, she told me it wasn't booting and thought the screen broke (not very tech-savvy).
I somehow got to the point where it cycled between green and blue light on the LED, and managed to copy some files from /sdcard/.
I know the screen isn't broken because I saw the LG logo once.
I tried to boot into downloadmode, it just shows the box for a split seconds and disappears instantly.
I really have no idea what to do, anyone please help!
Click to expand...
Click to collapse
short circuit
Sent from my HUAWEI NXT-L29 using Tapatalk
Try running the flash tool anyway. It worked for me.
Hi everyone,
I've already search the internet but i've never found that exact same problem and the solution for it
So my problem is when my phone turns off the Samsung logo, vibration etc. everything is ok but the glowing blue led. The led won't stop glowing.
It supposed to stop with the samsung logo at the turning off screen but it never does until i take the battery off.
I'm not sure but i think it started after the battery calibration or something. I hope someone have the solution and time to tell.
Thanks in advance :fingers-crossed:
Which rom and kernel r u using?