Hello,
I don't know why this is happening to my phone. I recently got this phone. I rooted it but it is a stock flash. I only keep apps that I need and disable everything else. However, about 50% of the time, any calls that I get, as soon as I accept it, it's restarts. Also, Whenever I am making a call, the phone goes dark, never comes back on to cancel a call or something and restarts if no one picks up. If someone picks up, the screen goes back on.
What gives?
rationalthinker1 said:
Hello,
I don't know why this is happening to my phone. I recently got this phone. I rooted it but it is a stock flash. I only keep apps that I need and disable everything else. However, about 50% of the time, any calls that I get, as soon as I accept it, it's restarts. Also, Whenever I am making a call, the phone goes dark, never comes back on to cancel a call or something and restarts if no one picks up. If someone picks up, the screen goes back on.
What gives?
Click to expand...
Click to collapse
Most probably ROM problems. Try changing the ROM.
abaaaabbbb63 said:
Most probably ROM problems. Try changing the ROM.
Click to expand...
Click to collapse
But it's a stock ROM. I didn't even install any other ROM.
rationalthinker1 said:
But it's a stock ROM. I didn't even install any other ROM.
Click to expand...
Click to collapse
Yeah, but system errors can occur, like a file being corrupted. This is solved by reflashing the system partition.
abaaaabbbb63 said:
Yeah, but system errors can occur, like a file being corrupted. This is solved by reflashing the system partition.
Click to expand...
Click to collapse
Hey, can you provide me a link or a tutorial on how I can do that?
Thank you.
rationalthinker1 said:
Hey, can you provide me a link or a tutorial on how I can do that?
Thank you.
Click to expand...
Click to collapse
You just take your ROM (Be sure it's the exact version you have installed), and flash it from recovery, without wiping anything.
Related
So before anything this is what I have.
SPL: Danger SPL
MOD:Cyanogen 4.0.4
RADIO: latest
THEME: CyanogenMod-4.0.4-CustomV7 by: Z҉A҉L҉G҉O
So what happened was after I installed this theme everything was running smoothly. My phone was low on battery so I pluged in my Charger. After being on the phone while charging for 30 - 60 minutes my touch stopped working, so I turned it off and on thinking it'll fix the problem and it didn't.
I leave it alone hoping the touch will comeback the the next morning and it didn't. So I wiped and reinstalled CyanogenMOD 4.0.4 hoping that'll do the trick and it juat made things worse.
Now I'm stuck a the "Tap the Android Screen To Begin" and I can't tap it because my touch isn't working.
Is there any way to fix this or just skip that screen?
I need to ge4t back to my gf or all hell is going to break loose.
You could restore your nandroid backup (you have one, dont you?) to get past the tap-the-android screen, or USB/adb kill the process.
Sounds like your digitizer is dead or disconnected. You might need to perform surgery.
lbcoder said:
You could restore your nandroid backup (you have one, dont you?) to get past the tap-the-android screen, or USB/adb kill the process.
Sounds like your digitizer is dead or disconnected. You might need to perform surgery.
Click to expand...
Click to collapse
i agree if a reflash didnt work your g1 needs to go under the knife
JJbdoggg said:
i agree if a reflash didnt work your g1 needs to go under the knife
Click to expand...
Click to collapse
He never said it was a "G1"...
lbcoder said:
You could restore your nandroid backup (you have one, dont you?) to get past the tap-the-android screen, or USB/adb kill the process.
Sounds like your digitizer is dead or disconnected. You might need to perform surgery.
Click to expand...
Click to collapse
No I don't, it would always say error when I tried that.
and how do I kill the process?
Thanks in Adavance if you teach me how.
Is your current issue related to your little trick?
http://forum.xda-developers.com/showthread.php?t=564592
marlopainter said:
Is your current issue related to your little trick?
http://forum.xda-developers.com/showthread.php?t=564592
Click to expand...
Click to collapse
No way!
This happened out of know where haha.
I think I'm going to just try and install cupcake 1.5 if I can find it.
AustinAce said:
No way!
This happened out of know where haha.
I think I'm going to just try and install cupcake 1.5 if I can find it.
Click to expand...
Click to collapse
Anytime you put a device in a freeze, or fridge, there will be condensation on the device. It will then create rust, or short things out. So it could 100% be because of your little "trick".
fenixnr said:
Anytime you put a device in a freeze, or fridge, there will be condensation on the device. It will then create rust, or short things out. So it could 100% be because of your little "trick".
Click to expand...
Click to collapse
Exactly, why would you think it's a good idea to put your phone in the fridge?!
THIS ENTIRE THING HAPPENED BEFORE I PUT MY PHONE IN THE FRIDGE.
Can someone just help me skip the initial process, or just teach me how change the Cyanogen image at the beginning to the original android image.
stop!!! i had this issue were you using a custom user.conf?
i messed up something on mine and phone would lock up nothing at all would happen i was cm 4.11.1 but i had just switch from xrom so went back to and went away but it bothered me so i rent back to rc29 then had more issues up graded to cupcake did one click root and all is good.
jmon777 said:
stop!!! i had this issue were you using a custom user.conf?
i messed up something on mine and phone would lock up nothing at all would happen i was cm 4.11.1 but i had just switch from xrom so went back to and went away but it bothered me so i rent back to rc29 then had more issues up graded to cupcake did one click root and all is good.
Click to expand...
Click to collapse
I kinda don't know what that is.
from the beginning:
I had the hard SPL and wanted the custom V7 them cyan 4.0.4 so I installed Danger.
Then installed the theme, and once I plugged my charger in my touch stopped working so I tried turning it off and on to fix it and it still wasn't working.
So i tried to wipe and reinstall 4.0.4 and got stuck into "tap android screen"
Now I'm back to the hard SPL but I still get stuck at the beginning.
I'm going to send it in, because I think it's a hardware issue not a software issue.
user.conf and userinit.sh and files you push to your ext to tell the ROM what CompCache/Swap settings to use. If you don't know what it is then it's clearly not causing the problem.
So I should jusr send it in?
AustinAce said:
So I should jusr send it in?
Click to expand...
Click to collapse
if i was you i would flash back to rc29 the flash back up to stock cupcake. and see if that helps because you should unroot before you send it in. hope this helps
AdrianK said:
user.conf and userinit.sh and files you push to your ext to tell the ROM what CompCache/Swap settings to use. If you don't know what it is then it's clearly not causing the problem.
Click to expand...
Click to collapse
you can also edit cpu speeds as well has some other things. but your right mainly used for swap settings.
jmon777 said:
if i was you i would flash back to rc29 the flash back up to stock cupcake. and see if that helps because you should unroot before you send it in. hope this helps
Click to expand...
Click to collapse
I flashed back to the rc29
And when I tried flasjing cupcake it said something about no signatures error
jmon777 said:
if i was you i would flash back to rc29 the flash back up to stock cupcake. and see if that helps because you should unroot before you send it in. hope this helps
Click to expand...
Click to collapse
I flashed back to the original radio
And when I tried flasjing cupcake it said something about no signatures error
AustinAce said:
I flashed back to the original radio
And when I tried flasjing cupcake it said something about no signatures error
Click to expand...
Click to collapse
Are you useing the one that came from tmobile? If its hard to find there a guy that has I like in his sig ill try and find it for u if u can't.
Hi guys. I already downloaded everything required for the event that I upgrade from stock eclair to a custom rom. In this case I want to try this one... http://forum.xda-developers.com/showthread.php?t=1253476
Well, this is actually my girlfriends phone. Anyway, yesterday, she was having this com.android.phone has stopped unexpectedly and she's unable to use her phone as well as other force close message. Anyway, just want to know how do I go about this problem.
If I try to do the steps on the given link, would it help? I do hope for an answer because I'm gonna attempt it 7 hours later. Thanks in advance.
rekcah_ogami said:
Hi guys. I already downloaded everything required for the event that I upgrade from stock eclair to a custom rom. In this case I want to try this one... http://forum.xda-developers.com/showthread.php?t=1253476
Well, this is actually my girlfriends phone. Anyway, yesterday, she was having this com.android.phone has stopped unexpectedly and she's unable to use her phone as well as other force close message. Anyway, just want to know how do I go about this problem.
If I try to do the steps on the given link, would it help? I do hope for an answer because I'm gonna attempt it 7 hours later. Thanks in advance.
Click to expand...
Click to collapse
Yes a new rom should fix the problem!!
Or a reboot will fix the problem too!!
Thanks for the feedback.
I got an update from her. When I told her to do a hard reboot, she told me that it got stuck on the logo. I'm gonna check it out later. But if that'd be the case, what should I do then?
rekcah_ogami said:
Thanks for the feedback.
I got an update from her. When I told her to do a hard reboot, she told me that it got stuck on the logo. I'm gonna check it out later. But if that'd be the case, what should I do then?
Click to expand...
Click to collapse
What update???
A custom rom??
Sent from my GT540 using Tapatalk
I meant an update from my girlfriend. Anyway, I'm gonna proceed with the upgrade attempt. Wish me luck
---
Okay, as of now, we're experiencing boot loop. I'm not able to access the phone settings. Is there a button combination I need to press in order for me to be able to access the "settings" Thanks
rekcah_ogami said:
I meant an update from my girlfriend. Anyway, I'm gonna proceed with the upgrade attempt. Wish me luck
---
Okay, as of now, we're experiencing boot loop. I'm not able to access the phone settings. Is there a button combination I need to press in order for me to be able to access the "settings" Thanks
Click to expand...
Click to collapse
Ok did you follow everything properly??
Ok so try and go into recovery!!
Hold home button while booting and you should
see a list of options. use the volume key to find your way.
Go to wipe cache and click yes.
then go to wipe data and click yes.
then go to advance and wipe dalvik cache and click yes.
go back using power button and reboot!!!
That shuld solve the problem!!!
I posted the results on the other thread..
http://forum.xda-developers.com/showthread.php?p=18770109&posted=1#post18770109
Hi, I got my Nexus 7 yesterday. Everytime I leave it in sleep mode for more than 10 minutes it shuts down and i need to hard reboot. I've read somewhere that its possibly Sleep of Death. I tried shutting wifi of during sleep, installed an auto airplane mode app, reset to factory settings about 5 times but nothing seems to help. I run stock rom, not rooted. Do you think i should return it or is there a possible sollution? Greatings
I'd return it
What build number are you in? Settings/about tablet maybe its somthing to do with JR3O0S?
Sent from my Nexus 7 using Tapatalk 2
leelaa said:
What build number are you in? Settings/about tablet maybe its somthing to do with JR3O0S?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Build number is JRO03D
Goldcell said:
Build number is JRO03D
Click to expand...
Click to collapse
I'm the same build JRO03D and I can say that mine dies sometimes after I press the power button to turn the screen off.
I've noticed it happens when I'm reading a pdf book on adobe reader and when I turn my screen off it just doesn't turn on and I have to hold it so it resets and turns on.
Is this a bad build number? The one that ends with a D?
kris4o2 said:
I'm the same build JRO03D and I can say that mine dies sometimes after I press the power button to turn the screen off.
I've noticed it happens when I'm reading a pdf book on adobe reader and when I turn my screen off it just doesn't turn on and I have to hold it so it resets and turns on.
Is this a bad build number? The one that ends with a D?
Click to expand...
Click to collapse
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Silentbtdeadly said:
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Click to expand...
Click to collapse
I'm stock. I've never used a custom ROM or rooted my devices.
Silentbtdeadly said:
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Click to expand...
Click to collapse
I'm running the stock rom from google. I don't know what hardware version I'm on. Thanks for the replies so far!
If the device is otherwise perfect and free of any defects, I might take a stab at trying to fix it by wiping it and reflashing the stock Image. If you can't get it to work you can always return it then.
Goldcell said:
I'm running the stock rom from google. I don't know what hardware version I'm on. Thanks for the replies so far!
Click to expand...
Click to collapse
The first few letters on the sticker on the back of the tablet, at the bottom, will tell you the hardware version..
And you have a choice, if you just got it and can return it, it is unlikely you will have the issue with a new one.. if you can't, you may want to figure out how to flash a stock firmware, as I have a feeling the OTA update may have went wrong. Resetting your tablet(factory reset) just deletes your /data partition, the system partition is not rewritten.. so if there was something wrong with the update in the system files, that won't help.
I am pretty damn sure it is likely kernel related, yet another option to look into.. the nook color(I used to use) has that issue, so it is sad to hear anyone hear have that issue too.
If you are willing to root, you may want to try increasing the minimum clock speed just one step, or if you have undervolted(which I don't think you've said) you may want to raise the voltage or allow stock voltage, as that can also be the issue.
irishrally said:
If the device is otherwise perfect and free of any defects, I might take a stab at trying to fix it by wiping it and reflashing the stock Image. If you can't get it to work you can always return it then.
Click to expand...
Click to collapse
Is reflashing the stock rom the same as resetting it to factory settings?
Silentbtdeadly said:
The first few letters on the sticker on the back of the tablet, at the bottom, will tell you the hardware version..
And you have a choice, if you just got it and can return it, it is unlikely you will have the issue with a new one.. if you can't, you may want to figure out how to flash a stock firmware, as I have a feeling the OTA update may have went wrong. Resetting your tablet(factory reset) just deletes your /data partition, the system partition is not rewritten.. so if there was something wrong with the update in the system files, that won't help.
I am pretty damn sure it is likely kernel related, yet another option to look into.. the nook color(I used to use) has that issue, so it is sad to hear anyone hear have that issue too.
If you are willing to root, you may want to try increasing the minimum clock speed just one step, or if you have undervolted(which I don't think you've said) you may want to raise the voltage or allow stock voltage, as that can also be the issue.
Click to expand...
Click to collapse
I don't have my box anymore. Is there another way to see what your hardware number is?
kris4o2 said:
I don't have my box anymore. Is there another way to see what your hardware number is?
Click to expand...
Click to collapse
I'm not exactly sure, I know the sticker on the back of the tablet itself, toward the bottom has it.. I'm still somewhat new to this tablet yet.
Goldcell said:
Is reflashing the stock rom the same as resetting it to factory settings?
Click to expand...
Click to collapse
I said in my last post, restoring to factory just deletes the /data partition, and leaves the /system files exactly the same. Reflashing actually overwrites the system files.
I get it occasionally but I'm running a CM nightly and Clemsyns elite kernel so I chalk it up to that.
I've flashed stock rom and several other roms, but it did not help so I've returned it for a new device, i have to wait 3 weeks for a new one . Thanks for the replies!
I ran the cache cleaner on Titanium Pro, and after restart my phone appears to be updating then shows an Android is upgrading....screen and just stays there forever. I can restart the phone using the power button and volume down keys, but it just keeps coming back to the Android is upgrading....Starting apps screen. I've got a rooted phone, obviously, but never messed with any custom ROMS or anything like that. Any ideas? thanks
brickedrazrm said:
I ran the cache cleaner on Titanium Pro, and after restart my phone appears to be updating then shows an Android is upgrading....screen and just stays there forever. I can restart the phone using the power button and volume down keys, but it just keeps coming back to the Android is upgrading....Starting apps screen. I've got a rooted phone, obviously, but never messed with any custom ROMS or anything like that. Any ideas? thanks
Click to expand...
Click to collapse
you might have to flash back to stock via RSD lite - but not sure.
How long is "forever?" Every time I clear my cache, it takes a while for the phone to start.
Forever is over an hour before I give up and restart it again. Just gonna take it to Best Buy and get a new one hopefully. Done with rooting.
brickedrazrm said:
Forever is over an hour before I give up and restart it again. Just gonna take it to Best Buy and get a new one hopefully. Done with rooting.
Click to expand...
Click to collapse
Rooting isn't the issue. Wiping cache through TiBu is. Just keep this phone, fastboot back to stock, and start over. If you're just going to give up this easily, you might as well get an iPhone. :good:
How do I fastboot back to stock?
nevermind, I figured it out. Thanks for your help!
brickedrazrm said:
nevermind, I figured it out. Thanks for your help!
Click to expand...
Click to collapse
I'm glad to hear you got it figured out, and I apologize if I seemed like a jerk in my previous post. Now, you know all about fastboot.
It was you using the term "fastboot" that led me to the proper guide on how to do it. Very simple. I was concerned because the computer wasn't seeing my phone when I plugged it in with a usb, but RSD found it no problem. Thanks again!
Hello, I am uploading my MOD ROM and kernel for Sprint. A previous attempt failed, and I just learned that the boot.img I had received was not the actual stock Sprint ROM, so the RAMdisk did not work.
Need someone, or some people to test, so I can make an official post in the ROM section.
As always, I recommend doing a full backup in TWRP to be able to restore to if the ROM does not work.
Also, Titanium Backup is the go-to app to backup your apps (do not backup system apps, only apps that you yourself have downloaded).
Must be on the latest TWRP. Must be fully decrypted. Do a clean flash.
Here is the latest test. I believe it should be fine. Static boot will remain since you have a bootloader not made for your device.
(reuploading, old zip would not flash due to a typo)
Updated, fixed link : https://mega.nz/#!LdkglIyY!8xJVm_1tTNwfrItn-t1n9bq4ZPginAL-DpW07hMwj8o
Tilde88 said:
As always, I recommend doing a full backup in TWRP to be able to restore to if the ROM does not work.
Also, Titanium Backup is the go-to app to backup your apps (do not backup system apps, only apps that you yourself have downloaded).
Must be on the latest TWRP. Must be fully decrypted. Do a clean flash.
Here is the latest test. I believe it should be fine. Static boot will remain since you have a bootloader not made for your device.
https://mega.nz/#!bUlE1RRa!Owuf3BVtZ...Gq8iNcSBRbe4bw
Click to expand...
Click to collapse
what is the decryption key? it will not allow me to download it without it.
ruthlessnature said:
what is the decryption key? it will not allow me to download it without it.
Click to expand...
Click to collapse
whoops
Tilde88 said:
whoops
https://mega.nz/#!bUlE1RRa!Owuf3BVtZ3Hlm96b5jVPGDZZP7gsMGq8iNcSBRbe4bw
Click to expand...
Click to collapse
thanks gonna download now and give it a go I will report back as soon as I can.
ruthlessnature said:
thanks gonna download now and give it a go I will report back as soon as I can.
Click to expand...
Click to collapse
hold on. i gotta reupload... there was a typo in the script >.> my bad
Tilde88 said:
hold on. i gotta reupload... there was a typo in the script >.> my bad
Click to expand...
Click to collapse
Ok let me know when it's good to go.
Sent from my iPhone using Tapatalk
ruthlessnature said:
Ok let me know when it's good to go.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Here is the updated link
Sorry about that!
https://mega.nz/#!LdkglIyY!8xJVm_1tTNwfrItn-t1n9bq4ZPginAL-DpW07hMwj8o
Tilde88 said:
Here is the updated link
Sorry about that!
https://mega.nz/#!LdkglIyY!8xJVm_1tTNwfrItn-t1n9bq4ZPginAL-DpW07hMwj8o
Click to expand...
Click to collapse
I have not been able to get it to boot up. it stays stuck on the static screen? I tried 3 times and did a full wipe all 3 times.
ruthlessnature said:
I have not been able to get it to boot up. it stays stuck on the static screen? I tried 3 times and did a full wipe all 3 times.
Click to expand...
Click to collapse
How long are you waiting? First boot takes about 15 mins.
You still have to do whatever the static boot fix is.
Tilde88 said:
How long are you waiting? First boot takes about 15 mins.
You still have to do whatever the static boot fix is.
Click to expand...
Click to collapse
I waited awhile id say atleast 30 min each time. it never gets to the point where I can shut off the screen to do the static fix. I'm in the process of trying again I will let it sit for awhile longer and see what happens.
Still couldnt get it to boot not sure why.
I locked up too. It happens just about a second into the boot animation. I can see maybe colored balls swirling and then some light text starts to fade in right in the center of the screen then it locks up. Pulled the battery and booted it up a 2nd time just in case but it also locked up and never finished. Gave it 30 minutes the first time and 15 on the second boot attempt.