Database Users

[Fix]boot freeze-up

hello folks,
I have seen some threads talking about some WM device freezing in bootup, and stick in the 1st screen when it says "stick together", I had the same problem, and I did contacted HTC for support, it seems they dont have a solution for that problem but to send the phone to them, whicj gonna take around 10 or 15 days to get back -if the warranty still in effect- and they probably gonna charge you something more than the shipping back fees, cause you flashed your device.
I was Planing to send my phone this monday, but i though lets try something and see what gonna happen, so what i did is :
1 - take you SIM card and your SD card, (don't connect your phone to your PC)
2 - While holding the VolUp press the Power button, you will see a screen with your device information
3 - Now connect your device to you PC, and use one of the Wm costume ROM, don't worry about the guide line, and about the winSync instruction, cause it do work without windows Sync
4 - follow the instruction on the costume ROM application, and just ignore the WmSync one.
your phone will reboot, and you probably gonna see your device radio and room information.
I just did the sameting to fix my device, I don't know if just got lucky
But I do have a problem now, I cant install android on my device, and when i try to lunch CLRCAD, it does not start, even when i lunch haret, the device reboot, if someone know a fix to that problem, so may help me.

dude, out of your three posts, two have been new threads that are strictly related to user-problems in a developmental sub-forum, which just isn't cool.
its like someone walking into your work meeting and asking about the lunch schedule (not the best analogy, but you get the point)
if you're really stuck in something, a hard reset always restores things nicely

bravo261 said:
dude, out of your three posts, two have been new threads that are strictly related to user-problems in a developmental sub-forum, which just isn't cool.
its like someone walking into your work meeting and asking about the lunch schedule (not the best analogy, but you get the point)
if you're really stuck in something, a hard reset always restores things nicely
Click to expand...
Click to collapse
i'm just trying to stay in the dark, waiting for the moment to say something useful, by the way hard reset does not work all the time

The only time a hard reset does not work is if there is something wrong with your phone or somehow you corrupted your ROM. In that case going into Bootloader and upping a new ROM does the trick. A Task29 will really fix things well.
As far as "launching" CLRCAD...it does nothing ANYWAY! You just tap it and that is it...it merely sets up the phone for Android to have sound, nothing more...no prompts, no hour glass nothing. (A SEARCH or reading the first post would have told you this.)
If you get resets in Haret then Android did not load correctly. Merely delete your data.img and start over. If that does not work then you likely corrupted your Android build....format your SD card and reload Android from scratch.
I personally have backed up my working daily build on a weekly basis so in case my Android gets hosed, I merely have to copy my entire backup (which is just a copy of my SD card on my computer) back to the SD card after a format (but have yet to really have a need for this except months ago).

[Q] Frozen focus and Flashing won't fix... Please advise me!

I flashed the Omnia 7 ROM onto my samsung focus after the memory was ruined by a bad microsd card (had only 15mb of memory, many people have had this issue from what i read). The unique problem is after flashing the samsung omnia 7 ROM onto the phone it now will not load past the samsung load screen it just stays frozen.
I have flashed every ROM possible onto the phone and it will not complete and just freezes on the samsung screen despite seeming to complete on the computer and even on phone to extent (shows the green loading bar on bottom while flashing). I figrue by this point one of you smart guys have figured out how to solve this. I would love to replace my HTC surround with my focus to refresh things.
PLEASE somone help me... Can someone at least confirm the phone is useless, and if so what I should do with it? Or is it possible that I can unlock it again somehow.

tmo Dell Venue Pro will not update to mango

So I just got a dell venue pro a few weeks ago from a friend, it was basically new, and i finally got it carrier unlocked, but i CANNOT get it to update from 7.0.7403.0
everything seems to work fine, i downloaded the most recent zune software, i connect the phone and it has me rename it, everything works fine at this point (sync and connection are OK), the software recognizes there is an update, so i hit "update now" and it begins to update.
from this point it will stop at random spots, usually at step 6/10 "resetting phone" is where it quits most, usually getting stuck on the dell logo, but sometimes at 15% or 20%...either way it will freeze the zune software or freeze the DVP itself and i'll have to remove the battery to get it to work again...
anyway, if anyone knows how to fix whatever is wrong with it, i really want to get it updated.

I've heard of weird problems like this. People having to try the update multiple times before it will be successful. One person said he had to try using a Windows Vista PC before it worked. If you have another machine, even if it's also Windows 7, try that next. Also make sure you are using a high quality USB cable of appropriate length.

I just tried a few different USB cables, the furthest point i get to now is step 6 of 9 "restarting your phone" and the phone freezes at DELL logo. Has done that 3 times now...
this is a pretty poor first experience with Windows phone

yessssssss victory.
for anyone having any similar problems i tried like 3 USB cables since i dont have the original Dell cable (dont know if that has anything to do with it really) and 3 different computers too, finally got an XP machine to do it.
my phone froze during my first attempt, so i pulled battery and did it again. phone was backing up and "resetting"
but it never reset, it just went to dell logo and froze.
i was pissed so i just pulled battery and made it update the exact same setup again
for some reason this time it did the entire update until the final 9/10 reset, which it froze at too.
however this time when i disconnected the phone to pull the battery the zune software didnt throw an error or even look like it knew the phone was disconnected.
so i pulled battery and held down Pwr Vol Camera to put it in that software mode and plugged it back in, it acted as if it had successfully reset and finished the update...Finally, this was way more trouble than its worth IMO.
hopefully anyone that has the same issue will get some satisfaction from knowing it can be overcome.
+ im still getting random resets when using Wifi and the market, so im going to swap my 8 gig card for a 32 and see if that can be cleared up too.
+lol, 32 gig card swap is a breeze and ive had no issues yet. sweet.

Make sure to get all of the WP and firmware updates so you won't have the wifi bug. I think the larger SD card isn't a permanent fix but it's fixed with a later update. This update is worth the trouble
If you feel adventurous, you can force an update to 8107 too
http://forum.xda-developers.com/showthread.php?t=1497142
xellion said:
yessssssss victory.
for anyone having any similar problems i tried like 3 USB cables since i dont have the original Dell cable (dont know if that has anything to do with it really) and 3 different computers too, finally got an XP machine to do it.
my phone froze during my first attempt, so i pulled battery and did it again. phone was backing up and "resetting"
but it never reset, it just went to dell logo and froze.
i was pissed so i just pulled battery and made it update the exact same setup again
for some reason this time it did the entire update until the final 9/10 reset, which it froze at too.
however this time when i disconnected the phone to pull the battery the zune software didnt throw an error or even look like it knew the phone was disconnected.
so i pulled battery and held down Pwr Vol Camera to put it in that software mode and plugged it back in, it acted as if it had successfully reset and finished the update...Finally, this was way more trouble than its worth IMO.
hopefully anyone that has the same issue will get some satisfaction from knowing it can be overcome.
+ im still getting random resets when using Wifi and the market, so im going to swap my 8 gig card for a 32 and see if that can be cleared up too.
+lol, 32 gig card swap is a breeze and ive had no issues yet. sweet.
Click to expand...
Click to collapse

You know I see this phone such a fine piece of hardware and when I read about problems people have or get into with this phone... it really disappoints me. I thank god my DVP works perfectly fine since day one. The phone is also updated to the latest and I got tmobile service on it. Everything works fine. I hope I don't ever run into any problems. You guys know whats up in making the custom roms? Man I want to post some info in the other developer thread but I am not allowed yet until I get 10 posts. I am helping currently a reseller on ebay with some DVP he has to fix and probably can provide technical information if needed.

[Q] URGENT HELP with a fully bricked defy

Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve

To get into the bootloader , keep the volume up button pressed and then press the power button. Is this what you tried to do?
And I didn't get the part where you wiped through the bootloader. As far as I know there is no option there. Do you mean the stock recovery?( The yellow dots are there in the stock recovery)
Sent from my MB526 using xda app-developers app

wahat3 said:
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
Click to expand...
Click to collapse
Check out this link all the best :good:

Samsung S5 reboots casually, and then does not boot for a certain period of time

Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!

hurricane flow said:
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
Click to expand...
Click to collapse
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838

eidairaman1 said:
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
Click to expand...
Click to collapse
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.

I will follow up on the battery swap when mine arrives.

hurricane flow said:
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
Click to expand...
Click to collapse
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.

eidairaman1 said:
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
Click to expand...
Click to collapse
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!

hurricane flow said:
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
Click to expand...
Click to collapse
I thought it was a bad rom flash as well or SuperSU causing it, well I found another article stating they replaced the battery and the issue went away. I think the phone was stating a bad POST so it would restart