Hi all, not sure if this the completely right section but,
Back story: I had a HTC Legend and after an unfortunate weekend, the screen was shattered and thus I had no phone. I scoured ebay and found a no name android (as I wanted dual sim for ease of use) running 2.3.6. Now I had issues rooting my Legend, and so I wasn't keen on it with this phone, but I couldn't resist myself and I tried again with almost next to zero information about my phone.
All I can tell you basically is that it's running 2.3.6, a model number e1101_v73_jbl1ctp_a515 (although scouring of google provided me with chinese websites, and as such I assume that what it's running is similar to that of the Motorola XT91x series? If that helps). I've tried super one click (it hangs at step 7) and I've also tried '2.3.6 root'.
I'm not quite sure what I can do now, any further ideas or help would be appreciated!
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)
Is there somewhere that has a working guide on how to reliably root a brand new Galaxy Tab S2 SM-T810 on 5.1.1?
About a month ago I bought an S2 tablet (9.7", Wifi) and immediately set about rooting it using xda-developers.com. Many years ago I rooted a couple HTC phones because I was having terrible battery performance but never found the need to do the same on my S3 or S5 phones, so I'm a little out of date on the tools and processes. Apparently jumping back in at 5.1.1 was poor timing. I spent half the day using the information in this forum and what else I could piece together to try and get the root to work but eventually got frustrated and stopped. I spent several more hours trying to jump back in at the same place and have been unable to get this to work. I don't have the windows open from all the places I've been, but I've seen a lot of people seeming to report they're having difficulties as well, but that's when the thread just stops and I can't tell if they found some magic to help them out or where I'm struggling.
This website has grown considerably since the last time I was trying to use it as a resource, and I'm either searching for the wrong things or am making mistakes out of frustration. My route has seemed circular, to paraphrase: I don't remember what or how many bootloaders I've tried, my device won't root. I tried using Odin to instead load TWRP, but it also won't install that. I've seen the suggestion to downgrade to 5.0.2 and using a different set of tools, I can work my way to rooted and back to whatever ROMs I want, but then I see conflicting information that I can't just downgrade to 5.0.2, don't see an obvious location of a ROM to even do that with. I don't even know if I'm looking in the right area of the forums.
Hi,
Please check this thread: http://forum.xda-developers.com/tab-s2/general/guide-root-tab-s2-t3205019
If that doesn't help you, you could try asking for help here: http://forum.xda-developers.com/tab-s2/help
Good luck!
Hi new to the forum.
I bought the Xcover 2 in order to get a smartphone capable of surviving in the construction site.
But I realised it could not hold too many apps.
It's screen is allready shattered but at least, thanks to xda, I rock rootetd it and I can now have some usefull apps with me at work.
This week I bought a brand new Leica Disto D510 laser distancemeter with bluetooth pairing to use on site with my ruged (!) smartphone but ... Oh Lord, it DOESN'T PAIR.
It uses Bluetooth Smart 4.0 which can only be used with Android 4.3 or higher!!!! BoloX. The Xcover 2 runs 4.1.2
So THE QUESTION:
1: Is there any way to go around this without upgrading? I don't want to push the poor device too far and since it was designed for 4.1.2 I would like ti leave it with that if possible.
2: If I have to upgrade.. how the heck do you do that? I ,ve spent more that three hours now trying to find the right ROM to flash and I can't!!!!
Thanks in advance to the lady or gentleman, kind enough to post an answer. He will save me the cost of a new phone.
Nagno said:
Hi new to the forum.
I bought the Xcover 2 in order to get a smartphone capable of surviving in the construction site.
But I realised it could not hold too many apps.
It's screen is allready shattered but at least, thanks to xda, I rock rootetd it and I can now have some usefull apps with me at work.
This week I bought a brand new Leica Disto D510 laser distancemeter with bluetooth pairing to use on site with my ruged (!) smartphone but ... Oh Lord, it DOESN'T PAIR.
It uses Bluetooth Smart 4.0 which can only be used with Android 4.3 or higher!!!! BoloX. The Xcover 2 runs 4.1.2
So THE QUESTION:
1: Is there any way to go around this without upgrading? I don't want to push the poor device too far and since it was designed for 4.1.2 I would like ti leave it with that if possible.
2: If I have to upgrade.. how the heck do you do that? I ,ve spent more that three hours now trying to find the right ROM to flash and I can't!!!!
Thanks in advance to the lady or gentleman, kind enough to post an answer. He will save me the cost of a new phone.
Click to expand...
Click to collapse
i dont believe there is any direct way around the bt issue.
your phone shipped with 4.1.2, seems odd that it never got any updates. did you go into settings near the bottom or in about phone, and check for updates?
there is at least one 4.4 rom for your phone that i found with a quick search, so there must be root and custom recovery some where, but its difficult for me to give accurate advice on how to proceed for a device i have no experience with.
ill just throw a couple google search links down here for you to look through if there are no software updates when you check.
if you decide to go the custom route, the first thing you want to do after installing twrp, and before installing a custom rom, is make a backup and save a copy to your pc for safe keeping. some times on these less popular devices it is hard to impossible to find the factory software, so you need a backup of it if anything goes wrong, or you dont like the rom.
https://www.google.com/search?q=Sam...=UTF-8#q=Samsung+GT+S7710+Xcover+2+custom+rom
https://www.google.com/search?q=Sam...ie=UTF-8#q=Samsung+GT+S7710+Xcover+2+recovery