Related
I've had this phone since the day it released and generally had no problems with it. But a couple months ago, I started having issues with the home screen loading the icons up every time I went to home. Random reboots for no reason, too. I read that it seemed to be a common issues for the phone, so I thought I'd wait for Gingerbread. But today the phone wasn't begin responsive when I tried to text, so I tried rebooting and now it's stuck on the endless reboot. It seems the only way to stop this is to get it to factory reset itself, but I'm hoping I don't have to do that because the phone did a factory reset by itself a month ago and I don't want to deal with starting over again. Is there another trick to it?
Maybe I'm better off getting it replaced. Are the newer models free of all these glitches or is it all still more or less a crapshoot with the problems I've had, screen bleeding, ect?
Just so it's out there, I rooted my phone with SuperOneClick, but I didn't flash or install any roms.
yea i would sumtimes u just get a bad phone when u flash it!! but i'd try another rom and see what that does!!!
But I never flashed it to begin with. It this happened 6 moths after already having the phone.
But if I can fix it by flashing it, maybe I'll try that. I've been wanting to try that cyanogenmod since it's lookign better than my stock froyo.
Yea I would flash it b4 tryin a new1...n if that doesn't wrk then u no what to do
Sent from my HTC VISION using xda premium
If I flash it, is my phone going to reset itself anyway? Totally new to this.
yup thats y i always flash lol
If you have Clockworkmod Recovery try to just clear the Dalvik Cache. Reboot loops are usually Dalvik Cache issues. The first boot after clearing the cache can take around 5 minutes so be patient.
I went ahead and factory reset it, since I have never flashed it or have any of those apps. If I decide to look into installing Cyanogenmon on my phone, where should I start reading to get all the information to learn how to do it? I've rooted my phone, but that's it. I've stuck to pretty much what was on the phone.
C16MkII said:
I went ahead and factory reset it, since I have never flashed it or have any of those apps. If I decide to look into installing Cyanogenmon on my phone, where should I start reading to get all the information to learn how to do it? I've rooted my phone, but that's it. I've stuck to pretty much what was on the phone.
Click to expand...
Click to collapse
If you rooted it, that means you installed Clockworkmod Recovery. To install CM7 you download the zip package, go into recovery, do a factory reset and wipe the dalvik cache, format the system and flash the zip you got from CM.
I rooted it in Superoneclick though, I don't know if I have Clockworkmod recorvery, unless it's not supposed to show up in the app tray like Superuser does.
Isn't there a way to backup my current state on my phone so I keep all my settings in place? I'll probably get into this tomorrow after work.
Check out tgagunmans nvflash method to get cwm 5.0.2.0 on your phone in dev section.
Sent from my LG-P999 using xda premium
Alright, now it's really ****ing up and pissing me off. I haven't done anything new to it. I was browsing the Market today and now I see that the home button doesn't work at all, I can't snap any pictures, there's no screen lock screen, I can't even change it to airplane mode when holding power, it only gives me the off option. What happened to this thing?
C16MkII said:
Alright, now it's really ****ing up and pissing me off. I haven't done anything new to it. I was browsing the Market today and now I see that the home button doesn't work at all, I can't snap any pictures, there's no screen lock screen, I can't even change it to airplane mode when holding power, it only gives me the off option. What happened to this thing?
Click to expand...
Click to collapse
Have you loaded a lot of apps that autorun when you turn on the phone? Many do and you could be unaware of that. If too many apps are running, or a badly programmed app is running, it can cause issues such as this with your phone.
Also, it sounds like you are still on Froyo with the old baseband. You might want to consider factory resetting it again and running the LG Updater to get GB and the new baseband. Then use the One Click Flasher to install Clockwordmod so you can do backups (basically snapshots of the current state of your device) and then you can play around with alternate roms.
if that doesn't fix it then your device is defective. If you have a warranty you might just want to get a swap going on it.
Yeah, I'm still stuck on Froyo. Is the LG Updater working now? Last I read, it was bricking phones. If it works now, I'm guessing my plan should be:
Factory reset
Use LG Updater
Use One Click Flasher to Install Clockworkmod
Install a rom (Cyanogenmod)
Alot of this terminology is totally new to me, so I'm totally lost reading these tutorials that seem to rely on knowing what these terms mean.
Anyway, would be nice to get rid of all these errors. I can't even install anything from the marketplace anymore, I get a force close.
Alright, tooling around on Cyanogenmod 7 now. I don't like that it doesn't have the LG camera or Swype, so I switched to Weapon G2X. Liking it. Any other recommendations?
Weapon G2x is awesome i keep coming back to it my self.... but for the record i've only owned my phone for about a month and i havn't had any problems at all with i love actually .. i just can't find a kernel that doesn't mess things up back on subject i pretty sure GB took care of most of the problems people were having with the phone i don't know if they did any hardware updates to the newer models
Yeah, it's great. The only issue I have is that Swype doesn't give me a list of alternatives when I double tap a word, so I need to re-Swype the word "if" when it was supposed to be the word "of".
Last question, Can I make multiple backups with Flashworkmod? Now that I've fully set up all my phone, apps and fully configured all my settings, I wanted to back it up to this point so my personalized settings are still accessible. Or is it only one backup?
C16MkII said:
Yeah, it's great. The only issue I have is that Swype doesn't give me a list of alternatives when I double tap a word, so I need to re-Swype the word "if" when it was supposed to be the word "of".
Last question, Can I make multiple backups with Flashworkmod? Now that I've fully set up all my phone, apps and fully configured all my settings, I wanted to back it up to this point so my personalized settings are still accessible. Or is it only one backup?
Click to expand...
Click to collapse
Do you mean Clockworkmod Recovery? The backups are coded by date and time so you can make as many as you want. Consider each one a snapshot of the exact state of the device at the time you made the backup. It will be restored exactly the same.
Yeah, whoops. Clockworkmod Recovery. Thanks for the help!
jboxer said:
Do you mean Clockworkmod Recovery? The backups are coded by date and time so you can make as many as you want. Consider each one a snapshot of the exact state of the device at the time you made the backup. It will be restored exactly the same.
Click to expand...
Click to collapse
Should I be deleting old back ups how much memory does each back up take?
Sent from my LG-P999 using XDA App
Rooted, CM 7.1.0, T-Mobile
Not sure if these are CM issues or HTC's crappy hardware issues, but...
1. When I try to turn on the screen using either the top button or bottom trackpad button, the screen will flash on for a second and then go off again. It will do this two or three times until the screen stays on at the lock screen. Didn't do this before CM, but also didn't start until months after I modded to CM.
2. When using the on screen keyboard(in vertical mode) sometimes it's like the touchscreen is responding very slowly to my taps and CERTAIN KEYS will not work at all. So I'll be typing and the keyboard will be kinda sluggish and suddenly I'll notice that none of the a's I'm hitting are registering. I'll hit the area of the screen over the "a" key and the surrounding keys will register but not "a". I will usually have to turn the screen off and then back on before it starts working again. I think it did this the first time before I modded, but can't quite remember.
Anyone else having these problems?
The first problem has happened before on some roms.
I don't recommend using CM 7, its old, outdated and hasn't been fully patched.
I had that same touch keyboard issue with my HTC EVO shift and my HTC Inspire....an of course all my phones were on different ROMS
Sent from my myTouch_4G_Slide using Tapatalk 2 Beta-4
The first issue... are you oc? If so how much? Really no need to oc this phone. Also, it could be a wake issue, if you are underclocked to much, there is a minimum amount that sometimes has to be higher on some phones than others.
It seems to me these could be kernel issues.
Sent from my HTC Vision using xda premium
mrbmg said:
The first issue... are you oc? If so how much? Really no need to oc this phone. Also, it could be a wake issue, if you are underclocked to much, there is a minimum amount that sometimes has to be higher on some phones than others.
It seems to me these could be kernel issues.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Unless CM over or under clocks by default, then no changes in cpu.
You should run the HTC stock software for a few days or a week to see if the problems you have are persistant across ROMs, or something specific to your current software package.
Just a thought.
Sent from my Bulletproof_Doubleshot using xda premium
Blue6IX said:
You should run the HTC stock software for a few days or a week to see if the problems you have are persistant across ROMs, or something specific to your current software package.
Just a thought.
Sent from my Bulletproof_Doubleshot using xda premium
Click to expand...
Click to collapse
Yeah I've thought about doing that, but I also use my phone for business and switching between roms is kinda disruptive, so I haven't done that yet. Hoping for more feedback from others.
Preparing for backup
Return to Contents Page - doubleshot Developers Reference
Backup Guide
AviatorJud said:
Yeah I've thought about doing that, but I also use my phone for business and switching between roms is kinda disruptive, so I haven't done that yet. Hoping for more feedback from others.
Click to expand...
Click to collapse
Yea, that is something that impacts us all. I could get a lot more dev done if I didn't have to have my plan phone set and ready a specific way each shift to be able to do my job the way i'm expected to.
Best bet would be to wait until you had a day or two off, maybe a weekend or something and when you finish with your obligations before that free time starts:
-try to have near to a full battery or a full one waiting.
Installing a new ROM always works better with a full battery on install, so if you can already be at that step you can start right away instead of waiting for it.
-Make a clockworkmod backup of your device as it sits, and copy that backup to a computer somewhere.
-Get all the ROM files you need to re-install it in a folder with that clockworkmod backup you just made. When you go to put the phone back together to go back to work, if the backup doesn't work for some reason you can at least install fresh and go from there.
-On that note, backup all your apps too. If you do end up having to re-install your ROM you are running right now, being able to install all the apps right away again off the sdcard saves a lot of time and hassle.
Make sure to get those apps backed up to a computer too.
-backup all your contacts. Export everything you can to the sdcard, and then copy that to the computer too.
-Make sure you have all the passwords and account names you need for anything you have installed. (Gmail(s) - Games - accounts tied to apps or services you use)
If you do have to reinstall everything, and you use internet services like dropbox or an internet faxing service you don't want to have to track down those logins if you don't type them often. Make sure you check all your apps and write them down ahead of time.
-Lastly, since you are on CM7, use titanium backup to backup everything and copy that also to the folder on the computer. The word backup in the computer industry is synonymous with redundant, and if it's not you're doing it wrong.
The reason why I said to copy all these backups off the phone and onto a computer is because if something catastrophically bad happens to the phone then what?
By catastrophically bad I mean you format the sdcard by mistake on a factory reset while you're playing with different ROMs - what then?
If you do need the device for work, and you are serious about trying to test the errors against being a phone-specific hardware issue or a software issue with the ROM you are using, then jogging your process by putting this all out there might help you get started.
When you get that downtime, you'll know ahead of time so you can prepare, and then when it hits you have an immediate plan of action to put into place to maximise the time you get for testing.
Also, have the ROM you want to put on it ready to go, and if possible alternates to that - so research the 3 software versions available from HTC for the device.
Also become familiar with this process:
Restore to stock
...maybe download all 3 software versions before your free time hits so you have them already. If everything goes sideways you can always use one of them to restore the device.
If you are S-OFF you have nothing to worry about for doing any of the software updates unless you manually re-lock the device, so just don't do that and you'll be fine.
If you are S-ON speak up and i'll lay out your possible headaches along the way and what we know about them if someone else doesn't first.
If you have prepped before the free time hits:
1 - passwords/account info written down and at the computer you'll be using...
2 - all software packages (restore files, roms, anything else...) that you need downloaded and on the computer you'll be using...
3 - all the apps you use backed up and on the computer you'll be using...
4 - any media like pictures and music or anything else backed up to the computer you'll be using...
5 - a full battery or close to ...
...you are still looking at almost an hours worth of backup time to do the clockworkmod backup, titanium backup, transfer them to the computer, and then you might run a little over that time when you test the clockworkmod backup.
( you always test the backup - the only thing worse then not having a backup is having a corrupt one you thought was good )
...which cuts into your time testing the other ROM enough as it is, but if you aren't ready to do it like this it will take significantly longer.
Since you'll know when the time hits getting a majority of the media, pictures and user generated stuff plus most (if not all) of the apps you use backup up the day before helps cut down on a lot, but that hour is still lost to making a way of putting it back together again.
You also need to leave yourself a solid 4 hours to put the machine back to the way it is before you started on the other side. Again, on install, you want to have a full battery so plan for that too.
4 hours gives you enough time to get everything slapped together from a fresh CM7 install and manually doing all your apps and setting up the phone for work, if the CWM backup fails for some reason and you have to start over.
I just want to see everyone have their phones running right, and if it's a hardware issue then you should get it repaired, if it's a software issue then you should seek a solution - but the quickest way to a result, and the one for your issue, is to directly test it yourself.
Since you sounded like you came to that conclusion too, your only issue now is squeezing it into a time slot you can get so don't hesitate if you have questions on the processes involved.
Edit - also:
If you have multiple MicroSD cards you could use for this, then you can save a lot more time.
You could take the one you have in there now out, and put it to the side so that when you installed your work setup again the memory card and all it's stuff is right there.
Then you could take different memory cards and have them pre-made to what you need, so as soon as you are done backups you power off and swap memory cards.
First one you swap in has the PG59IMG.zip restore file (and nothing else) renamed that way and ready to go, so when you power back on to hboot that installs itself and you save the time spent copying that over before you can install it.
When that finishes, you are back to stock and ready to go, and you didn't change any of the info on your work sdcard.
Something to think about, if work stuff is that important that's what i'd do (and what I do myself, so thought to add it)
Wow Blue, thank you for taking the time to respond. I think I will have some time this weekend to give this a shot. I am S-OFF. And you're right, as long as you plan everything ahead and allow for the time to get set back up, it's not too bad. I'm just trying to decide what rom to try switch to. I really hate sense, so I don't really wanna go back to stock. Wish there was a good stable vanilla to use. Any thoughts?
Oh and if I want to update to the newest radio, which is listed in your "return to stock" thread and then perhaps use another custom rom, like bulletproof, will that radio stick? Do roms not ever update the radio? I just noticed that I am on the original one for the doubleshot, which came out last june.
AviatorJud said:
Oh and if I want to update to the newest radio, which is listed in your "return to stock" thread and then perhaps use another custom rom, like bulletproof, will that radio stick? Do roms not ever update the radio? I just noticed that I am on the original one for the doubleshot, which came out last june.
Click to expand...
Click to collapse
I don't even know what radio I'm on that's a sad thing...but yeah once you update your radio, no Rom will overwrite the radio unless it somehow has one in it you know...
Sent from my myTouch_4G_Slide using Tapatalk
AviatorJud said:
Wow Blue, thank you for taking the time to respond. I think I will have some time this weekend to give this a shot. I am S-OFF. And you're right, as long as you plan everything ahead and allow for the time to get set back up, it's not too bad. I'm just trying to decide what rom to try switch to. I really hate sense, so I don't really wanna go back to stock. Wish there was a good stable vanilla to use. Any thoughts?
Click to expand...
Click to collapse
My pleasure, it's what makes XDA work - people taking time to share what they've learned so others can benefit from or add to the knowledge.
If you are trying to bug-check, honestly, the stock official ROM is a good one to use. It's not something you are so much doing to enjoy the phone, as much as to check on a specific aspect of it.
Further, you are already halfway home on putting the phone back to factory settings if it is a hardware issue, so then you just have to S-ON it and send it in for repair - though you probably won't get it back with S-OFF ability, you will at least be able to unlock it.
Just from directly developing things for the device, and having to go through these testing procedures time and again, I try to set the process up to keep moving, so by going to bone stock if it is broken you already have taken steps to make it what it has to be to send it in, the next looming goal if you aren't going to restore to your work setup.
AviatorJud said:
Oh and if I want to update to the newest radio, which is listed in your "return to stock" thread and then perhaps use another custom rom, like bulletproof, will that radio stick? Do roms not ever update the radio? I just noticed that I am on the original one for the doubleshot, which came out last june.
Click to expand...
Click to collapse
This was just answered above me, but you can always go back to previous radio installs if you are S-OFF...but only if S-OFF.
I've run Bulletproof on the new radio and it runs fine, so doesn't matter either way on that one - other ROMs you'll have to ask the author.
ROMs can update the radio, or only work on specific ones, but for our device I don't think it's been an issue yet, pretty sure everything works with everything on that part.
I can't seem to stop my phone from freezing/rebooting. I managed to catch this in the logcat - http://pastebin.com/m2Wtg4J3. Does it indicate anything and/or is there something else I need to be looking out for? The FATAL ERROR part kinda concerns me.
As the little description states on pastebin, I'm on AOKP B38 and in addition using Matr1x kernel. I've had the error for several days now but with work and other things I haven't had time to really sit down and troubleshoot. Last night I did a full wipe (data/factory, system and boot) a couple times and reinstalled everything. The AOKP ROM followed by the gapps and then the Matr1x kernel. I even redownloaded all of those and verified the MD5's were correct. So after all that, thought I was good. Back at work and already my phone's froze and then rebooted twice. Only thing I can think of is maybe restoring apps via Titanium Backup is messing things up... no clue. If anyone's got any input it'd be greatly appreciated, thanks.
Did Data/Factory Reset, wiped System and Boot once again. After reinstalling the AOKP ROM this time my phone won't boot past the Google screen with the unlocked padlock down below. Looks like my phone is done.
Could be the memory dying on it. So you wiped everything from recovery and it still doesn't work?
I'd send it to warranty.
Correct, wiped everything.
I've only had the phone for almost exactly a year. Thinking about doing the contract buyout thing with Sprint (if I can) and getting the Galaxy Nexus. I guess I should run by the store and see what can be done in the free range, lol. I just noticed I do have TEP.
Flash stock and skip TB and see if its stable.
Sent from my Nexus S 4G using XDA
You said you are using matrix that is UV(undervolted) you need to edit the voltage value to stock to make it stable on your phone because not all phones cant handle Uv.
Sent from my Nexus S®
mixtapes08 said:
You said you are using matrix that is UV(undervolted) you need to edit the voltage value to stock to make it stable on your phone because not all phones cant handle Uv.
Sent from my Nexus S®
Click to expand...
Click to collapse
Dude, I've been on the kernel for ages, can't imagine that issue would arise out of nowhere.
The phone no longer boots into the Android OS. I can still access via Recovery. I tried unrooting but the 1-click method requires to be in the OS and USB Debugging enabled. I can get all unrooted and back to stock just via Recovery right?
I also tried doing the contract buyout at the Sprint store today and just getting rid of my Nexus S for a Galaxy Nexus. Apparently the promo ended a week ago (lucky me) and is only available in certain 'markets' (which of course doesn't include mine [lucky me]).
Ok, glad I brought my laptop with me to work today, got it unrooted, flashed to stock and OEM locked. Reboot to system from the bootloader and same results, can't boot into the OS. Just sits at the boot animation over and over and over and over... fun. Back to the Sprint store!
Tech guy at the store couldn't figure anything out. Got a new one coming on Tuesday, or according to the guy "probably Tuesday." Didn't have the greatest experience with the store today to say the least. The most annoying part being that I was told I can buyout the remainder of my contract and then 2 mins later being told I can't. Normally not one to raise hell but I think I might this time.
Okay, I bought a used MT4GS from a fairly reputable phone reseller called CPR (cell phone repair.) I bought it back in March or April of this year. I immediately rooted and installed a custom rom and CWM. A few months ago I upgraded my rom to CM9 and about a month ago I began having problems. The isses were minor at first, the hardware buttons on the outside of the phone would stop working but I could open the phone and use the ones on the keyboard. Then in the past two weeks all of the buttons would stop working. I thought it was a hardware problem so today I dropped it off at CPR and they took it apart and tested all of the buttons. According to them all the buttons tested out fine. So I have a phone that the only thing that works is the touch screen. Here is the odd thing. If I hold the volume down while booting I get the fastboot menu and can navigate it using the volume keys. If I go into recovery mode none of the buttons work same as in the phone. So either this is a software problem or a systemboard problem. Because my power and volume buttons work on the recovery menu I'm inclined to believe it's a software problem but I'm a little lost on how to fix it. I just tried to boot the phone again and it's now stuck on the boot animation and does nothing. Please help!!!
I was curious if you tried a reinstall before your keys went completely berserk...but no matter now. Sometimes a person will get a bad download though and you can get some WEIRD results from them.
Anyway....this is how I answered on the CM9 Thread if you hadn't seen it......
I've never heard of a ROM brickng a phone especially gradually but I suppose anything is possible. If what you're wanting to do is to return to stock & just kinda "start over" then just go to This Thread and scroll down to the files labeled as "Return to Stock" & download the correct file according to your installed software. Then you can just place it in the root directory of your SD card and reboot into Hboot. PG59IMG files are designed to run from your bootloader and you just answer the few questions it asks as it does.
WeekendsR2Short said:
I was curious if you tried a reinstall before your keys went completely berserk...but no matter now. Sometimes a person will get a bad download though and you can get some WEIRD results from them.
Anyway....this is how I answered on the CM9 Thread if you hadn't seen it......
I've never heard of a ROM brickng a phone especially gradually but I suppose anything is possible. If what you're wanting to do is to return to stock & just kinda "start over" then just go to This Thread and scroll down to the files labeled as "Return to Stock" & download the correct file according to your installed software. Then you can just place it in the root directory of your SD card and reboot into Hboot. PG59IMG files are designed to run from your bootloader and you just answer the few questions it asks as it does.
Click to expand...
Click to collapse
Yeah I actually did that last night. Got to watch the intro animation from HTC/T-Mobile etc. Still no buttons. I'm guessing that the system board has a bad chip since the buttons tested out okay. That is more consistent with the gradual failure than a software bug. Now if there were a rom made for a phone without buttons then I'd be in good shape. Luckily I found an identical phone on Craigslist for $85 which I feel is reasonable for a discontinued phone. Does anybody have recommendations on QWERTY Android phones for T-Mobile that are better than the MT4GS?
Someone mentioned that Samsung is coming out with one soon but I can't remember the name for squat.
If it's for T-Mobile then I suggest the Samsung Relay 4G. Else better wait for Samsung Stratosphere 2 fior Verizon if you might consider changing networks for the sake of a better phone.
THAAAAT'S the one! Samsung Relay 4G. Thank you kind sir!:good:
Samsung took over for HTC, who took over for crApple.
blackknightavalon said:
Samsung took over for HTC, who took over for crApple.
Click to expand...
Click to collapse
Samsung also.
First off let me say I'm sorry about the death of your MT4GS - mine died over a month ago and I'm still in mourning. However, the Relay is a nice little device. I don't want to be accused of attempting to recruit people again, but at the risk of saying so it is an upgrade from the HTC product in MOST ways - some people don't like the screen as much and the camera is definitely inferior. However, it's a nice device. I'm happy with it honestly. TouchWIZ takes some getting used to but since HTC didn't give us ICS, even ICSense... and Samsung has ICS on here with JB to come... I'm satisfied. If you are still curious we have a thread in the G2/Desire forum that we are using until XDA gives us a dedicated forum.
Sent from my SGH-T699 using xda app-developers app
I'm not even kidding, everything takes a good 10 seconds to open. I can't scroll through settings because it takes 3 seconds to register my swipe.
It's a family members tablet and it has never been rooted, or flashed any custom ROMs. The 4.2.2 update came from Samsung and ever since then they've been complaining to me about how slow it is.
I'm having the same problem when trying to clear the cache through recovery - the dead android and 'error'!
I do NOT want to flash a new ROM because it involves resetting all apps and settings back to how they used to be. The owner hardly has any idea how to use it, so any changes will just freak them out.
Is there anything I can do to fix this thing?
eKulzz said:
I'm not even kidding, everything takes a good 10 seconds to open. I can't scroll through settings because it takes 3 seconds to register my swipe.
It's a family members tablet and it has never been rooted, or flashed any custom ROMs. The 4.2.2 update came from Samsung and ever since then they've been complaining to me about how slow it is.
I'm having the same problem when trying to clear the cache through recovery - the dead android and 'error'!
I do NOT want to flash a new ROM because it involves resetting all apps and settings back to how they used to be. The owner hardly has any idea how to use it, so any changes will just freak them out.
Is there anything I can do to fix this thing?
Click to expand...
Click to collapse
You can root it and then try installing agni kennel from recovery
Sent from my GT-P3100 using Tapatalk
eKulzz said:
I'm not even kidding, everything takes a good 10 seconds to open. I can't scroll through settings because it takes 3 seconds to register my swipe.
It's a family members tablet and it has never been rooted, or flashed any custom ROMs. The 4.2.2 update came from Samsung and ever since then they've been complaining to me about how slow it is.
I'm having the same problem when trying to clear the cache through recovery - the dead android and 'error'!
I do NOT want to flash a new ROM because it involves resetting all apps and settings back to how they used to be. The owner hardly has any idea how to use it, so any changes will just freak them out.
Is there anything I can do to fix this thing?
Click to expand...
Click to collapse
Root it and install an app called seeder .
It makes 4.2.2 super fast ..
Greetings;
Either it was a terrible custom Rom, or you didn't flash it properly.
If you wan't it to work properly consider that you will have to Backup your Applications; their Data and your Contacts as well if they are not syncronized with your Gmail Account.
Perform a "Clean Flash" whenever you Flash a Rom to prevent Issues, and use Odin (for PC - Never Odin Mobile) for such "Clean Flash).
Also Consider Researching Before Doing any Operation you are not familiar with.
What you should try:
0) Backup your Apps & Data;
1) Boot your Device under Recovery;
2) Under Recovery:
- Perform Factory Reset
- Clean Cache
- Reboot into Download Mode
3) Open Odin, under PDA Load you Stock Rom [MD5 file] (to revert your Device Settings to Stock).
4) Under Odin: Considering your Device is Recognized, Press Start.
Do NOT Disconnect USB Cable until Odin Displays "PASS" Message.
5) Reboot into " Download Mode " to Flash ClockWorkMod Recovery or CF-Root (or your Fav. Recovery).
6) Once Completed, Boot your Device into Recovery and Perform " Factory Reset ".
7) Test your System.
Let me know how it went.
Best Regards,
Richard
Any Joy
eKulzz: Did you have any success with the above suggestions? I am in exactly the same boat. I inherited the device (Galaxy Tab 2 10.1 5113 16gig) from a family member. I am not really sure precisely when it started to suck so bad....I am assuming, based on the internet posts, that it happened as a result of the 4.2.2 upgrade. It is taking literally minutes in some cases to load a web page. Flipboard is particularly bad. I have cleared cache, uninstalled or disabled every app the tablet will allow, done a full revert to factory, and nothing works. My wifi throughput goes down to miniscule rates (5, 10 , 15 kbps), although once in a while, for larger objects it will jump up to 5 or 10 mbps....so I know it can do it!). I have done IP traces, thinking it might be my internet provider, but the delays are after the TCP/IP response is returned. It seems to peg the CPU and wander off for 10 or so seconds, and then proceed to do the next TCP/IP request.......so if a page has lots of content, it can take minutes to load.
I am at the point that I either throw it away, try to revert to the original android version the tab was delivered with, or possibly go the other way and instally cyanogenmod, in which case it would be interesting to know the best version of android to install on this device, based on other people's experiences.
It is so amazing that this can happen....and it doesn't seem like an isolated case....the vendor just seems to have effectively bricked a major part of their customer base, and won't admit or do anything about it. You can be sure my next purchase will not be Samsung!
However, in Samsung's defence, almost the same thing happened with my Nexus 7 2012 WIFI tablet. The android 5.1 upgrade has made it almost as bad as the Samsung. I wasted days following threads and screwing around, but only achieved minor gains...it is still not really usable. Again, no mea culpa from Google.... I find it amusing that there is such furore when a new release of android comes out and there is such outrage if peoples devices are not supported, or not upgraded fast enough. My point of view now is that I don't want to see an upgrade on any device I have that is working acceptably.....I think there is such pressure from users for upgrades that the vendors are not testing enough and not asking themselves if the upgrade is actually improving usability for the device....
Rick
Have you tried downgrading?
Go sammobile website, Download the Rom version for your device, and follow the procedures i wrote previously.
(Dont forget to erase cache(s)).
Also check for flash counter. You may need to reset it.
Let me know how it went - with detailed info.
Best regards;
Richard
Tried Downgrade
rgxHost said:
Have you tried downgrading?
Go sammobile website, Download the Rom version for your device, and follow the procedures i wrote previously.
(Dont forget to erase cache(s)).
Also check for flash counter. You may need to reset it.
Let me know how it went - with detailed info.
Best regards;
Richard
Click to expand...
Click to collapse
I gave it a try. Got stymied with the USB drivers. I installed them, but the PC (windows 10) will not recognize the USB device, so Odin does not see the tablet.
I got the drivers from the Samsung web site, and also tried another set, but no luck. I am pretty sure they are the correct drivers...., and were installed successfully, so I am not sure whether it is a Windows 10 thing or a driver problem. The PC sees the device when you plug it in and remove it, but reports it as an unrecognized device. I tried re-booting the PC, just in case.
Anyway....it has pretty well stopped me in my tracks.
Rick
Update
Rickster22 said:
I gave it a try. Got stymied with the USB drivers. I installed them, but the PC (windows 10) will not recognize the USB device, so Odin does not see the tablet.
I got the drivers from the Samsung web site, and also tried another set, but no luck. I am pretty sure they are the correct drivers...., and were installed successfully, so I am not sure whether it is a Windows 10 thing or a driver problem. The PC sees the device when you plug it in and remove it, but reports it as an unrecognized device. I tried re-booting the PC, just in case.
Anyway....it has pretty well stopped me in my tracks.
Rick
Click to expand...
Click to collapse
Update: Tried installing the USB drivers from Samsung on a 32 bit windows XP netbook I had lying about. Same result. The tablet is reported by the OS as an "unrecognized device" when I plug it in, and Odin does not see it.
I guess it could be my cable....but it is the only one I have, and since Samsung uses a non standard cable, I would have to buy a new one to find out. I definitely am not going to do that....talk about good money after bad. I have spent about 10 hours on this.
Interestingly, I ran into a guy at a party last night that is experiencing the same slowness on a galaxy tab 2 7" . Seems too coincidental! We were wondering if it could be related to slow SD ram with bad memory locations degrading over time, and possibly a change in android 4.2.2 garbage collection or memory management.
I think the outcome of this is that Samsung is an undependable vendor, that I don't want to invest any more time or money in. No future product I purchase will be from them.
Rickster22 said:
Update: Tried installing the USB drivers from Samsung on a 32 bit windows XP netbook I had lying about. Same result. The tablet is reported by the OS as an "unrecognized device" when I plug it in, and Odin does not see it.
I guess it could be my cable....but it is the only one I have, and since Samsung uses a non standard cable, I would have to buy a new one to find out. I definitely am not going to do that....talk about good money after bad. I have spent about 10 hours on this.
Interestingly, I ran into a guy at a party last night that is experiencing the same slowness on a galaxy tab 2 7" . Seems too coincidental! We were wondering if it could be related to slow SD ram with bad memory locations degrading over time, and possibly a change in android 4.2.2 garbage collection or memory management.
I think the outcome of this is that Samsung is an undependable vendor, that I don't want to invest any more time or money in. No future product I purchase will be from them.
Click to expand...
Click to collapse
Your guess is right, that's the cable issue, I have changed 3 cables already for my tab 2. I bought a cheap USB cable, and that worked same like the original one.(not suggesting you do the same)
Now, about the slowness, it's an every user issue who are on stock rom, yes, Samsung messed up things with ics/jb and a cheap emmc, but you can stop it before the bug hits the stock user and make the tab a hard bricked tab. few users have reported this already. they were on stock, never went custom, still their devices started slowing and eventually bricked or worse, rendered a read only device.
it's that time already, when I would want to see every tab user who are running on stock to take their tabs in their hands and start flashing the custom rom before the tab hits the brick. Good Luck
billysam said:
Your guess is right, that's the cable issue, I have changed 3 cables already for my tab 2. I bought a cheap USB cable, and that worked same like the original one.(not suggesting you do the same)
Now, about the slowness, it's an every user issue who are on stock rom, yes, Samsung messed up things with ics/jb and a cheap emmc, but you can stop it before the bug hits the stock user and make the tab a hard bricked tab. few users have reported this already. they were on stock, never went custom, still their devices started slowing and eventually bricked or worse, rendered a read only device.
it's that time already, when I would want to see every tab user who are running on stock to take their tabs in their hands and start flashing the custom rom before the tab hits the brick. Good Luck
Click to expand...
Click to collapse
Thanks very much for your feedback....nice to know I am not alone, and not losing it! If it is happening to all Samsung Tab 2 users, and the product is basically destined to become useless after a few years of use, and Samsung did not warn users of this limitation when they purchased.....seems like the kind of thing class actions are made of!
As a newbie, I would like to clarify your comments a bit to make sure I end up doing the appropriate thing. When you say that every Tab user should start flashing the custom ROM, I assume you are not talking about the Samsung provided ROMS for 4.1.1 (P5113UECLK7_P5113XACCLK7_XAC) or an updated Samsung 4.2.2. It sounds like doing that will not resolve the issue. Are you talking about Cyanogenmod? and if so, what version of Cyanogenmod and Android OS would be appropriate? .........I wouldn't mind giving it one more kick at the cat, if someone knowledgeable says there is a little glimmer of light at the end of the tunnel!
Thanks for your assist!
Rick
Rickster22 said:
Thanks very much for your feedback....nice to know I am not alone, and not losing it! If it is happening to all Samsung Tab 2 users, and the product is basically destined to become useless after a few years of use, and Samsung did not warn users of this limitation when they purchased.....seems like the kind of thing class actions are made of!
As a newbie, I would like to clarify your comments a bit to make sure I end up doing the appropriate thing. When you say that every Tab user should start flashing the custom ROM, I assume you are not talking about the Samsung provided ROMS for 4.1.1 (P5113UECLK7_P5113XACCLK7_XAC) or an updated Samsung 4.2.2. It sounds like doing that will not resolve the issue. Are you talking about Cyanogenmod? and if so, what version of Cyanogenmod and Android OS would be appropriate? .........I wouldn't mind giving it one more kick at the cat, if someone knowledgeable says there is a little glimmer of light at the end of the tunnel!
Thanks for your assist!
Rick
Click to expand...
Click to collapse
Yes, I meant Custom ROM(cynogenmod) and not stock official builds as they have fixed the trim related problem present with the old stock official ROMs, that's causing the slow downs and eventually causing the tab emmc card to die.
Check here for this emmc bug
http://wiki.cyanogenmod.org/w/EMMC_Bugs
that's one reason, cheap emmc is second (although both users have been hit with the emmc bug but c'mon a person who had never rooted or flashed a custom ROM on his tab ever got hit with this was very disappointing for stock users)
If you check other threads in help and troubleshoot you will see numerous users on stock having more brick issues than the custom ROM users. I have been here from long and have been watching over on all the issues. both have equal share of risks.
See this case here too
http://forum.xda-developers.com/galaxy-tab-2/help/gt-p3100-boot-loop-recovery-information-t3307456
So, if you're planning to choose custom ROMs, take a tour of the General sections for guides and Android development section for ROMS.
Most of the ROMs of our TAB 2 developer Android-Andi, CCD and tuxafgmur are fine and near stable(with updates) (don't go below KK versions)