So i am in need of assistance. I have been running lollipop since it came out basically, but realized that my battery life and performance were suffering. So I decided to go back to kitkat. I flashed the 4.4.4 firmware then flashed the RUU to be safe. Then I reflashed TWRP and flashed nu sense six 4.4.4 v4.02. It is running great, the problem is mobile data is not working at all. I had this problem before. When I used to be on Kitkat certain roms the mobile data would never work. It just says "disconnected" and there is nothing i can do. When I upgraded to lollipop it fixed it so I forgot about it and moved on. But now that I am back to kitkat it matters again. Is there a way to fix this? Also a second unrelated question. My phone barely charges anymore. Any suggestions? I tried buying a new cable from walmart and it didn't charge it AT ALL. My current one is the original cable that came with it and it only charges if you fiddle with it a lot and get it at the exact right angle. When it comes undone in the middle of the night I am left with a dead phone in the morning.
anyone??
You probably needed to perform a factory reset with the stock recovery before you flashed TWRP. Try that and see.
As for the charging, I would first try to clean the usb port. There are lots of ideas on how, Google it. That's the most likely culprit.
Related
i got a notification saying there was a firmware update, which i left running over lunch. came back and it said there was also a dock update, so ran that too. after it rebooted, the touchpad doesn't work. it changes orientation, i can use the dock, i just cant touch anything on screen. ive tried rebooting countless times, even factory reset, but it wont have it.
it was fine up until it installed 8.2.3.13WW so im wondering if theres a way to downgrade to 8.2.3.12 (which this came shipped with) to see if that fixes it.
any help would be appreciated as at the moment i have a glorified eeepc!
If your box was factory sealed when you got it, I highly doubt the original firmware on your device was was 8.2.3.12 as that was only released to a few people as a beta firmware. And those people had to specifically give their mac addresses to even get it.
More likely it came with 8.2.3.9 installed, which you can download from HERE. Using that version of the firmware gives the added advantage of being able to root with it too.
If you want to fix all your issues I highly recommend you downgrade to 8.2.3.9, do a factory reset, then upgrade to the latest 8.2.3.13 available from the Asus site, factory reset again, then check to make sure the version info matches correctly. If still getting problems then your device may have a fault that will require you to get it replaced.
thanks for the info. ill be honest i assumed it was .12 but never really paid attention. i have the .13 download on my sd card but battery is under 50% so cant do it til i get home. thanks for the link to .9 too, will give it a try. it just seems weird that it worked perfectly right up until the update this morning, then died. had the unit two weeks using daily and no problems so it has to be a firmware issue somewhere id hope.
asus support gave the usual "try factory reset" as first and only answer.
thanks once again for the info, will definitely try when i get home
well i got home, charged and ran the 8239,factory reset (no touchscreen) then 82313 and reset and still nothing. have tried it countless times now.
still waiting to hear from asus support as i cant see what else to try, thanks for the link to the firmware though
I had this exact same issue. The only thing that fixed it was to let the battery drain completly (the TF wouldnt even come on anymore) and then when i plugged it back in and powered on it was working again. Give it a shot and see if it works for you.
IsuGuy said:
I had this exact same issue. The only thing that fixed it was to let the battery drain completly (the TF wouldnt even come on anymore) and then when i plugged it back in and powered on it was working again. Give it a shot and see if it works for you.
Click to expand...
Click to collapse
just giving it a try now. typically the unit was fully charged when i was trying the various firmwares so im having to try and drain it. im waiting to hear back from asus and also sent an email to the place i bought from asking about a return if asus cannot fix it.
Well, it worked!
Thank you for that! I let it drain, switched it on a couple of times to make sure it was completely dead. plugged in the charger and when it came on, it worked! you sir are a saviour
mk2media said:
just giving it a try now. typically the unit was fully charged when i was trying the various firmwares so im having to try and drain it. im waiting to hear back from asus and also sent an email to the place i bought from asking about a return if asus cannot fix it.
Well, it worked!
Thank you for that! I let it drain, switched it on a couple of times to make sure it was completely dead. plugged in the charger and when it came on, it worked! you sir are a saviour
Click to expand...
Click to collapse
Glad to hear you got it working. I am not sure what caused the problem but i hope it doesnt happen again.
Hello all, I have an HTC Arrive running LEAD's 7.8 8858 ROM. I've been running this rom since January with very little issues. However, within the last couple of weeks I have been noticing strange things going on with my phone. Some mornings I have woken up and left for work and notice my phone is almost dead, even though I remember plugging it in the night before. Also, as of this week, after a reboot of my phone, the Call button shows Home Service instead of Sprint, but eventually changes over to Sprint. At times I will go to use my phone and see it has put itself in Airplane mode or has a locked sim card logo displayed instead of signal bars. In this case I have to reconnect to the network to regain functionality.
Now as of last night my phone is constantly rebooting while charging. I plugged it in last night and kept hearing a buzz (I keep it on vibrate), looked at the phone and it would be booting up. It fully boots to the Start screen and I can go ahead and begin doing something, but no matter what I'm doing it just shuts completely off without even saying Goodbye (literally). It continues to do this until I unplug it, and it ONLY reboots when plugged in. I've tried a battery pull a couple of times but to no avail. Its getting very annoying because it takes much longer to actually charge, and I also don't imagine this is very good for the phone itself.
I was planning on flashing LEAD's latest release to see if it fixes it, but I'm not sure if the phone will react this way plugged into the PC as well. I haven't plugged in to the computer yet to find out, hopefully it won't do this, else I won't be able to flash it.
Any ideas or suggestions? Has anyone else had this issue?
well i plugged into the pc and it still reboots however, when in the tricolor bootloader it does not reboot! so with this discovery i now know that its a bug in the OS causing the reboots. also, because its not rebooting in the bootloader, i should be able to reflash without issues, correct?
as a side note, the phone got VERY hot last night while left in to charge, so i will just charge my wifes phone and swap the batteries so that i wont damage my phone.
no one else has reported this issue with this ROM as far as i can see, only random reboots.
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
leadpoizon said:
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
Click to expand...
Click to collapse
thanks for the reply lead! i am going to flash you latest release now. i am going to look for an alternative way to backup pictures outside of Zune and the PC, but i dont think any exist.
i will post back when its up and running.
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
x_orange90_x said:
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
Click to expand...
Click to collapse
No problem. Glad your issue is fixed now.
Ok so I am no longer having the charging or battery issues anymore, but now my Marketplace is basically broken. When I can manage to begin a download it immediately goes to Attention Required, and upon clicking i get error code 8000ffff. So no apps will install/download from Marketplace. Also, on almost every game and app, it says this app is not available for your device, even ones i used to use on 8858. Some i have even manually installed and they work fine. Also when trying to even view many of the games in the Marketplace, I get error 805a0194. So far I haven't managed to install anything from the Marketplace aside from the Bank of America app.
I have tried resyncing with Live, rebooting the phone, tried changing Marketplaces and settings with the Marketplace Config app. Nothing fixes it
Any suggestions?
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
x_orange90_x said:
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
Click to expand...
Click to collapse
Sorry, I've moved on from this device, so I can't test anything now. I never had any issues like this on my device and I used it extensively for a long time after flashing that ROM.
I've been having this problem starting the last couple of days. I'll be using my phone, and all of a sudden the screen turns off and nothing short of a battery pull will turn it back on again. Sometimes it happens when I'm not using it at all too. I'll pull it out of my pocket and get nothing. Do a battery pull, and everything's fine again until the next time it happens. Never had this problem before, but in the last two days it has happened 7 times. It even happens when it's plugged in. The LED indicator that is normally lit up when it's charging will go out. Unplugging it and plugging it in seem to have no effect. No sounds, nothing.
I'm running Jellybeans 4.1.2 Rom, with TWRP. Today I ran a backup, cleared and wiped data, fresh install, recovered backup and still having the problem. Should I try a clean install without recovering the backup? Could that have anything to do with it? Any other ideas on what to try or what the problem could be?
If you've been running the same ROM this whole time and it just started out of the blue, I don't really think it would be ROM related. It might be hardware related.
I suppose the only real way to test if it is ROM related is to ODIN back to stock and see if it still happens. If it does keep happening once returning to stock you could probably get it swapped out by Verizon.
BattsNotIncld said:
If you've been running the same ROM this whole time and it just started out of the blue, I don't really think it would be ROM related. It might be hardware related.
I suppose the only real way to test if it is ROM related is to ODIN back to stock and see if it still happens. If it does keep happening once returning to stock you could probably get it swapped out by Verizon.
Click to expand...
Click to collapse
I've been running the ROM a lot longer than I've been having the problems, so I suspect you're right. I've had the phone for over 2 years now, so there's no warranties anymore. If it really is a hardware problem I'm probably looking at a new phone.
I'll try going back to stock though and seeing if it changes. Thanks!
Update: I just flashed did factory reset and flashed back to stock, but can't even get through initial setup before it goes black...guess it is hardware.
Hello,
My phone was running a stock ROM, it was not rooted.
On Tuesday morning i received notification on my phone that I had an update for 4.2.2. I applied the update and it appeared that everything went fine. Unfortunately, the phone immediately began re-booting every two to three minutes.
I have re-set the phone to factory defaults - no change.
I have used different batteries - no change.
I have put the phone into safe mode - no change.
If I put the phone in download mode - it does not re-boot.
I have tried to revert back to an older ROM but ODIN errors out.
Does AT&T have the ability to re-push the update OTA or even roll back to an older version?
Of course my contract is 5 months away from being fulfilled so I believe that I would be forced to pay full price for a new phone should I not be able to resolve this.
Any suggestions?
Thanks.
ShrinkWrap561 said:
Hello,
My phone was running a stock ROM, it was not rooted.
On Tuesday morning i received notification on my phone that I had an update for 4.2.2. I applied the update and it appeared that everything went fine. Unfortunately, the phone immediately began re-booting every two to three minutes.
I have re-set the phone to factory defaults - no change.
I have used different batteries - no change.
I have put the phone into safe mode - no change.
If I put the phone in download mode - it does not re-boot.
I have tried to revert back to an older ROM but ODIN errors out.
Does AT&T have the ability to re-push the update OTA or even roll back to an older version?
Of course my contract is 5 months away from being fulfilled so I believe that I would be forced to pay full price for a new phone should I not be able to resolve this.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
your phone likely is not broken physically, it just needs to be re-flashed. the problem with that is, the flash files dont always get released or leaked right when the ota comes out.
unless someone has a better idea, your best option is probably to keep an eye on your phone specific forum for someone to post the flash file for this new update.
it really doesnt matter if they could push the update again, it would fail on verifying the current install.
if the device was unlocked, it could be rolled back to an older version. i wouldnt hold my breath waiting for them to do that for you.
you could check the forums and see if there is a way to unlock it yourself. some can be unlocked, a lot cant.
bweN diorD said:
your phone likely is not broken physically, it just needs to be re-flashed. the problem with that is, the flash files dont always get released or leaked right when the ota comes out.
unless someone has a better idea, your best option is probably to keep an eye on your phone specific forum for someone to post the flash file for this new update.
it really doesnt matter if they could push the update again, it would fail on verifying the current install.
if the device was unlocked, it could be rolled back to an older version. i wouldnt hold my breath waiting for them to do that for you.
you could check the forums and see if there is a way to unlock it yourself. some can be unlocked, a lot cant.
Click to expand...
Click to collapse
Update...I went to a SAMSUNG experience (or whatever they are called) in a Best Buy and I re-flashed the phone with 4.4.2...no improvement.
I have tried to root the phone with Towel Root and CyanogenMod but neither worked.
In additional attempts to figure this out, My son noticed that if the phone was connected to a computer, it did not re-boot. He though that it was related to it being connected to a power source so he plugged it into a charger, the phone would still re-boot.
So what we have determined is the phone needs to think that it is connected media device. The phone then works as it should.
Any ideas on how to resolve this? If the phone's battery dies and we are not near a useable computer, the phone is then again a paper weight.
ShrinkWrap561 said:
Update...I went to a SAMSUNG experience (or whatever they are called) in a Best Buy and I re-flashed the phone with 4.4.2...no improvement.
I have tried to root the phone with Towel Root and CyanogenMod but neither worked.
In additional attempts to figure this out, My son noticed that if the phone was connected to a computer, it did not re-boot. He though that it was related to it being connected to a power source so he plugged it into a charger, the phone would still re-boot.
So what we have determined is the phone needs to think that it is connected media device. The phone then works as it should.
Any ideas on how to resolve this? If the phone's battery dies and we are not near a useable computer, the phone is then again a paper weight.
Click to expand...
Click to collapse
you have got me on this one. it acts like a classic software issue. now that that has been eliminated.
you performed a factory reset after the flash im assuming?
i don't know what else to tell you, if the software is clean, it has to be hardware damage.
sorry
Hello, here is my problem. I posted it here as well, but maybe it's not the only place because it might be more than a CyanogenMod problem? (http://forum.xda-developers.com/showthread.php?p=57411392#post57411392)
The other day, my phone shut off. I thought maybe my battery (zerolemon standard size) was dead, so I tried charging it, but I realized that nothing was happening. In fact, my phone didn't even start up. I would see the Samsung Screen, then Cyd (sp?) the Android showed up, but it wouldn't boot. I could still get into my Recovery, so I tried reflashing CM11, but it still was broken. I had put in my OEM stock battery at this point. I even factory reset, but nohting.
I found that by flashing Bonestock, that my phone worked, however. So I grabbed whatever photos and files that I deemed important, and tried formatting data, then reflashing the newest cm11 nightly (12/6 i believe. ) STILL nothing. Wouldn't boot.
Finally, I used ODIN to go back to stock (4.1 or something), then rerooted my phone, and put the 12/6 nightly on.
It worked, for the time being. A few random restarts, but nothing weird.
However, Today, i noticed that the random restart happened again. I press the home button, cuz i think it's on, but it isn't. It vibrates, then starts to reset. I see the Samsung screen, then nothing! This is with my zero lemon. I can't get it to go to recovery or anything w/o shutting off.
I put in my stock battery, and it starts right up! However, after a few hours, it starts turning off and doesn't boot up.
I managed to get it into recovery long enough to reflash hyperdrive, because it seems like touchwiz roms work?
questions:
1. is this a CyanogenMod problem?
2. Is this a hardware problem?
3. Is this a battery problem?
4. What should I do? If I stay on this touchwiz rom, I can't use my Moto 360. You need 4.3 or 4.4 to use Android Wear.
5. I am thinking of unrooting and sending my phone back through warranty. (cuz it might be hardware problem). However, if they send me a refurb, would it be unlockable? Cuz it's like 4.2 or something? and then I'm stuck w/o my Moto 360. (what's the latest verizon update?) (also, is there a chance i'd get the phone like 4.1 and then i could still root and unlock bootloader?)
6. the other day, before this happened, it was raining and i used my phone. i don't think water got in... but could this be the result of that? I don't see how water would hate CM but like TW though.
Thanks, any ideas would be super helpful.
chances of getting a phone that is rootable and bootloader unlockable is very low, if there's any chance at all. if you wann try and replace the phone why not try swappa and look for one that is either bootloader unlocked or look for one that is capable of being unlocked. other then that, i dont see any way of getting another one that you can root and rom.
Thanks. I would get a replacement through my Verizon insurance. I guess it might be the end of an era for cm my galaxy s3. Sigh. Just looking forward to nexus 6 hopefully for Christmas.