Story: My mom hates stock touchwiz so I went ahead and installed Cm10.1 on it. She loves it. I own an S2 myself, so its not exactly my phone.(Waiting for the new Nexus or Moto X). Today I realized that the Vibration wasn't working... Thinking it was a software problem, I quickly flashed stock firmware on it to see if that would solve the problem. I was thinking it may have been a broken kernel feature or something. This didnt solve the problem. Now I was getting worried. There may have been a possibility that the kernel could have fried the motor.
This is a $650 dollar phone. She just got it a few weeks ago. I tried different roms, kernels, everything.
I ran into an idea. I once fixed my friends stuck power button my banging it against my table. (funny I know)
Fix: Bang the phone on your knuckles or wrist. Yep. Solved the problem. Figured it was a stuck motor. HOWEVER this did not fully solve the problem. The motor would seize again after a while; Applied same process to fix it. This would only fix it for a while so, In my case, it wasn't a true fix. It may come in handy for those where it was only a stuck motor. Seems like either my vibrate motor is dislodged from the leads or the motor is Semi-DOA.
Anyways, This is a $650 phone. Really? This is Chinese knockoff quality control. There are loads of people having problems with this phone from sound issues to crazy ghosting on the screen. There isn't an excuse. Seems like imma have to set up an RMA or something.
Since your phone is rooted i would suggest to bring it to 2nd hand cellphone shops or repair shop to fix it.... maybe they can fix your problem....
If i helped don't forget to press the thanks button... :thumbup:
Sent from my GT-I9505 using
xda app-developers app
bryanchan727 said:
Since your phone is rooted i would suggest to bring it to 2nd hand cellphone shops or repair shop to fix it.... maybe they can fix your problem....
If i helped don't forget to press the thanks button... :thumbup:
Sent from my GT-I9505 using
xda app-developers app
Click to expand...
Click to collapse
I could do that. Couldnt I use stock firmware and use triangle away?
1. Restore to stock
2. Root
3. Use triangle away
4. Restore to stock again.
?? I should look like I never messed with it?
I would use my warranty while I still have it.
I think you could do that...
1. Backup current rom... use cwm....
2. Download stock rom for your phone
3. Use via odin to install...
4. After install check if your still rooted by using root checker download free from Google play...
5. If your not rooted anymore then your good to go...
* using odin is a complete wipe also root... incase you get stuck on boot loop use your backup to restore... and try reflashing it...
If i helped dont forget to press thanks button...:thumbup:
Sent from my GT-I9505 using
xda app-developers app
Related
i have a non-rooted HTC incredible, however it's stuck in an endless boot loop. I can enter recovery, but that's about it.
any suggestions as to what i can do?
hard reset may work
Sent from my Incredible using XDA App
i tried hard resetting it. this did not solve the problem.
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
i am the second owner of the incredible, and apparently, the warranty only applies to the original owner.
Are you root?
When and how did this start happening?
jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Sounds like you got a bad one. Mine is perfect. No issues.
JaydenR said:
Sounds like you got a bad one. Mine is perfect. No issues.
Click to expand...
Click to collapse
im actually thinking of taking it back and getting a moto droid. i love the dinc, but it is poorly made.
Too bad i cant return, as i got it on release day. maybe if i can pick a good fight with the vzw guy, i could swap it out.
Sent from my Incredible using XDA App
JaydenR said:
Are you root?
When and how did this start happening?
Click to expand...
Click to collapse
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
RUU
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
theanswer said:
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
Click to expand...
Click to collapse
edit: post is useless.
Sent from my Incredible using XDA App
Try the RUU that was posted.
jdmba said:
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
Click to expand...
Click to collapse
these RUUs require the phone to be turned on though. i cant get past the boot screen
theanswer said:
these RUUs require the phone to be turned on though. i cant get past the boot screen
Click to expand...
Click to collapse
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
jdkoreclipse said:
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
theanswer said:
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
jdkoreclipse said:
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
theanswer said:
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
Click to expand...
Click to collapse
ruu, hard reset, and stock img, that is it. Your dinc is hosed. I hope you have insurance??? (this is the part where you say yes)
Sent from my Incredible using XDA App
Welp
While it may not help you, it can't hurt to say. I was having huge reboot issues ... highest number was 13 initial white screen / black screen cycles. I could also NEVER get into Recovery (I could get into HBOOT but when I chose recovery, it would do TWO reboots, the second being full). A battery pull was usually needed.
However, the one thing that allowed me into recovery, etc., was to let the phone charge overnight to 100% and let it be. In the morning, the phone was charged and cool. At that point, I could easily get into recovery, start up, etc.
While I am sure you have tried this; just wanted to note to make sure your phone is cool and you did a battery pull for at least 10 minutes.
I too have this issue
I also have a stock incredible that I bought second hand, which when i bought it, I checked to make sure the device was ok. When I activated it like 2 minutes later it entered a reboot loop. I thought it might be a botched PRL so I went to the Verizon Rep (I met the seller at vz store) and he performed a forced activation. It continued the reboot loop so I took it home. I noticed that if I was outside or near a window, the phone would act normally. I used this discovery to root it and install a recovery. I flashed a few kernel/rom/radio combinations including stock rooted but there was no luck. I flashed back to RUU and it continued to reboot loop. The next day I reversed the activation back to my Eris. 20 minutes later the phone is perfect. I reactivated the device and it commenced rebooting immediately. I took it back to the store and they noted the same behavior. I'm pretty sure it's a faulty radio but since it wasn't activated on the original # they couldn't warranty it. They did tell me if the original owner activates it, they will warranty it so were gonna do that. I hope nobody else has this issue, but if you have this problem, try RUU, and if that doesnt fix it, it's likely hardware failure
Just jumped ships from sprint and got my facinate. Today rooted with one click and tried installing clock work. Thmanage rom manager. All seems well then suddenly my phone freezes for ten minutes I have to do a battery pull. Phone wont boot in anyway or form now. No lights or signs of life other than if I hold the power button as long as its pressed. A device labeled SEC S5PC110 Test B/D appears in device manager. And that'd all it will do. Thinking about exchanging it tomorrow afternoon. Just letting the community know what happened to me any thoughts as how or what happened might be able to help future mishaps
I'd try doing an odin flash. Just search the forums for the step by step. If u can get the phone into flash mode.
Yeah dude, definitely try Odin. Did you try flashing cwm from within ROM manager? I ask because that doesn't work for our phones yet, and it wouldn't surprise me if that could cause problems. I would use Odin to flash it back to stock, and then use the very thorough guide on here on how to get cwm going.
Sent from my SCH-I500 using XDA App
hilarious post title.. good luck tho man. my only word of advice (tho it won't help u now) is to run back ups before you do anything major
illtema said:
hilarious post title.. good luck tho man. my only word of advice (tho it won't help u now) is to run back ups before you do anything major
Click to expand...
Click to collapse
Hard for him to do a backup when he got bricked installing CWM LOL
Possibly bootlocked.
Newer Fascinates seem to be locked. Don't know if there is any way to tell which you've got without attempting a modification of the system....which would of course, result in the above nastiness....
I would think that if newer fascinates were boot locked, so would mesmerizes and I first flashed the stock files for Verizon on my phone then went to elements zinc (which is awesome BTW) installed voodoo 1200 kernel and everything is working great for me. Could just be that he got a bunk phone or something
PhoenixPath said:
Possibly bootlocked.
Newer Fascinates seem to be locked. Don't know if there is any way to tell which you've got without attempting a modification of the system....which would of course, result in the above nastiness....
Click to expand...
Click to collapse
I'm thinking it's just Noob users who are bootlocked...
My phone is only a week old everything went fine root,cwm...
wisconsinated said:
I would think that if newer fascinates were boot locked, so would mesmerizes
Click to expand...
Click to collapse
Why would you think that? Same hardware!=same software...or we'd all be running USC's kernel/ROM.
Could just be that he got a bunk phone or something
Click to expand...
Click to collapse
Could be...which is why I said "possibly" instead of "definitely".
Couldn't get to the flash mode even to use odin, went back today and bestbuy swapped it out for me thinking I just got a bad phone, I could also shake the thing and hear raddling with the usb door shut to so im not really surprised. The new one seems to be working better already, eill try root tonight,
Jwahlg said:
I could also shake the thing and hear raddling with the usb door shut
Click to expand...
Click to collapse
Volume toggle. I bet the new one does it.
good day.
chopper the dog said:
Volume toggle. I bet the new one does it.
good day.
Click to expand...
Click to collapse
He's right, the volume rockers rattle like a sumbitch.
Sent from my SCH-I500 using XDA App
My Fascinate is just twp weeks old and One Click and CWM worked just fine for me. BTW I am running JTs super clean rom. Lovin this phone!
Sent from my SCH-I500 using XDA App
This is why manufacturing companies are locking down phones now. That phone wasn't bricked it could have easily been fixed. OP. Please read and try to learn what u r doing. As well try to have a semi understanding of how u can fix ur phone if u mess it up. I would bet that your phone could have been up and running in 15 minutes.
Sent from my SCH-I500 using XDA App
ksizzle9 said:
This is why manufacturing companies are locking down phones now. That phone wasn't bricked it could have easily been fixed. OP. Please read and try to learn what u r doing. As well try to have a semi understanding of how u can fix ur phone if u mess it up. I would bet that your phone could have been up and running in 15 minutes.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
x10
This is counter development long term.
I further submit that in the future, all root processes require a ten question exam on the users knowledge to work.
Sent from my SCH-I500 using XDA App
Mine crashes sometimes. Even with all original OS. I just pull the battery and all is good.
My volume rocker doesn't rattle, so there is that plus.
Sent from my SCH-I500 using XDA App
Hello all. I am hoping I can get some advice as to what to do about my wife's phone(epic 4g). Her phone is completely stock and has never had any custom rom or anything flashed to it. Over the last three months, the phone has semi-bricked itself 3 times. The phone will just power off by itself and when it is rebooted, it gets stuck at the "samsung" screen. The only way I can get the phone back to normal is by flashing DI18 with Odin v1.85 (no other versions work). Anyway, my wife obviously does not want an unreliable phone. I should also note that about 8 months ago, my 2 year old son took my wife's phone and threw it in the toilet. After taking the phone apart and drying it, the phone worked perfectly for the following 5 months. For that reason, I do not think it is a good idea to have sprint look at it because the water damge indicators will be colored. I have seen a thread here that talked about calling sprint and complaining about the epic and in turn getting a new nexus s. I am not sure what to do. I cannot afford another phone. my wife uses her phone as the house phone as well. The phone bricked itself yesterday so I flashed the stock DI18 rom. I then tried to flash EC05 and it bricks itself again. Even the OTA update bricks the phone when ran. I really appreciate any help/suggestions the community can provide.
Thank you
Sent from my SPH-D700 using XDA App
Interesting problem you have there. I barely remember Di18.
I would use Odin to flash the EC05 stock rom. QBKing77 has an awesome video showing exactly how to do that. That would not brick your phone unless you are using the stock cable. Get a new one. First boot will take a little bit. Here is the link, the description includes all necessary downloads. I would fresh download everything even if you think you already have it. http://www.youtube.com/watch?v=YQ2g6J1JgjU
There is no reason it will Odin to DI18 and not EC05. Water damage doesn't force the phone to like one rom over another. If the others are "not working" as you said, then you are doing something wrong. Follow the video to a T and it will work.
If you want more I would the one click root it with CMW 3101 and remove all of the sprint bloat. Not necessary, but will help the phone a bit.
If the water indicator has already changed, what is stopping you from using a custom rom that is more stable? You might not have as many issues.
Thank you both for your replies. I am using the stock cable, so I will try a different cable. It may be possible that I am doing something wrong as far as flashing roms. It has been a while since I have flashed anything to my phone. Again, thank you very much for the help!
Sent from my SPH-D700 using XDA App
I am just so confused as to why the phone semi-bricks itself every so often. My wife doesn't do anything out of the norm with her phone. I guess the only likely possibility is that the water slightly damaged something.
Sent from my SPH-D700 using XDA App
Arion02 said:
I am just so confused as to why the phone semi-bricks itself every so often. My wife doesn't do anything out of the norm with her phone. I guess the only likely possibility is that the water slightly damaged something.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Like I said, water damage will not cause your phone to only be flashed to DI18. Now the random reboots may have something to do with the water damage, without more info as to what is happening when it reboots I have no idea. Maybe a custom stable ROM with voltage control set correctly would help with that?
Need to take my phone back to att for a faculty gps and after reading around here i found out it might hard brick it.
Well i didn't hard brick, but i am stuck on boot loop.
Any help?
It goes to the att boot animation, then goes back to the Motorola logo one...
I used a File called 2.3.4_pudding_preroot or something like that.
I had a similar problem once and re flashing fixed it, which ill try when i get home from errands, but i wanted to post and ask for suggestions i til I get back to try it.
Im gonna stop at an att store and see if they can give me a replenished one, but i doubt that...
There is probably a thread related to this somewhere too, but im posting from Tapatalk so its hard to look around. Lol
Thanks in advance!
Sent from my Xoom using Tapatalk
Sent from my Xoom using Tapatalk
At&t will refer you to Motorola ...I had the same problem with my ATRIX gps too and actually hard bricked it in the processes if returning to stock just tell them when updating the rom your phone died ...they will overall send you a new one
Sent from my MB860 using XDA App
yokozuna82 said:
At&t will refer you to Motorola ...I had the same problem with my ATRIX gps too and actually hard bricked it in the processes if returning to stock just tell them when updating the rom your phone died ...they will overall send you a new one
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Is there a number for motorola warranty you have? How do I start the process?
Sent from my Xoom using Tapatalk
Just left the att store. There is apparently a DSC (device support center) about 10 miles from here and they'll just replace the phone on the spot. Hopefully they won't say anything about the 'unlocked' text.
Let you know what happens
Sent from my Xoom using Tapatalk
In recovery mode wipe the cache then factory reset. Don't restart the system. Pull the battery out and place it back without touching the power button, it might happen when putting the battery cover back on.
Reflash the desire. sbf file as you normally do with the latest version of MotoHelper and RsdLite program that you can find. Make sure your battery have enough charge for next flash attempt.
The above instructions are what I would do in your circumstances. Please make sure the. sbf is exactly same version as what is on your handset. If the flashing .sbf has higher version then it will be safe.
Good Luck!
CSharpHeaven said:
In recovery mode wipe the cache then factory reset. Don't restart the system. Pull the battery out and place it back without touching the power button, it might happen when putting the battery cover back on.
Reflash the desire. sbf file as you normally do with the latest version of MotoHelper and RsdLite program that you can find. Make sure your battery have enough charge for next flash attempt.
The above instructions are what I would do in your circumstances. Please make sure the. sbf is exactly same version as what is on your handset. If the flashing .sbf has higher version then it will be safe.
Good Luck!
Click to expand...
Click to collapse
Ok got it running at the att store and was able to download GPS status and i compared the performance to the xoom's GPS status. He saw how the GPS just couldn't lock on so he said hell swap it out for me. Waiting on the replacement now
Sent from my Xoom using Tapatalk
Got a new phone. GPS works. Gonna have to sbf again for Unlock and pre root now. Hopefully this one will work out. Lol...
Is there a way to Unlock and root without sbf??
Sent from my Xoom using Tapatalk
razorseal said:
Ok got it running at the att store and was able to download GPS status and i compared the performance to the xoom's GPS status. He saw how the GPS just couldn't lock on so he said hell swap it out for me. Waiting on the replacement now
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Good to hear that. Please make sure you will read the following thread once you got your new Atrix. I get GPS lock in the UK within seconds. I even managed to get GPS lock indoors. A must for every handset really.
http://forum.xda-developers.com/showthread.php?t=1239713
Like the title says. I accidentally wiped the CWR recovery file. I still have the stock recovery backup though.
I was in the same boat with mine, hardware fault and running CWM / CM10. Thought abut trying to wind it back close to stock, but couldn't be bothered. Didn't present a problem with a warranty service, I was nervous enough but figured if they wanted to charge me they could keep it, I only paid 200 for mine, so no great loss.
Sent from my ThinkPadTablet using XDA Premium HD app
hughtc said:
I was in the same boat with mine, hardware fault and running CWM / CM10. Thought abut trying to wind it back close to stock, but couldn't be bothered. Didn't present a problem with a warranty service, I was nervous enough but figured if they wanted to charge me they could keep it, I only paid 200 for mine, so no great loss.
Sent from my ThinkPadTablet using XDA Premium HD app
Click to expand...
Click to collapse
I'm not sending it back to Lenovo, I'm sending it back to the store I bought it from, and they're really picky about **** like that.
Someone please share a backup. I tried the ROW one here on XDA, caused bootloop whatever I do. EU (sweden) 3G model.
All ROW models have the same recovery? Cause i have a ROW tablet and bought it here in the EU.
You can try it if you want.
I'd love to try if you could upload a backup. Köszi!
EDIT: Also, the ROW backup here on XDA is WIFI only, not 3g. Which I assume causes an issue.
Original recovery from my ROW tablet.
Hope it helps.
Thanks, but I was thinking more along the lines of a complete backup. I have the original recovery, what I don't have is the rom itself.
give me an email address and i will send it to you.