Related
I was happily running along with my GT2 10.1 5113 using CM10, updating nightlies, all is well. Then I put the CM 10.1 unofficial, that went well, was using it and put the 12/09 version on, that went well also. However I decided I didn't like it and wanted to go back to CM10. I had a back up that I made in CWM with the 12/08 nightly and had begun restoring it when an error came up stopping the restore, only said file error restore can't continue. OK, that kinda blows chunks cause I know my rom just got hammered. Tried to restart, boot loop. Got back into recovery re flashed the CM 10.1, trying to save my data, bootloop. Got back in recovery and wiped data re flashed, bootloop. On an act of desparation I flashed the 12/08 nightly and, viola she lit up and booted to the setup screen.
Set it all back up and updated to the next nightly, 12/10 and I'll be danged, bootloop. Went back to recovery re-flashed the 12/08 nightly and all went well. No data loss just worked fine.
Bottom line I can't get anything but the 12/08 nightly to boot up. I even flashed stock with Odin, that bootlooped too! So I'm stumped.
It boots into the 12/08 nightly just fine and that's it.
I know this is wordy, but I wanted to make a thorough explanation. I feel this is related to the CWM error, but I have no idea where to go from here.
Anybody got a suggestion? All help is greatly appreciated.
I think cm10 installs jelly bean on your system. and switching back to an older version will cause the bootloop. that's what i believed happened to me when I installed cm10 by mistake instead of cm9 which is what i wanted. it took me several tries with odin and the stock rom to be able to go back.
I think the key is when you have cm10 installed then you need to enable the "usb debugging" in the developers section. that is probably what is stopping you from switching back to an earlier version or a new version or the stock rom using odin.
anyway that's how I was able to switch back to stock.
I think the reason you can´t restore CM10 is the fact that Android 4.2 introduces muti-users management. Thus, the system do not store in /sdcard/ any longer, but in /sdcard/0/ (for the first user). Since you still have a 4.1 recovery version, it doesn´t find the backups files any more. A solution is to move your sdcard data from /sdcard/0/ to /sdcard/ before restoring your backup.
As for CM10, the 12/09 and 12/10 nightlies don´t boot, due to kernel changes. These changes were reverted in 12/11, so this one should boot.
Einril said:
As for CM10, the 12/09 and 12/10 nightlies don´t boot, due to kernel changes. These changes were reverted in 12/11, so this one should boot.
Click to expand...
Click to collapse
Bingo! That worked, 12/11 worked. I had no idea that was happening. I made all the file changes actually because I wound up with sdcard/0/0/0 from all the flashing back and forth, that was funny. All is normal now thanks!
Sent from my GT-P5110 using xda premium
I recently bought my girlfriend a galaxy s II skyrocket. I own one myself. I updated my phone successfully and easily to jellybean through the official CM10. I am well aware of the different methods to install different custom roms to your phone. I received my girlfriend's phone with stock gingerbread. I proceeded to install the stock ice cream sandwich update to the phone through Odin. It was successful. I also installed ClockWorkMod recovery into her phone, the exact same one I had. I continued to attempt to install the same rom that I had on my phone, to my girlfriends phone, CM10. CWM said it was a successful installation after the careful 3x: Factory reset, Cache, Dalvik Cache. Upon rebooting of the phone however, the phone would fail to successfully turn on. It would stay in boot loop mode forever. One time I even left it for an hour and there it was, the boot screen I so dreadfully began to hate. I gave up on CM10, so i began to look for other prospects of a rom. I discovered slim bean. I installed it into my original phone to test it and found it to be of great quality. After I followed the exact same steps I followed to install slim bean to my original phone, to my girlfriends phone, the same result came about; boot loop. After about 20 tries, seriously, I tried to find yet another prospect of a rom. I also discovered another slimmer version of jelly bean for the Skyrocket. Even after the careful following of the steps, I encountered the same result; boot loop. I am beyond frustrated at this point at the fact that I am holding two phones exactly the same, yet when I attempt to install the rom, it only works on one of them. They are both Samsung Galaxy S II Skyrockets model numbers 1727. Both based off of At&t in the United States. One is white while the other one is black. If it makes any bit of a difference the phone I am having trouble with is white. I need help. I've tried everything with no success. I am trying to update this phone to jellybean but it does not seem to accept it, and I have no idea why
Re: [Q] Stuck on boot loop after several different jb roms
TLDR condense give important details that's it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
TLDR condense give important details that's it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Sorry, I am not yet familiar with all the terms. It seems like jargon to me at times lol. TLDR Condense?
Re: [Q] Stuck on boot loop after several different jb roms
Nobody knows what version of cwm you're on.
Nobody knows where you're dl'ing cm10 from.
Quit wiping 3x you only need to do it once.
Don't write novels.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Tldr means to long didn't read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Nobody knows what version of cwm you're on.
Nobody knows where you're dl'ing cm10 from.
Quit wiping 3x you only need to do it once.
Don't write novels.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Tldr means to long didn't read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I've tried installing Official CM10.1 (from XDA) with boot loop result. I've tried installing unofficial 4.2.2 slimbean (from XDA) with boot loop result. I've tried installing Skyjellybean 4.1.2 update 11.4 (from XDA) with boot loop result, and finally I've tried installing Superlite CM10 JB 4.1.2 v8.0 (from XDA) with boot loop result as well. I am currently on stock Ice cream sandwich installed through Odin (links and all found from XDA)
Agree with mtdew.
Keep it as short as possible and be specific.
Get CM10 (not CM10.1 as it's still unstable) from http://get.cm/?device=skyrocket .
Also try latest CWM http://forum.xda-developers.com/showthread.php?t=1777970 .
lingowistico said:
Agree with mtdew.
Keep it as short as possible and be specific.
Get CM10 (not CM10.1 as it's still unstable) from http://get.cm/?device=skyrocket .
Also try latest CWM http://forum.xda-developers.com/showthread.php?t=1777970 .
Click to expand...
Click to collapse
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
s3rgioru3las said:
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
Click to expand...
Click to collapse
That is good news, i'm glad it worked out for you. Good luck. :good:
Help
s3rgioru3las said:
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
Click to expand...
Click to collapse
I too Have a Bad Recovery . Every time i try to install ANY jellybean rom i get stuck in boot loop . I Tried different recovery's and different rom's and stock jellybean and no success . But any ics or gingerbread installs normally . I have a epic 4g touch galaxy 2 and it's rooted . Any new idea's what it could be or how to fix it ? I feel i'm the only person with this problem since i cant find anyone else with the same situation . Your the closets to my problem
Cisco408ca said:
I too Have a Bad Recovery . Every time i try to install ANY jellybean rom i get stuck in boot loop . I Tried different recovery's and different rom's and stock jellybean and no success . But any ics or gingerbread installs normally . I have a epic 4g touch galaxy 2 and it's rooted . Any new idea's what it could be or how to fix it ? I feel i'm the only person with this problem since i cant find anyone else with the same situation . Your the closets to my problem
Click to expand...
Click to collapse
Use the latest recovery in your forum
Sent from my HTC One using Tapatalk 4
I've been using CM10.1 on this phone pretty much since it's been available and updating nightlies about once a week usually. Typically I use Ktoonsez kernel and also update this regularly. Also I am on the MF1 firmware. So, I'm pretty comfortable with the update process and have done it many times.
The other day I attempted to update to CM10.1 7/8 nightly while also installing a kernel I've never tried before called 'Sultan-kernel-Venturi-r5-USA'. Also completing the update process I rebooted and the phone would not move past the CM loading animation splash screen. After about 10 minutes of this I pulled the battery and rebooted, hoping it was just a hiccup but the same thing happened. After dirty installing various CM10.1 nightly and release versions with various combos of no custom kernel and the KT kernel but nothing would fix the boot issue.
I then attempted to wipe and ended up eventually wiping everything on the phone except the external SD card. Still, I could not get the phone to move past the CM splash screen. I then tried a few other AOSP ROMs with the same issue presenting.
Eventually I installed a TW based ROM and was able to get the phone to boot and and able to at least use my phone now. I've tried a couple time since to do a nandroid backup then try installing CM10.1 again and still nothing changes. I can restore the backup and the TW ROM works fine again.
Any ideas on what could have happened to cause this or anything else I can try to get AOSP ROMs working on my phone again?
I would say Odin back to 4.0.4 stock, do the OTA's, reroot with the one click root in the developer section, and it should work.
Sent from my SCH-I535 using xda app-developers app
I did get this figured out. Somehow my EFS partition was wiped. TW based ROMs would actually boot but displayed a 'Factory Mode' warning on startup. AOSP ROMs would not finish booting at all. After restoring EFS from backup everything started working again.
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
So I'm new to rooting and flashing custom roms on android devices. This also shows that I'm new because I forgot to make a backup of my stock system before moving forward, hence this problem.
So I currently have CM 10.2 flashed on my phone and so far I can't get the wifi to work. My bluetooth works perfectly fine (I've read that if one fails usually the other should too), so I don't know what to do.
At this point I'm sure i'm stuck because I've flashed a few different roms already to see if i can fix it (10.0, 10.1, 10.2, and hacker's aosp 4.4) but the wifi isn't working in either so I stuck to the rom that had the fewest bugs.
What's weird was that it was working when I had 4.4 flashed, but when i found it too buggy and flashed CM 10.2, now it doesn't work.
Anyone else have this problem? I guess I can live with it for a while until maybe I purchase a new phone.
Thanks
di3zelherbert said:
So I'm new to rooting and flashing custom roms on android devices. This also shows that I'm new because I forgot to make a backup of my stock system before moving forward, hence this problem.
So I currently have CM 10.2 flashed on my phone and so far I can't get the wifi to work. My bluetooth works perfectly fine (I've read that if one fails usually the other should too), so I don't know what to do.
At this point I'm sure i'm stuck because I've flashed a few different roms already to see if i can fix it (10.0, 10.1, 10.2, and hacker's aosp 4.4) but the wifi isn't working in either so I stuck to the rom that had the fewest bugs.
What's weird was that it was working when I had 4.4 flashed, but when i found it too buggy and flashed CM 10.2, now it doesn't work.
Anyone else have this problem? I guess I can live with it for a while until maybe I purchase a new phone.
Thanks
Click to expand...
Click to collapse
Did you flash 10.2 directly over 4.4 without wiping system data and both caches?
Sent from my XT926 using Tapatalk
koftheworld said:
Did you flash 10.2 directly over 4.4 without wiping system data and both caches?
Sent from my XT926 using Tapatalk
Click to expand...
Click to collapse
The first time, no. I thought I may have installed 4.4 incorrectly so after installing 10.2 i tried flashing 4.4 again, but I did wipe the caches, system, data and dalvik caches the second time going back after reading in this forum how to flash over a custom rom. But then seeing that the bugs were still there, i wiped again and went back to 10.2 and I've been there for a day now.
Missed Wifi
I'm facing the same trouble , same conditions.
Solved
zirig said:
I'm facing the same trouble , same conditions.
Click to expand...
Click to collapse
This will solve !! http://forum.xda-developers.com/showthread.php?p=47415109&posted=1#post47415109
thanks for xXLuHXx
zirig said:
This will solve !! http://forum.xda-developers.com/showthread.php?p=47415109&posted=1#post47415109
thanks for xXLuHXx
Click to expand...
Click to collapse
That worked! Thank you!