Related
Hello, I have an Axim X51v that I bought off someone who didn't want to deal with it anymore. Anyway when you turn it on it hangs at the dell logo or sometimes at the windows start up logo, rarely it makes it into windows but it freezes up after a little while. I've tried flashing several different roms on it (so did the previous owner) but each time it's the same result. I've checked diagnostics mode (record+power+reset) and everything seems to check out (flash has a green zero) and every time I flash a rom it makes it through without any problems. Also the bootloader is a10_g3 is this version known to be unstable? Could it be flashed wrong? That's the only thing I can really think of.
You know this forum is for HTC devices?
Im not familiar with Dell PDA's but i cant imagine flashing roms willy nilly will work on a dell which are designed for HTC devices. Give me a link for the ROM which you are currently trying to use.
Have you tried flashing original rom back on, thats wm5 yes?
Yeah I know it's for htc devices (this is where I get roms for my kaiser). But I've also seen roms for the x51 here too and I assumed someone may know something about em here. Anyway I have the "stock" wm5 rom flashed right now (flashed with sdloader) and it's pretty much in the same shape.
We don't frown upon answering questions for other devices. This forum is meant to help people. If you can get your answer here.. cheers on that.. hope you will.
mbannick said:
Yeah I know it's for htc devices (this is where I get roms for my kaiser). But I've also seen roms for the x51 here too and I assumed someone may know something about em here. Anyway I have the "stock" wm5 rom flashed right now (flashed with sdloader) and it's pretty much in the same shape.
Click to expand...
Click to collapse
sorry wasnt meaning to sound sarcastic, ive had some experience of axim but mostly wm5, just wasnt too clear on ur issues, what exactly happens? you say it freezes but what do you do that makes it so?
Well that's the thing it freezes randomly, even just sitting there it will freeze. I want to say its the flash but every time I check it the test comes out clear. So the the only thing I can think of is the bootloader is messed up.
Ive just been to the dell support site and wow, alot of un happy people, i can see why your friend didnt want it anymore...
After doing some reading there i can only suggest you download their official rom and rom updates and see if you can get it running normally. What i dont understand is flashing a new rom should clear everything, i dont think it is the bootloader if the system boots up fully correctly, it has to be a rom issue (or hardware of course).
check out these sites, doesnt make good reading im afraid :
http://search.euro.dell.com/results...~srd=False&ipsys=False&advsrch=False&~ck=anav
http://en.community.dell.com/forums/3530.aspx?PageIndex=2
good luck and let me know how you get on.
Well as I said it takes several tries to get into windows (sometimes it wont work at all until I leave it without the battery for an hour or so) so its not booting up normally at all . Anyway I had the wm5 a12 rom on there for a while but it still has the same problems (I used sd flash since I really cant sync and flash with the way it freezes). So yeah I'm not sure what I can do
mmm.....
If youve had several different roms on it, including official ones, it could mean a hardware problem too.......
Im no chef, but i would have expected a bootloader issue to be resolved with a known working official rom?
How old is the Dell? Just a thought, have you tried the online help with a technical rep from Dell, they were good when trying to sort out an issue with my 4 year old laptop? Sorry but im running out of ideas........
Hey I think I got it! Seems the previous owner modified the battery latch. After messing around a bit I stuck a toothpick on the "button" that is depressed when the door is closed and it seems to be running perfectly stable! I even did a few resets and each time it boots just fine. Thanks to everyone who replied and offered advice.
hoorah! saved by a tooth pick, now ive heard it all haha. congrats!
Last week I rooted my primary phone, a Samsung Admire with Gingerbread 2.3.4. This was done only after successfully rooting my older LG Optimus T running Fryo. I had no trouble with either phone during the process. However, as of 2 days ago the Admire has had some troubles, namely that the phone function crashes when I press the send key. I get the error message stating “Sorry! The process com.android.phone has stopped unexpectedly. Please try again.” It will receive incoming calls but they cannot be answered and when I try, it crashes
I’ve spent much of the time since researching the problem to find the cause and it’s fix. In doing d\so I have read of multiple causes from screen resolution changes to attempted over clocking, which I have played with. I’ve read that there might be problems with the phones attempting to switch from 2g to 3g too rapidly, something this phone cannot do I believe.
I came to the conclusion, probably erroneously, that I needed to reset it back to factory and then reinstall apps and data out of the backup I made using Titanium Backup prior to the phones troubles. So I did so, doing the three button cocktail I’ve read about here on XDA Forums. After doing this, the problem persists. I’ve read some more becoming more baffled as I went along. So I tried to reroot the phone using one click root, and that was unsuccessful as well, no root. I then read that all I needed to do was to install Superuser from the Market. In attempting this I found my device was no longer recognized by Market and after going through their troubleshooting process it’s still unrecognized, Next I decided, also most likely erroneously to reset the phone again using the three button combo as before. This time I noticed at the bottom of the screen written in yellow, E: File is written: not updated
Also as a side note my phone currently says that there are 133MB available and after the reset(s) my bloat ware has not returned,
So that’s it. I seem to have deleted something that kills the phone app and prevents me from rooting. Other than those two things the phone is working well. However as it sits it’s merely a small Internet tablet with no phone capability. Can anyone help me out with this? And yes, I have read and read and read about it but clearly this is beyond my ability to fix on my own.
Thanks,
Zeke
Hey, my skill level ranges between beginner and intermediate, but honestly in a situation like that I would odin back to stock. I have an epic 4g, so I have no idea what your download mode is or if you have one or if you have to use quick boot or fast boot? Its one of those. If **** ever hits the fan on me (Thank god it hasn't yet) I would odin to an old stock rom and root it and install a recovery and wipe and flash a ROM. Good luck I hope I helped and didn't sound like too much of a scrub.
Reached said:
Hey, my skill level ranges between beginner and intermediate, but honestly in a situation like that I would odin back to stock. I have an epic 4g, so I have no idea what your download mode is or if you have one or if you have to use quick boot or fast boot? Its one of those. If **** ever hits the fan on me (Thank god it hasn't yet) I would odin to an old stock rom and root it and install a recovery and wipe and flash a ROM. Good luck I hope I helped and didn't sound like too much of a scrub.
Click to expand...
Click to collapse
I will research this Odin you mention as I have no clue as to what it is. Thanks, anyone else care to chime in?
Zeke
Hi,
I've been using using the Endymion 3.1 ++ ROM for about two months and everything has been OK until I found out that it's recently started doing a weird thing - when I lock the screen by the hardware button, the screen randomly turns on as if I unlocked the phone. I don't recall making any changes that could possibly influence this.
Any advice?
Thanks
Pride4u said:
Hi,
I've been using using the Endymion 3.1 ++ ROM for about two months and everything has been OK until I found out that it's recently started doing a weird thing - when I lock the screen by the hardware button, the screen randomly turns on as if I unlocked the phone. I don't recall making any changes that could possibly influence this.
Any advice?
Thanks
Click to expand...
Click to collapse
Does it happen on any other ROM, or only on Endymion? Have you tried Reaper and tried to reproduce the problem there?
I'm quite inexperienced in this business - I've rooted and installed my phone because it got broken during an official upgrade to a higher Android version. Therefore, Endymion is the first and only custom ROM I've tried so far and to be honest I don't feel like backing up and setting up everything on my phone again. (unless I actually have another choice, that is)
And I'm using the Unity kernel from this forum if it could help.
Pride4u said:
I'm quite inexperienced in this business - I've rooted and installed my phone because it got broken during an official upgrade to a higher Android version. Therefore, Endymion is the first and only custom ROM I've tried so far and to be honest I don't feel like backing up and setting up everything on my phone again. (unless I actually have another choice, that is)
And I'm using the Unity kernel from this forum if it could help.
Click to expand...
Click to collapse
Why use Unity kernel with Endymion when Endymion kernel is excellent on the ROM by itself?
I would suggest you try another ROM like Reaper and see if the problem persists...
Someone who appeared to quite well-versed in rooting etc. advised me to use "a faster kernel" and suggested the Unity kernel. I don't understand this a tiny bit so I followed the advice. However, I don't think the kernel is the cause because I installed it long before the problem occured.
Pride4u said:
Someone who appeared to quite well-versed in rooting etc. advised me to use "a faster kernel" and suggested the Unity kernel. I don't understand this a tiny bit so I followed the advice. However, I don't think the kernel is the cause because I installed it long before the problem occured.
Click to expand...
Click to collapse
Why I asked you to try another ROM is because if my hunch is correct, you have a hardware problem... I just didin't want to say it till we had ruled out the software issue. This is the exact same thing that happened to my wife's phone a month after purchasing it (Desire S) and HTC put it down to a hardware problem (mainboard) and replaced the device free of cost under warranty (wife never allowed me to touch her phone, so it was S-on, stock!!)
I hope you don't have the same problem, but it sounds exactly like the problem my wife's phone had... the only way is to flash another ROM and see if the issue persists. Make a nandroid backup. What have you got to lose?
What I've got to lose is the time spent, but I guess I have no other choice so I'll get around to it as soon as I find the time.
If it's HW problem I may encounter some trouble as I've bought the phone from an e-shop that sells unofficially distributed phones because they offer considerably lower prices, although it is true that the customer service and complaints may be rather poor.
I'd have to send the phone to them and wait like a month or so until they finally decided that my complaint wouldn't be accepted :-D Not to mention that I would have to unroot the phone and change it back to the S-ON setting.
Anyway, let's hope for the best.
Shameless bump - I'd like to ask a question about Titanium Backup.
I've backed up my installed apps but would like to know whether it will be OK if I back up the system and user data - I don't if it matters that the data will be from a different ROM - in other words, if the system structure doesn't change.
For contacts backup Google sync will be the best I guess.
EDIT:
Installed Reaper 1.6 and the problem is gone. I lost some data in the process as Titanium backup didn't back up the notes from Endymion HTC Notes, never mind, though.
EDIT2: EPIC FAIL! I was probably just unlucky not to see the phone flashing for a long time but today I've seen the screen turning on of its own accord again. Repair service, here I come! :-(
Alright I am absolutely PI$$ED OFF. I installed 2.0.0 earlier this morning and I've been at it all day trying to fix all the stuff that "update" broke. Moment I installed it my wifi & camera ceased to function, moments later WhatsApp is crashing. So after trying to fix those issues I gave up and restored a backup back to 1.8.0 right? Well now my wifi and camera work but all of Googles bull**** is crashing (google play services, something else) and WhatsApp is still messed up. I installed a new copy of gapps and the google crashing is still persisting. WhatsApp I can't really do much about because I'm using an old number on it to prevent from giving people my new one and i don't want to lose that privilege. The only way I can even use my phone is by slowly getting to Titanium backup and freezing them all. I've wiped my /system, /cache and dalvik cache about 5 times and still no luck. I can't even begin to see how this could relate to my /data partition as I was sure to not let the 2.0.0 update touch it but if it is then please tell me cause I am so fed up right now that I'm ready to toss this phone into a wall then snap it in half and set it on fire.
(THIS IS ABOUT ViperROM)
What in the the Nar Shadda do I have to do to fix these phone wrecking issues? I just want to use the version I've been using for the past month or so again, honestly if I'd known I would have to deal with this much crap I never would've EVER installed this update.
Now on to a little less venting and to more explaining, I've had this wifi issue that I had on 2.0.0 back when I first switched to KitKat on my old Galaxy S4. The camera issue I have never experienced and none of the fixes fixed it except downgrading to 1.8.0, the camera would never display anything on the default camera app & when i downloaded googles camera it would say "Can't connect to camera". on the google apps topic i figured installing a new gapps would solve it but apparently i am wrong. Whatsapp issue i haven't the slightest clue.
Sounds like some sort of firmware problem to me.
S1L3nTShaDoWz said:
Alright I am absolutely PI$$ED OFF. I installed 2.0.0 earlier this morning and I've been at it all day trying to fix all the stuff that "update" broke. Moment I installed it my wifi & camera ceased to function, moments later WhatsApp is crashing. So after trying to fix those issues I gave up and restored a backup back to 1.8.0 right? Well now my wifi and camera work but all of Googles bull**** is crashing (google play services, something else) and WhatsApp is still messed up. I installed a new copy of gapps and the google crashing is still persisting. WhatsApp I can't really do much about because I'm using an old number on it to prevent from giving people my new one and i don't want to lose that privilege. The only way I can even use my phone is by slowly getting to Titanium backup and freezing them all. I've wiped my /system, /cache and dalvik cache about 5 times and still no luck. I can't even begin to see how this could relate to my /data partition as I was sure to not let the 2.0.0 update touch it but if it is then please tell me cause I am so fed up right now that I'm ready to toss this phone into a wall then snap it in half and set it on fire.
(THIS IS ABOUT ViperROM)
What in the the Nar Shadda do I have to do to fix these phone wrecking issues? I just want to use the version I've been using for the past month or so again, honestly if I'd known I would have to deal with this much crap I never would've EVER installed this update.
Now on to a little less venting and to more explaining, I've had this wifi issue that I had on 2.0.0 back when I first switched to KitKat on my old Galaxy S4. The camera issue I have never experienced and none of the fixes fixed it except downgrading to 1.8.0, the camera would never display anything on the default camera app & when i downloaded googles camera it would say "Can't connect to camera". on the google apps topic i figured installing a new gapps would solve it but apparently i am wrong. Whatsapp issue i haven't the slightest clue.
Sounds like some sort of firmware problem to me.
Click to expand...
Click to collapse
First thing. Before you ever take a update... Have you ever heard of a nandroid...
Second. Did you check your md5?
Third. Actually try wiping your data partition... When switching ROMs or even doing a update to a ROM with a new version such as 4.4.3 from 4.4.2 it's smart to wipe data and everything except internal and external SD card.
Forth. Why did you install a new GAPPS? That WILL cause crashes...
Fifth. We don't have updated firmware for 4.4.3 with a 2.22 base. That will cause some issues. It's a given.
Sixth. Have you tried a clean flash of viper 2.0?
Seventh. Have you tried installing another ROM. If so did you have the issues there.
Sent From My HTC One M8 Running Insert Coin. S-OFF.
I agree with person above me...don't flash viper 2.0 till we have 4.4.4 firmware.
An why not flash stock recovery do a factory reset an then go one about your way with it back to out of box set up.
Tigerstown said:
I agree with person above me...don't flash viper 2.0 till we have 4.4.4 firmware.
An why not flash stock recovery do a factory reset an then go one about your way with it back to out of box set up.
Click to expand...
Click to collapse
I didn't really read up too much on 4.4.3 other than it was a security patch I believe? & I considered that but I had tons of messages which I would lose that were important beyond what I'm willing to explain. In the end I said f*** it and just restored my 12 day old backup. Really the only thing stopping me from doing that is my WhatsApp account, I have it setup to use one of my old phone numbers so I never have to disclose real information when I want to give someone my WA. Losing that would mean giving a lot of people something I really don't want to give out...
Now onto the person above me and his idea of my Nandroid doings, yes I have some but I don't have the storage to keep making them everytime I flash something which is practically every week knowing me. & before someone tells me to quit being a lazy "idiot" I simply don't want to spend the time deleting my backups every month when I run out of storage, much un-needed inconvenience. Yup could put them on PC, too bad I'm also running out of storage there too. Could use cloud, no, not into putting my private information and files onto a highly vulnerable privacy invading idiotic creation. In before someone insults me for calling the cloud idiotic, yes it is. I stand by that and have no intents on replying to anyone that may bring that up.
Onto the /data topic, it shouldn't have even touched my data partition if it was just a mere "update". & just now I went and read up on 4.4.3/4.4.4 and the differences = Bug fix & Security update (4.4.4). Most ROM's I've seen actually tell you you don't have to wipe /data unless coming from another ROM, simply that it's better to do it. If it was really such a necessity it should've been stated or stated more seriously/obviously. If 2.0.0 was like Jellybean to Kitkat or Kitkat to Lollipop then yeah i'd understand. If someone with a higher knowledge would like to enlighten me as to why my /data was ruined from such a minor update then feel free to tell me (no more cocky responses after this please, civil only.). Maybe 4.4.2 to 4.4.3 really is a big deal and I just don't realize it & actually it could be the firmware thing the guy above mentioned could be a good reason for it but something I read tells me otherwise, just can't remember it at the moment.
Lastly just incase pball sees this again, for the lols that is.
1. No of course not, I did hear something about a Bandroid 2014 though. Heard it bans all the sarcastic insulting comments to OP's on the internet.
2. No.
3. Might try that if it's ever serious enough to require it. <3.
4. Because I was quite sure it would reinstall the google services, and if you install the correct version for your ROM/OS version I'm pretty sure it shouldn't cause any problems, could be wrong though. Anyways it was not the cause of my GServices crashing anyways.
5. Thanks for the info, I'll consider that next time.
6. Clean as in without wiping /data, yes. With wiping data, no.
7. Yes & the problem went away but I restored to my 12 day old backup of Viper anyways and it's solved now.
52998. Hello!
Anyways problem solved!
/case /closed
You can easily store text on cloud well factory reset. Just FYI. But glad your all set.
There is no correct version of gapps for the ViperOne ROMS. I usually only save the last two nandroid backups as long as everything seems to be working ok. If you want to save the older ones, well . . . . but you don't have the space on your pc. And sdcards are getting real cheap
S1L3nTShaDoWz said:
Lastly just incase pball sees this again, for the lols that is.
1. No of course not, I did hear something about a Bandroid 2014 though. Heard it bans all the sarcastic insulting comments to OP's on the internet.
2. No.
3. Might try that if it's ever serious enough to require it. <3.
4. Because I was quite sure it would reinstall the google services, and if you install the correct version for your ROM/OS version I'm pretty sure it shouldn't cause any problems, could be wrong though. Anyways it was not the cause of my GServices crashing anyways.
5. Thanks for the info, I'll consider that next time.
6. Clean as in without wiping /data, yes. With wiping data, no.
7. Yes & the problem went away but I restored to my 12 day old backup of Viper anyways and it's solved now.
52998. Hello!
Anyways problem solved!
/case /closed
Click to expand...
Click to collapse
Hello, I am back. Just a suggestion in a civil manner. Could you try backing all of your apps up. Make a backup of what you have now, just incase something happens again.. Then, go in and flash the new viper 2.0 or 2.0.1 either or is fine. Please do a clean install. Meaning wipe your data partition. Not your internal SD card not external. In viper I know it gives the option to do a clean install. Please consider actually trying it and seeing the outcome. What's the worst it could do? As for the GAPPS. HTC uses there own personal GAPPS, so it might clash with let's say banks minimal GAPPS. It's not containing the same files and they may just clash with each other. Causing more crashes and instability than before. Somewhat make sense? Lastly, I wasn't trying to be "snarky" or "sarcastic". I may have came across that way, because the way the original post is stated sounds very problematic to some. I went through and listed all the things that could have gone wrong or been happening. Because a lot of ROM threads do mention clean installs with updates or new ROMs. I've seen lots of threads. "If you're having problems please wipe you data, cache, and dalvik cache partition or clean install the ROM again.
Tl;Dr actually try a clean install and check the md5 for matching numbers. A clean install can solve a lot of issues.
Sent From My HTC One M8 Running Insert Coin. S-OFF.
pball52998 said:
Hello, I am back. Just a suggestion in a civil manner. Could you try backing all of your apps up. Make a backup of what you have now, just incase something happens again.. Then, go in and flash the new viper 2.0 or 2.0.1 either or is fine. Please do a clean install. Meaning wipe your data partition. Not your internal SD card not external. In viper I know it gives the option to do a clean install. Please consider actually trying it and seeing the outcome. What's the worst it could do? As for the GAPPS. HTC uses there own personal GAPPS, so it might clash with let's say banks minimal GAPPS. It's not containing the same files and they may just clash with each other. Causing more crashes and instability than before. Somewhat make sense? Lastly, I wasn't trying to be "snarky" or "sarcastic". I may have came across that way, because the way the original post is stated sounds very problematic to some. I went through and listed all the things that could have gone wrong or been happening. Because a lot of ROM threads do mention clean installs with updates or new ROMs. I've seen lots of threads. "If you're having problems please wipe you data, cache, and dalvik cache partition or clean install the ROM again.
Tl;Dr actually try a clean install and check the md5 for matching numbers. A clean install can solve a lot of issues.
Sent From My HTC One M8 Running Insert Coin. S-OFF.
Click to expand...
Click to collapse
Yes I'll back up the apps tomorrow, I used to do that with titanium and make a flashable zip but It rarely occurs to me to use Titanium anymore. Matter of fact 90% of the time I don't even realize I have it or it even exists. Last time I did it I did the wrong option which probably turned me off from it anyways soo I'll just have to pay attention this time.
I'll install 2.0 another day, too traumatized after my last experience to mess with it again LOL.
On the GAPPS topic yes it makes sense, I was unaware HTC had their own as it doesn't really say anywhere that they do or at least I haven't found anything stating such yet up until your response but yes it makes 100% sense.
& yeah I understand, I was quite frustrated and angry at the time and probably should've waited til I calmed down before originally posting this thread. Anyways my bad for even calling you out on that, I didn't originally plan to respond due to my natural urge to wanna retaliate when I feel I've been insulted, mocked or other words "attacked". Not literally attacked but you get what I'm saying, felt like I needed/wanted to be on the defensive. If that even makes sense, oh well.
Lastly, as to the "If you're having problems please wipe you data, cache, and dalvik cache partition or clean install the ROM again." I may have just skimmed over that and maybe just completely ignored the data part in my head. Having read so many I don't really bother to read anything other than the features and some other stuff anymore. I'd say what other stuff but I'm tired and can't think of it at the moment.
Anyways, thanks for trying to help even though my original post sounded like it was made by an idiotic jack***. How frustration & anger makes you change eh? & apologies for responding to what I thought was a "snarky & offensive" reply with attempt to try the same thing. Night!
My viperone 2.0 works just fine on my verizon m8 boot times are really slow but it works a lot smoother and faster with the update. I will deal with long boot times as its woth it to me, no other problems on mine.
Roefastford said:
My viperone 2.0 works just fine on my verizon m8 boot times are really slow but it works a lot smoother and faster with the update. I will deal with long boot times as its woth it to me, no other problems on mine.
Click to expand...
Click to collapse
May I ask if you wiped your /data when you installed it? (clean installed)
S1L3nTShaDoWz said:
May I ask if you wiped your /data when you installed it? (clean installed)
Click to expand...
Click to collapse
No I dirty flashed from 1.8 to 2.0.0 then I dirty flashed from 2.0.0 to 2.0.1 because the ota kept coming back corrupt download so I just flashed the full rom to get from 2.0.0 to 2.0.1
teddyearp said:
There is no correct version of gapps for the ViperOne ROMS. I usually only save the last two nandroid backups as long as everything seems to be working ok. If you want to save the older ones, well . . . . but you don't have the space on your pc. And sdcards are getting real cheap
Click to expand...
Click to collapse
SD cards cheap? Um buy a class 10 scandisk ultra 64g top of the line not cheap by any means it might cost you 70 bucks like mine did but well worth it. Viper ROM needs no gapps its a sense ROM so I'm confused with that.
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)