Database Info

[Q] 4 separate ROMS. Gets stuck at Turning wi-fi on, nothing else

I have tried all of the ICS roms, and always gets stuck at the same spot. Wi-fi is turning on.
It worked on the Revolver 4, but I wanted to try another one. Did a super wipe, and bam. Nothing after that..
Any thing I might be able to try?

Nandroid restore, if that won't work nvflash?

you mean use NVflash to do the rom install vs the recovery?

I made a topic about this, check my post (not able to give you a link right now sorry)

I also need help with this. I am trying to come from CM9 cornerstone build back to revolver. I have done a couple restores and I still get no WIFI. Anybody have anymore info on this?

Have a look at this : http://forum.xda-developers.com/showthread.php?t=1530612

You can try this:
- Turn off wifi
- rename the file /data/misc/wifi/wpa_supplicant.conf to wpa_supplicant.old
- reboot
- try wifi again to see if it works
**note
This might cause the tablet to forget any previously saved networks.

I have tried Outpoxs' method in varies combinations with no success also I have tired your method a.mcdear and also with no success. Mine is still stuck on Turing WI-Fi on... The one thing with outpox method there might have been something I was doing wrong.

This is how I fixed my tablet after 15 hours of trying everything. I downloaded the ota rooted full version of ics and performed a full wipe then made sure it booted into that rom with wifi working then proceeded to flash my revolver backup with no problems. Hope that helps.

Similar WiFi issue - still stuck
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger

I've have a rooted TF101 B50 and most ROM's that I have tried seem to fail at this point as well. However, I did notice that when I flashed my first ROM (AOKP) it has the same stock kernel. So I tried another one. This time was Revolution 4. It seemed to work out just fine because I belive it has the stock kernel. Next I moved onto a CM10 Eruoskank ROM. It too had the problem of the AOKP ROM in that after I flashed it, the stock kernel was still present, presumably left over from the Revolution 4 ROM. I am now on Android Revolution HD 3.5.0 and it seems to work fine so I am sticking with it for the time being.
I beleive something in the flashing script of the ROM or the recovery program itself is not flashing the /boot partition properly. I am not a developer nor do I have an in depth knowledge of the inner workings of Android...but this is just a guess. I hope there is a way to flash just a kernel in the /boot partition from these individual ROMs. That would be nice.

If can access recovery then do a full wipe(system, cache and dalvik) and install the ROM again... that should do the trick... you might wanna try some other kernel also... there few kernels for ICS in the forum look for them and flash them via recovery...
Sent from my Transformer TF101 using xda app-developers app

It seems as thought someone else is on the same track as I am.
http://forum.xda-developers.com/showpost.php?p=29447134&postcount=8

rstry this:
take unit out of dock if you use one. restore via cwm if u can, to 3.01 firmware, honeycomb. wipe all cache, data, etc prior to flash.
DO NOT SIGN INTO GOOGLE ACCOUNT.
Turn tablet completely off following boot. Cold boot back on. Grab latest official firmware off Asus website, xx.27
Install via CWM, and again wipe ALL.
Boot into system again, and cold boot back on. Asus should prompt you with 300mB update now, which differs from the official .27,but had same filename...
I found this bug/glitch a few hours ago... Somehow downgrading to HC and back to stock triggers this unknown update...
See if you can reproduce please. I also saved the firmwares to sdcard external.

The various ROMs require a supporting kernel. I would try obtaining the correct kernel for the ROM you want and then flash them both at the same time from recovery.

Resolved - for me
From replies here and other research, it became clear to me that I should reflash my transformer back to stock (NVFLASH down to the metal). Every other ROM would show the stuck WiFi issue or (worse) would get into a boot loop.
This was something of a problem, because my volume up button was broken and I couldn't enter APX mode. I finally managed a workaround for that (see http://forum.xda-developers.com/showthread.php?t=1890236) and then used EasyFlasher to restore the Asus firmware. Now the WiFi works fine and all is well again.
So, as a last resort - scrub and start over.
Cheers!
--Roger
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse

regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
I also have the same issue. Bought the eee pad transformer with a cracked screen; touch screen did not work. I replaced it and everything works great! except for Wi-Fi =\ Any help would be greatly appreciated!

You should really start your own thread. That being said, first thing to try is to back up all your data and wipe it to factory using EasyFlasher. If the problem persists after a stock firmware flash, then it's likely a hardware issue. If it's resolved, then it was a rom/software issue.

regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
Im 99% sure your problem is that you haven't got the right kernel for the rom your using, this is the usual outcome - wifi not working/ turning on. i don't think nandroid backs up the kernel so your basically restoring stock ICS rom with cm9s kernel. Try find the related kernel to rom your currently on. As for your rom failed flashing, you might be using a very old recovery try updating to the newest twrp recovery. Better yet join the dark side and move up to Jelly Bean, makes the tf101 a whole new device.

[Q] TF300 not connecting to wifi

Okay so Im not that new with rooting androids or with using custom roms, so I'm not that much of a noob. The other day I decided since CM9 was in official nightlies I would give it a try. So I backed up my rom which was stock and rooted and I installed CM9 all through CWM recovery. Once in CM9 i notice the tablet wont connect to my phones tethering which is the only way I can get internet on it so I deciced to go back to my backup. But now on my backup the Wifi wont even turn on, anyideas why?

Hello,
I got exactly the same problem. I have installed CWM 5.5.0.4 and I tried CM9 nightly and return to Nandroid BackUp. Then no more wifi..
I tried to flash differents versions of stock kernels, but it was impossible to flash it : "Installation aborded"..
I used fastboot to install a new recovery : TWRP, but same problem : impossible to flash any kernels..
Does someone has the same problem? Or any idea to solve it?
Thank a lot !
Crystalyse

I also had another question...
is there any rom that will connect to Android tethering (ad-hoc)?
I was able to connect on stock rom rooted with cwm recovery but now every rom I tried so far wont connect to it.
Is there a way to work around this issue

I'm having similar problems, check this out:
http://forum.xda-developers.com/showthread.php?t=1438297
Going to try when I get home but other users are reporting this working for them.

KB Smoka said:
I'm having similar problems, check this out:
http://forum.xda-developers.com/showthread.php?t=1438297
Going to try when I get home but other users are reporting this working for them.
Click to expand...
Click to collapse
+1 That's the fix (WPA_Spullicant2) that worked for me. My TF300 just kept saying "Saved" when trying to connect to ad-hoc. Replaced the WPA_Supplicant2 file and all is working well.

It's a known issue with wifi not working on stock rooted nandroid backups. If you go back to stock, you will need to follow the step in this post from Xplod.
http://forum.xda-developers.com/showpost.php?p=26435786&postcount=2

meatrocket said:
+1 That's the fix (WPA_Spullicant2) that worked for me. My TF300 just kept saying "Saved" when trying to connect to ad-hoc. Replaced the WPA_Supplicant2 file and all is working well.
Click to expand...
Click to collapse
Sent from my ASUS Transformer Pad TF300T using XDA
Worked perfect....Thanks again for this.
Inc2.CM7.Condemned.Wireless.Tether.2.0.7

[Q] - Ruined for all other ROMs?

So I have a little bit of a strange issue.
I had flashed the AOKP Milestone 5 on my TF, and although I managed to fix the CWM bootloop, it doesn't appear I'm able to install any other ROM.
Since I've flashed it, any other ROM I attempt to flash either fails to complete it's first boot (watched a few different ones try for hours yesterday) or wifi will not turn on. The wifi issue is also present in my backup from stock.
Perhaps for the ROMs that are booting for me there is a different kernel I may have better luck with? Thoughts, anyone?

frankxanders said:
So I have a little bit of a strange issue.
I had flashed the AOKP Milestone 5 on my TF, and although I managed to fix the CWM bootloop, it doesn't appear I'm able to install any other ROM.
Since I've flashed it, any other ROM I attempt to flash either fails to complete it's first boot (watched a few different ones try for hours yesterday) or wifi will not turn on. The wifi issue is also present in my backup from stock.
Perhaps for the ROMs that are booting for me there is a different kernel I may have better luck with? Thoughts, anyone?
Click to expand...
Click to collapse
What recovery are you using? might pay to try another (Recommended: http://forum.xda-developers.com/showthread.php?t=1759452)

You may want to obtain a kernel compatible with the ROM you want to try and flash both the ROM and kernel at the same time. The wrong kernel could definitely cause both the booting problems and the wifi not turning on.

I think about a kernel problem too, go to your ROM thread and you'll see the best kernel to flash with it...

[Q] Wifi Issues

I would have posted this in the Sensation Android development area, but I don't have sufficient privileges to do so.
I no longer have WiFi.
I am using the 4.1.2 CM Kang, and I originally had WiFi working with that ROM, but it stopped working about a weeks ago, and I can't get it to come back.
If I watch the Wifi on/off toggle, I can see it blink white for a split second then return to grayed out about once every 5-10 seconds.
I've checked the WiFi settings, and the only thing that looks peculiar is that the region code under Advanced says "Europe," but when I try to change that, it just reverts.
I have tried a factory data reset,re-flash of the ROM, and installing newer versions of the ROM with no luck.
Does anyone have any suggestions?

tried this ?

WiFi will not turn on
ganeshp said:
tried this ?
Click to expand...
Click to collapse
I tried to install WiFix Manager, and I followed the directions closely, but WiFi still will not turn on.
The country code always reverts back to Europe in the Advanced WiFi Settings.
I'm on T-Mobile US, running AOKP aokp_pyramid_unofficial_Oct-19-12.zip; a JB ROM; 4.1.2
I previously tried the CM10 Kang for the HTC Sensation, but switched ROMs to make sure that it wasn't issue with the ROM.
To be clear, my problem is not that the WiFi radio never locks to a particular signal, it's that the WiFi radio won't even turn on.
When I go to WiFi settings it just says, "Turning on WiFi...," and never actually turns on.
My best guess was that it had something to do with the WiFi country code, but that's really just a stab in the dark; open to suggestions.
Thanks

bump
Surely, there's someone out there that can help?

kosstheory said:
Surely, there's someone out there that can help?
Click to expand...
Click to collapse
In order of easiest and quickest to longest time it will take to do each one...
Install the latest version of the ROM (10/23) overtop of your existing rom (5 minutes)
If that doesn't work...
Do a full wipe and install a fresh copy of the latest version. (15 minutes, with Nandroid backup)
If that doesn't work...
Format your SD card (save all the contents to your computer first) (40 minutes between copying every to the computer and back to the SD card)
NON ROM RELATED OPTION IF YOU ARE S-OFF
Reinstall your firmware as it's possible something got messed up. You will have to boot to recovery after this and wipe cache and dalvik or you will get bootloops. (5 minutes, but a little more involved)
My guess is that the full wipe and fresh install is the most likely to work the first time.

Skipjacks said:
Reinstall your firmware as it's possible something got messed up. You will have to boot to recovery after this and wipe cache and dalvik or you will get bootloops.
Click to expand...
Click to collapse
is there a sensation specific guide for this procedure?

Still perplexed
How do I know which kernel and radio combination should work best with my ROM. I switched out to AOKP to see if that was the problem, and I believe I'm using the 3.33 Kernel, but I don't know how to check to make sure it installed correctly.

Had the same problem as you but a full wipe and reflash would bring it back. Seems to be a CM10 problem since it happens with Bruce's and Paranoid roms. Try a Sense rom and see if wifi works.

Is OpenSense considered a "Sense ROM?"

http://forum.xda-developers.com/showthread.php?t=1926858
Try that rom, more stable and better performance than all the popular roms.

I had the same problem only option was another room Android_Revolution_HD-Sensation_6.8.0 (this is the rom)

so long, and thanks for all of the fish...
I figured it out.
I bought a Samsung Galaxy S III. WiFi is working again.
Thanks for all of the help!

wifi cm10
I have tried several CM10 roms. It is as you said about the region code. It reverts back to the original and doesnt save it on the settings

Even though editing db file doesn't work. Actually it changes the country code. I guess the ROM changes it during booting. Because while it boots you can see that the wifi is connecting first then goes off. I have tried several roms. DOnno what the problem is. probably JB both on cm10 and aokp

[Q] How to de-brick rooted P5110 that keeps rebooting after startup animation (boot)

As the title says: P5110 keeps rebooting during boot - right after animation stops (before word SAMUNGS starts glowing).
Tablet is rooted and there is CWM 5.5.0.4 installed. Was just fine for almost half a year and all of a sudden this...
I have tried
- wipe data/factory reset
- wipe cache partition
- advanced : wipe Dalvik Cache (whatever that might be?)
I also tried all the "mounts and storage" options and noticed on thing: i can mount all storage mounts (/system, /cache, /data, /efs, /preload, /sdcard) but one - namely /emmc. Does it mean that emmc is broken? What is emmc? Is it important?
I am considering unrooting it and removing CWM. But not sure whether it's even possible and don't dare to try!
Can you tell me anything that might help me debrick this tablet?

Do you have nandroid backup(one that you make with cwm)? If yes go to backup and restore in cwm and hit restore....if not try to reflash rom via cwm or flash stock rom via odin in dowload mode.
emmc is.... http://www.simmtester.com/page/news/showpubnews.asp?num=181

Starojitski said:
As the title says: P5110 keeps rebooting during boot - right after animation stops (before word SAMUNGS starts glowing).
Tablet is rooted and there is CWM 5.5.0.4 installed. Was just fine for almost half a year and all of a sudden this...
I have tried
- wipe data/factory reset
- wipe cache partition
- advanced : wipe Dalvik Cache (whatever that might be?)
I also tried all the "mounts and storage" options and noticed on thing: i can mount all storage mounts (/system, /cache, /data, /efs, /preload, /sdcard) but one - namely /emmc. Does it mean that emmc is broken? What is emmc? Is it important?
I am considering unrooting it and removing CWM. But not sure whether it's even possible and don't dare to try!
Can you tell me anything that might help me debrick this tablet?
Click to expand...
Click to collapse
If you have nandroid backup.. Just restore it.. Or else download a stock firmware and flash it via odin.. gud luck:good:

flash another rom !!

mythi said:
flash another rom !!
Click to expand...
Click to collapse
Sorry to jump on this thread but might be a similar steps the OP has to take.
What if he flashes a new Rom and it still is locked in a strange boot up?
I posted a thread earlier today but either no one has an answer or my thread title was just crappy.
Mine did exactly what his is doing now (just boots the samsung logo and hangs) and now it just boots into recovery everytime you start it.
Flashing an original stock rom didnt fix it.

Flash via Odin any stock ROM then root it and flash whatever you like.
This kind of brick may occur easily if you have flashed uncompatible kernel or tried to restore nandroid backup of another ROM or made by uncompatible CWM recovery version.
Sent from my GT-P5110 using XDA Premium HD app

Solved?
dartd27 said:
Sorry to jump on this thread but might be a similar steps the OP has to take.
What if he flashes a new Rom and it still is locked in a strange boot up?
I posted a thread earlier today but either no one has an answer or my thread title was just crappy.
Mine did exactly what his is doing now (just boots the samsung logo and hangs) and now it just boots into recovery everytime you start it.
Flashing an original stock rom didnt fix it.
Click to expand...
Click to collapse
Normally, it should actually work absolutely fine if you flash a stock ROM via Odin.
Nobody knows what did cause your problems and what did you flash as last. Also, different OS versions use sometimes different partitions. Even CWM recovery is not compatible through all versions, it uses different formatting.
So this way should work to restore stock ROM on your device:
find and download Odin that fits your device (earlier versions are not neccessarily worse ones)
find and download PIT file for your device
find stock ROM for your device consisting 3-files (for PDA, Phone, CSC).... ROMs are usually zipped, so you will get 3 data after extracting
The PIT file will do re-partitions for the case that your formerly installed ROM used different partitions whch are not compatible with the stock ROM.
After that you will have again unrooted stock ROM. So just be careful afterwards whatever you flash and before you do it, make sure that whatever you flash always fits your device (no matter is it whole ROM, kernel or just upgrade).

tetakpatak said:
Normally, it should actually work absolutely fine if you flash a stock ROM via Odin.
Nobody knows what did cause your problems and what did you flash as last. Also, different OS versions use sometimes different partitions. Even CWM recovery is not compatible through all versions, it uses different formatting.
So this way should work to restore stock ROM on your device:
find and download Odin that fits your device (earlier versions are not neccessarily worse ones)
find and download PIT file for your device
find stock ROM for your device consisting 3-files (for PDA, Phone, CSC).... ROMs are usually zipped, so you will get 3 data after extracting
The PIT file will do re-partitions for the case that your formerly installed ROM used different partitions whch are not compatible with the stock ROM.
After that you will have again unrooted stock ROM. So just be careful afterwards whatever you flash and before you do it, make sure that whatever you flash always fits your device (no matter is it whole ROM, kernel or just upgrade).
Click to expand...
Click to collapse
Thank you for the reply. I had posted a link in here that linked to my thread that explained what i had done and used but it didnt show up for some reason? Anyway I used the below roms(in bold). An update was available for JB and we own two tablets both the P5113 and bought at the same time. One tablet updated fine but the other one would download the package but then would keep failing to install it. So i did a factory reset on the device and then that's when the fun began and it started booting strange.
So I first tried flashing the official JB rom using ODin 3.04.
P5113UECLK7 (4.1.1) - Cellular south November 2012 (Official)
and it still did the same thing so then i tried flashing it back to ICS which is the rom that was on there i think. (It was ICS but not sure if that was the exact version number?)
P5113UEBLI1 (4.0.4) - Singapore September 2012 (Official)
Im sure the roms are going on there fine as if im not mistaken ICS has a blue battery charge icon and JB a gold one. I noticed that it went from blue to gold when i first loaded the 4.1.1 on there and then back to blue when i put ICS back on there.
I cant seem to find a PIT file for the P5113. Only for the P5100. Would that work?
I tried it anyway and it didnt work

dartd27 said:
I cant seem to find a PIT file for the P5113. Only for the P5100. Would that work?
Click to expand...
Click to collapse
If I was you, I wouldn't flash it before I am 100% sure it fits the p5113. I own the p5110 and they are indeed very similar, but who knows.... Take care of your Tab, mate.
BTW: why not CM10.1 stable? It works awesome, full wipe/factory reset, install zip through recovery, install recent gapps for CM10.1 (4.2.2) and after boot install Apex launcher and enjoy life
Sent from my amazing i9000 running CM10.1 by pawitp

tetakpatak said:
If I was you, I wouldn't flash it before I am 100% sure it fits the p5113. I own the p5110 and they are indeed very similar, but who knows.... Take care of your Tab, mate.
BTW: why not CM10.1 stable? It works awesome, full wipe/factory reset, install zip through recovery, install recent gapps for CM10.1 (4.2.2) and after boot install Apex launcher and enjoy life
Sent from my amazing i9000 running CM10.1 by pawitp
Click to expand...
Click to collapse
I hear you Its a paper weight right now though so thought id rather try as nothing else is doing the trick.
The tablets are my kids so i preferred to just give them an official stock version. I got put off using custom roms when i used paranoid android on my samsung galaxy 2 and it was real buggy. I just need my devices to work for the basics. I now run stock jelly bean on my GS2 but even that has crappy battery life, lucky for it to make it till 4pm and still be on and thats with moderate use. Couple of phone calls and a few text messages and a tiny bit or browsing. I know what is causing it though as it only starts to lose battery when im not on wi fi. It at least doesnt freeze and stop receiving phone calls altogether like PA did though. I used to miss a ton of work calls because the phone had actually frozen.
I love Apex though. I have Apex pro on my GS2 and its much better then the standard launcher. My daughter has the GS3 and it still does not rotate on the home and app screens which i find annoying.

dartd27 said:
I got put off using custom roms when i used paranoid android on my samsung galaxy 2 and it was real buggy. I just need my devices to work for the basics.
Click to expand...
Click to collapse
I've got your point, mate. :good:
Same with me: I need all the functions to work. The CM10.1 does it really, but my p5110 is wifi-only device so I'm not sure if CM10.1 is same good for your p5113. CM10.2 seems to be smooth and fast, but many apps aren't yet updated for 4.3 so I will wait a while before I flash it again.

I have cm10.1 on my p5113...it runs amazing...the p5113 owners most of the time have to flash the p5110 version because there is nothing different with the tabs besides the ir port..
Sent from my GT-P5110 using xda app-developers app

help me
hello guys,
i have the same problem with my p3100
in my case i cannot connect my tablet to my laptop and it is always looping
i already install the driver, odin, and kies
i already root my tablet
can anyone help me please??

obeye said:
hello guys,
i have the same problem with my p3100
in my case i cannot connect my tablet to my laptop and it is always looping
i already install the driver, odin, and kies
i already root my tablet
can anyone help me please??
Click to expand...
Click to collapse
Can you describe it bit more precised, mate? Don't panic, so far it doesn't sound so bad....

tetakpatak said:
Can you describe it bit more precised, mate? Don't panic, so far it doesn't sound so bad....
Click to expand...
Click to collapse
okay, thanks mate
the problem is my tab always looping whenever I turn it off
I already try wipe at CMW mode,
but it is always restart and nothing happen and its still looping
I already try install the OS, but its aborted
i trying to flash it with Odin, but my laptop cannot read my tab
its been 3 day my tab cannot turn on

obeye said:
okay, thanks mate
the problem is my tab always looping whenever I turn it off
I already try wipe at CMW mode,
but it is always restart and nothing happen and its still looping
I already try install the OS, but its aborted
i trying to flash it with Odin, but my laptop cannot read my tab
its been 3 day my tab cannot turn on
Click to expand...
Click to collapse
Can you reach the download mode? (press 2 buttons at same time: volume down and power button)
OK, yes- you need same Odin version as Tabs 51xx, this is link for Odin 3.07:
http://hotfile.com/dl/161620048/6c6d559/Odin3_v3.07.rar.html
Try pressing the buttons with the charger plugged in, as well as plugged out, that is little trick with the p51xx Tabs

tetakpatak said:
Can you reach the download mode? (press 2 buttons at same time: volume down and power button)
OK, yes- you need same Odin version as Tabs 51xx, this is link for Odin 3.07:
Try pressing the buttons with the charger plugged in, as well as plugged out, that is little trick with the p51xx Tabs
Click to expand...
Click to collapse
Thanks mate!
already done!!
its work!
thank you so much!!

obeye said:
Thanks mate!
I already install ROM JB on my tab
but its still looping in samsung logo,
i read that i should install CWM, but when i install it, it says that "verification failed"
what should i do??
Click to expand...
Click to collapse
Great, I am glad to hear it did charger cable trick help?
Just to make sure: you must be sure to flash a stock ROM first (not JB based custom ROM), after it you will have revived Tab without root. After that normal proceeding: root it, install CWM recovery or custom kernel that fits your ROM (or even whole custom ROM) which already features the CWM recovery.
The stock recovery (3e) checks the signature so of course you can't flash any custom zips. CWM recovery has an option "toggle signature verification" where one can disable signature check. Then you can flash whatever you want, just take care that all you ever flash must be absolutely compatible for your device.
---------- Post added at 03:45 PM ---------- Previous post was at 03:21 PM ----------
obeye said:
Thanks mate!
I already install ROM JB on my tab
but its still looping in samsung logo,
i read that i should install CWM, but when i install it, it says that "verification failed"
what should i do??
Click to expand...
Click to collapse
One more thing mate, look at this video which I've posted on YouTube last January:
http://www.youtube.com/watch?v=0NXBN9Z63TY
It describes how to get rid of the signature verification problem. For the reason that quite many people don't understand english well, I have made a speechless video added by step by step description in the text (video description) so people can just copy the text and paste it into their translators.
If one ROM that you have flashed bootloops on the logo just try another ROM. It happens sometimes. Important is that you should always before flashing another ROM make full wipe: (data/factory reset/cache/dalvik) in your recovery mode.
Did you do it?
Please let me know if you were successful, it should work now! Good luck :fingers-crossed:

It works!
Thanks everyone for your feedback!!!
and my apologies for late response.
I followed the advise to (re)flash stock rom and it worked!
After that i rooted it again, installed another recovery and now have the latest stock rom working perfectly.
For those who get the same problem and the tabled keeps rebooting - just plug it into recharger and keep the on/off button until it turns off. Then you can fully charge it before you attempt to flash rom.
Once again, thanks a lot!
PS. now i am considering installing CM10.1

Starojitski said:
Thanks everyone for your feedback!!!
and my apologies for late response.
I followed the advise to (re)flash stock rom and it worked!
PS. now i am considering installing CM10.1
Click to expand...
Click to collapse
Great! Congratulations
Yes, install CM10.1.1 with gapps for 4.2.2 it works great, all the functions. Just mind that you can not restore nandroid backups made with other kernel, (sometimes also not if done with older CWM recovery version) and also apps backups made by Titanium backups in older systems aren't good idea to restore once you upgrade to CM10x
If you want to return for any reason to your old (current) ROM, do the same procedure like by unbricking