Related
I have searched for the past thirty minutes and have not found a solution so i decided to post in the place where every person seems to know the answer to every question. Anyways, my tp succesfully got set up in ICS and WIFI turned on at first for me to do my original setup, but after rebooting to flash the charger fix and new kernel, my wifi will not connect. I tried a fresh install to make sure the kernel was not the issue, to no avail. When i try and slide the wifi on/off switch to on it just slides back and clicking on the button does nothing. I also tried to add the power widget to the main screen and hit the Wifi button from there, but that was also borked. Any help would be appreciated.
Try setting your router to a specific channel I put mine on 9 and it works now. I was having wifi issues after reboot but after setting the Chanel on my router they went away
If I forget my network, then reboot, then reconnect it seems to work fine. I tried a few other "fixes" I have read about and nothing else seems to work for me at this point...
The problem is not my network, its the fact that i cannot hit the "on" button for wifi
rizdog23 said:
The problem is not my network, its the fact that i cannot hit the "on" button for wifi
Click to expand...
Click to collapse
The OP did make the problem clear!
Looks like a reinstall may be needed.
try fixing permissions from CWM.
If that doesn't work, I suggest to have a look at the logcat entries while trying to switch on and off the Wifi, you may see the reason for the error there.
What version of CM9 is intalled? did you install any special kernel? What channel is your wifi on? (I changed mine from 11 to 1 and it's stayed connected for days now!)
Try a full cache and dalvik cache wipe in ClockworkMod. If that fails, then do a full wipe, re-install and try again from scratch.
This happened to me when I updated to Alpha 0.5. I had to go back and reflash the bricked kernel which i previously installed. I think he made a change to the wifi settings and if I remember correctly he told you how to go back to stock cm9 if you wanted to. But if you installed bricked before that's your problem, reflash it in CWM
bricked kernel uses a different WIFI module, so you need to have both in sync (kernel and driver).
If it worked on first boot, I presume he didn't change the kernel, so something else must be causing his WIFI to fail (fail to start, not fail to connect)
As we mention before, I will go for permissions, cache and get a logcat for the error
Permissions did not work so I wiped and started fresh for the third time....well I guess third time is a charm because I am posting from the TP right now thanks guys.
Hello everyone,
I've been literally 12 hours searching for possible answers on how to repair my Galaxy Note N7000 which from what I've concluded, has a problem that can be easily repaired but I've found nothing but limitations when I have a go at it. It doesn't seem to be bricked as I can still access recovery mode, download mode and it effectively boots, it's only giving me errors.
Here's what happened:
1) I tried rooting it using UnlockRoot PRO. Paid the PRO version, detected the device. Later I find it says the N7000 with 4.1.2 is not compatible so the rooting process was never completed, so I rooted it using Root_SuperSU.0.95.Only-signed and it worked just fine.
2) Everything worked fine, downloaded Andromizer to customize the phone.
3) Changed the DPI size to test it, then went to Developer Options and changed the Animation scales to 0.5 to make it all run faster.
4) Rebooted the device. Once I did, I got nothing but "SystemUI has stopped working" together with "TouchWiz home has stopped working errors".
I checked around the web and so far, what I've found (and tried) is this:
1) There seems to be a bug related to TouchWiz and the Animation Scale option (or perhaps the DPI size option in Andromizer). So I tried to do a wipe data / factory reset through recovery mode.
2) When trying the wipe data / factory reset through recovery mode, I rebooted the phone, only to find the SAME errors after I registered everything.
3) First option that came to mind was to wipe everything and immediatly reinstall the Official JellyBean 4.1.2 firmware (at this point I want to pretty much unroot the device as I didn't know it was going to give me so much trouble). When I tried that, I realized that SUDDENLY, Odin (nor Heimdall) are NOT detecting the phone in download mode. I'm guessing it's because USB Debugging is turned off but, I can't access the phone settings. It's my only logical conclusion, although it should be turned on given I could install PhilZ Custom Recovery later.
4) I search around the web and it says it's a driver problem. So I uninstall everything, run CCleaner, USBDeview to uninstall everything related to the Samsung Galaxy. Reboot. Install drivers again. Reboot. Plug booted phone and let Windows detect the device, installed successfully. Reboot in download mode. Let windows detect the device, installed successfully. Run Odin: DEVICE NOT DETECTED. (It does detect it while it's booted though, only it doesn't work for **** obviously).
I've literally tried everything. I've tried checking for a way to install the firmware via Recovery Mode instead of Download Mode. I've tried checking for a way to remotely access the device and mod the settings from there using ADB, and I get the same problem in ADB, doesn't detect the device.
Also tried to reset settings to normal via PhilZ Custom Recovery which I managed to install later.
Isn't there just a way to reset all settings to normal? Shouldn't a factory reset do this? How can I get SOMETHING to work and try to recover the phone? Any Aroma Recovery Script? Any way to mess with the system folder and modify settings manually via notepad or something since due to the SystemUI / TouchWiz home errors I can't access the phone settings?
I'm barely awake at this point. Can't believe I've stressed myself this much. Please help. This is beyond retarded.
Thank you,
Z
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
I read the post but it seems you have done a lot of things and nothing worked. So what is the situation right now? You can boot as normal but cannot get any icons or settings as sysUI and TW crashes?
Try installing GB ROM then wipe/cache first. If good, root GB ROM then do full wipe. Then test ROM for crashing.
If good then install JB rom and test. Let us know.
unable to enter phone setting ？ then just simply look for a secsetting.apk for ur version then replace it n set the permission rw-r--r--
You could use adb to modify your build.prop
Sent from my SGNote
Makrilli said:
You could use adb to modify your build.prop
Sent from my SGNote
Click to expand...
Click to collapse
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
nice to hear that you had this one fixed
Glad to hear its working now.
n7000 touchwiz home stopped
Zardonic said:
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
Click to expand...
Click to collapse
hi.... im having the same problem as yours. i dont know what to do
lulu2050 said:
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
Click to expand...
Click to collapse
I have tried to upgrade my touchwiz to the new one, but got the danger message, would clearing the cache help?
Sent from my SM-N910C using Tapatalk
Here's the story:
I bought an AT&T HTC One that had an unlocked bootloader and was rooted. I SIM-unlocked it so I could use T-Mobile. Everything worked perfectly fine.
Today I decided I wanted to try out AR HD. I use CWM to flash it, and have a few problems the first few times because of Aroma Installer. Eventually it installs fully, but when I rebooted, something went wrong. It wouldn't boot up. Eventually I had to wipe everything (including the internal storage, which had a backup of mine), and now I'm trying to flash a working rom on this phone.
So now I've tried pretty much everything. The main problem now is that in recovery, when I try to flash a ROM it says it can't mount the the sdcard. I've tried using Nocturnal's method of using the stock recovery to wipe the partitions and everything, but it still gives the the can't mount error.
If anyone could help me I would really appreciate it! Looks like I'm going to have to get a SIM adapter to use with my Galaxy Nexus until I can get this fixed.
aka757 said:
Here's the story:
I bought an AT&T HTC One that had an unlocked bootloader and was rooted. I SIM-unlocked it so I could use T-Mobile. Everything worked perfectly fine.
Today I decided I wanted to try out AR HD. I use CWM to flash it, and have a few problems the first few times because of Aroma Installer. Eventually it installs fully, but when I rebooted, something went wrong. It wouldn't boot up. Eventually I had to wipe everything (including the internal storage, which had a backup of mine), and now I'm trying to flash a working rom on this phone.
So now I've tried pretty much everything. The main problem now is that in recovery, when I try to flash a ROM it says it can't mount the the sdcard. I've tried using Nocturnal's method of using the stock recovery to wipe the partitions and everything, but it still gives the the can't mount error.
If anyone could help me I would really appreciate it! Looks like I'm going to have to get a SIM adapter to use with my Galaxy Nexus until I can get this fixed.
Click to expand...
Click to collapse
Download the All-In-One toolkit from the development section and follow the directions to ADB SIDELOAD a ROM onto your phone.
EDIT: now with a link to the thread: http://forum.xda-developers.com/showthread.php?t=2183942&highlight=all-in-one
Well, I got it to flash a ROM, but now there's a new problem...
I got it to flash the ROM by using CWM to flash a ROM after using Nocturnal's method instead of TWRP.
So now I'm in setup, and am prompted to select a WiFi network. I selected my network, put in the password correctly (it shows connected), and now when I press Next, it transitions forward and then straight back to the WiFi page. Won't let me progress past it.
I think it might have something to do with HTC Sync Manager (I have it installed and running just fine), but I don't know what to do about it.
aka757 said:
Well, I got it to flash a ROM, but now there's a new problem...
I got it to flash the ROM by using CWM to flash a ROM after using Nocturnal's method instead of TWRP.
So now I'm in setup, and am prompted to select a WiFi network. I selected my network, put in the password correctly (it shows connected), and now when I press Next, it transitions forward and then straight back to the WiFi page. Won't let me progress past it.
I think it might have something to do with HTC Sync Manager (I have it installed and running just fine), but I don't know what to do about it.
Click to expand...
Click to collapse
You can skip the wifi setup. Try changing the channel on the router sometimes phones and routers on certain channels don't get along.
I there i have a hp touchpad, an offer. It had already a android version (7 I think), and a problem with wifi, some times didn't connect.
So I decided to upgrade to cm-11-20140625-SNAPSHOT-jcsullins-tenderloin, with rom update-PhilZ_CWM-jcs-dm-tenderloin-20140612 and pa_gapps-stock-4.4.4-20140818-signed, I used the tptoolbox,but the problem with wi-fi remains.
Its a problem of room?
Or of software?
Or hardware?
Can anybody help, please?
thanks in advance :good:
Rs127 said:
I there i have a hp touchpad, an offer. It had already a android version (7 I think), and a problem with wifi, some times didn't connect.
So I decided to upgrade to cm-11-20140625-SNAPSHOT-jcsullins-tenderloin, with rom update-PhilZ_CWM-jcs-dm-tenderloin-20140612 and pa_gapps-stock-4.4.4-20140818-signed, I used the tptoolbox,but the problem with wi-fi remains.
Its a problem of room?
Or of software?
Or hardware?
Can anybody help, please?
thanks in advance :good:
Click to expand...
Click to collapse
Ensure that you are cleanly installing, by factory resetting. Do WiFI problems exist when booted into WebOS?
BuffMcBigHuge said:
Ensure that you are cleanly installing, by factory resetting. Do WiFI problems exist when booted into WebOS?
Click to expand...
Click to collapse
When they gave it to me, it already brought android, and some it works fine some times no.
I did the factory reset, before the installation.
I watched that e can't get a ip address, e get stuck there .
For WebOS I need to download and reinstall?
How to?
thanks
When the tablet starts, you are greeted with a moboot menu. Use the volume rocker to select WebOS. In WebOS, attempt to connect to WiFi there. That should iron-out a hardware issue. I highly doubt it is a hardware issue to being with.
On the latest Android builds, WiFI is certainly not an issue. Use the Toolbox and try flashing again.
BuffMcBigHuge said:
When the tablet starts, you are greeted with a moboot menu. Use the volume rocker to select WebOS. In WebOS, attempt to connect to WiFi there. That should iron-out a hardware issue. I highly doubt it is a hardware issue to being with.
On the latest Android builds, WiFI is certainly not an issue. Use the Toolbox and try flashing again.
Click to expand...
Click to collapse
Moboot then e select WebOs recovery and then a Big usb image appears....
I have no idea how to connect wi-fi there ....
Thanks
Rs127 said:
Moboot then e select WebOs recovery and then a Big usb image appears....
I have no idea how to connect wi-fi there ....
Thanks
Click to expand...
Click to collapse
Hold power and home, until moboot appears again. Then select Boot WebOS (not recovery).
BuffMcBigHuge said:
Hold power and home, until moboot appears again. Then select Boot WebOS (not recovery).
Click to expand...
Click to collapse
That doesn't work. If i do like you say I will do a loop, i only have webosrecorey....
It seems like you do not have webOS installed. Have you tried a newer ROM?
Sent from my TouchPad using XDA Free mobile app
Rs127 said:
That doesn't work. If i do like you say I will do a loop, i only have webosrecorey....
Click to expand...
Click to collapse
It would be wise to keep WebOS on a volume on your Touchpad. You can do this by running WebOS Doctor. Once your tablet returns to complete HP stock, you can then easily use the fantastic Toolbox provided by JScullins to push the latest KitKat builds of Android.
Good luck! And make sure to pass around your thanks on this forum by hitting the "Thanks" button!
BuffMcBigHuge said:
It would be wise to keep WebOS on a volume on your Touchpad. You can do this by running WebOS Doctor. Once your tablet returns to complete HP stock, you can then easily use the fantastic Toolbox provided by JScullins to push the latest KitKat builds of Android.
Good luck! And make sure to pass around your thanks on this forum by hitting the "Thanks" button!
Click to expand...
Click to collapse
Unbelievable, yesterday it start to work, I didn't anything...
but it worry because now i am afraid to disconnect... lolol.
What is the influence of gapp on th system?
I read in the past, that the touchpad WiFi, prefers channel 7 for WiFi. The only way to set that is to hard code that channel on your router!
kulkat said:
I read in the past, that the touchpad WiFi, prefers channel 7 for WiFi. The only way to set that is to hard code that channel on your router!
Click to expand...
Click to collapse
All the router's I use are set to select the best available channel, at home and my local pubs (I set them up) and I don't have any problems connecting apart from the Tablet it's self very occasionally locking up.
Wifi fix for HPTouchpad CM11 (if you get stuck at "Wifi Turning On")
Hi all,
would like to share the issues I've been facing. Previously been using CM9 until one day the wifi stopped working - stuck at "Wi-fi Turning on...". WebOS wifi always worked flawlessly, just not android. Everytime I reflashed using TP Toolbox / ACMEUninstaller2, android Wifi did not work, always shows MAC Address Unavailable (regardless of wifi optimization settings, wifi sleep settings etc, and always stuck at Wi-fi Turning on...).
What I tried that didnt work:
>> TPToolbox with [cm-11-20141002-SNAPSHOT-jcsullins-tenderloin],[update-PhilZ_CWM-jcs-dm-tenderloin-20140317],[gapps-kk-20140105]
>> TPToolbox with [cm-10.1-20131210-SNAPSHOT-VPN-tenderloin], [update-CWM6_tenderloin-20121215], [gapps-jb-20130812-signed]
>> ACMEInstaller5E with [update-cm-10.1-20131210-SNAPSHOT-VPN-tenderloin],[update-CWM6_tenderloin-20121215],[update-gapps-jb4.2.2-20130812-signed]
>> ACMEInstaller5 with [update-cm-9-20130929-NIGHTLY-tenderloin],[update-CWM6_tenderloin-20121215],[update-gapps-ics4.0-20120429-signed]
all cases android wifi was stuck at "Wifi Turning On..." MAC address unavailable but webOS wifi works without issue.
>> installing FXR Wifi fix [FXR WiFi fix and rescue 1.5.0.apk] did not help either, it got stuck at "deleting profiles"
>> going into CWM and wiping Cache/Data + Dalvik Cache, turning on Bluetooth etc did not work either
After multiple tries, here's the solution that works for me for the past few hours. Will update if wifi stops working again:
Using JCSullins TPToolbox [tptoolbox_v40]:
1) Complete Data Reset
2) Create webOS volumes
3) WebOsDoctor to restore WebOS - check wifi works and clear USB data. [webosdoctorp305hstnhwifi]
4) TPToolbox to Install Android [cm-11-20141002-SNAPSHOT-jcsullins-tenderloin],[update-PhilZ_CWM-jcs-dm-tenderloin-20140317], [pa_gapps-stock-4.4.2-20140608-signed]
5) Wifi turns on after booting CM11! MAC address also restored.
6) 1st thing to download - Nandroid online backup
personally, i feel it's the pa_gapps that did the trick. Could be a problem with the KK-signed gapps making the wifi issue appear (suspect its the ath6k failed to initialize problem that others have posted about)
Would like to thank the devs for their work, especially JCSullins for the TPToolbox, it is truly awesome and easy to use.
ashTP88 said:
Hi all,
would like to share the issues I've been facing. Previously been using CM9 until one day the wifi stopped working - stuck at "Wi-fi Turning on...". WebOS wifi always worked flawlessly, just not android. Everytime I reflashed using TP Toolbox / ACMEUninstaller2, android Wifi did not work, always shows MAC Address Unavailable (regardless of wifi optimization settings, wifi sleep settings etc, and always stuck at Wi-fi Turning on...).
What I tried that didnt work:
>> TPToolbox with [cm-11-20141002-SNAPSHOT-jcsullins-tenderloin],[update-PhilZ_CWM-jcs-dm-tenderloin-20140317],[gapps-kk-20140105]
>> TPToolbox with [cm-10.1-20131210-SNAPSHOT-VPN-tenderloin], [update-CWM6_tenderloin-20121215], [gapps-jb-20130812-signed]
>> ACMEInstaller5E with [update-cm-10.1-20131210-SNAPSHOT-VPN-tenderloin],[update-CWM6_tenderloin-20121215],[update-gapps-jb4.2.2-20130812-signed]
>> ACMEInstaller5 with [update-cm-9-20130929-NIGHTLY-tenderloin],[update-CWM6_tenderloin-20121215],[update-gapps-ics4.0-20120429-signed]
all cases android wifi was stuck at "Wifi Turning On..." MAC address unavailable but webOS wifi works without issue.
>> installing FXR Wifi fix [FXR WiFi fix and rescue 1.5.0.apk] did not help either, it got stuck at "deleting profiles"
>> going into CWM and wiping Cache/Data + Dalvik Cache, turning on Bluetooth etc did not work either
After multiple tries, here's the solution that works for me for the past few hours. Will update if wifi stops working again:
Using JCSullins TPToolbox [tptoolbox_v40]:
1) Complete Data Reset
2) Create webOS volumes
3) WebOsDoctor to restore WebOS - check wifi works and clear USB data. [webosdoctorp305hstnhwifi]
4) TPToolbox to Install Android [cm-11-20141002-SNAPSHOT-jcsullins-tenderloin],[update-PhilZ_CWM-jcs-dm-tenderloin-20140317], [pa_gapps-stock-4.4.2-20140608-signed]
5) Wifi turns on after booting CM11! MAC address also restored.
6) 1st thing to download - Nandroid online backup
personally, i feel it's the pa_gapps that did the trick. Could be a problem with the KK-signed gapps making the wifi issue appear (suspect its the ath6k failed to initialize problem that others have posted about)
Would like to thank the devs for their work, especially JCSullins for the TPToolbox, it is truly awesome and easy to use.
Click to expand...
Click to collapse
sadly, still having the "turning on wi-fi" problem on my Touchpad (32GB wifi)
using bluetooth to tether to my phone's wifi network, and also reverse usb tethering via capslock66's android reverse tethering windows
http://forum.xda-developers.com/showthread.php?t=1371345
ashTP88 said:
Hi all,
would like to share the issues I've been facing. Previously been using CM9 until one day the wifi stopped working - stuck at "Wi-fi Turning on...". WebOS wifi always worked flawlessly, just not android. Everytime I reflashed using TP Toolbox / ACMEUninstaller2, android Wifi did not work, always shows MAC Address Unavailable (regardless of wifi optimization settings, wifi sleep settings etc, and always stuck at Wi-fi Turning on...).
What I tried that didnt work:
>> TPToolbox with [cm-11-20141002-SNAPSHOT-jcsullins-tenderloin],[update-PhilZ_CWM-jcs-dm-tenderloin-20140317],[gapps-kk-20140105]
>> TPToolbox with [cm-10.1-20131210-SNAPSHOT-VPN-tenderloin], [update-CWM6_tenderloin-20121215], [gapps-jb-20130812-signed]
>> ACMEInstaller5E with [update-cm-10.1-20131210-SNAPSHOT-VPN-tenderloin],[update-CWM6_tenderloin-20121215],[update-gapps-jb4.2.2-20130812-signed]
>> ACMEInstaller5 with [update-cm-9-20130929-NIGHTLY-tenderloin],[update-CWM6_tenderloin-20121215],[update-gapps-ics4.0-20120429-signed]
all cases android wifi was stuck at "Wifi Turning On..." MAC address unavailable but webOS wifi works without issue.
>> installing FXR Wifi fix [FXR WiFi fix and rescue 1.5.0.apk] did not help either, it got stuck at "deleting profiles"
>> going into CWM and wiping Cache/Data + Dalvik Cache, turning on Bluetooth etc did not work either
After multiple tries, here's the solution that works for me for the past few hours. Will update if wifi stops working again:
Using JCSullins TPToolbox [tptoolbox_v40]:
1) Complete Data Reset
2) Create webOS volumes
3) WebOsDoctor to restore WebOS - check wifi works and clear USB data. [webosdoctorp305hstnhwifi]
4) TPToolbox to Install Android [cm-11-20141002-SNAPSHOT-jcsullins-tenderloin],[update-PhilZ_CWM-jcs-dm-tenderloin-20140317], [pa_gapps-stock-4.4.2-20140608-signed]
5) Wifi turns on after booting CM11! MAC address also restored.
6) 1st thing to download - Nandroid online backup
personally, i feel it's the pa_gapps that did the trick. Could be a problem with the KK-signed gapps making the wifi issue appear (suspect its the ath6k failed to initialize problem that others have posted about)
Would like to thank the devs for their work, especially JCSullins for the TPToolbox, it is truly awesome and easy to use.
Click to expand...
Click to collapse
I have one of my hptp with same problem, cant wait to try it. Thanks.
Sent from my Touchpad using XDA Premium HD app
jerryatherton said:
I have one of my hptp with same problem, cant wait to try it. Thanks.
Sent from my Touchpad using XDA Premium HD app
Click to expand...
Click to collapse
sadly it reverted back to wifi stuck at "turning on".. even the nandroid backup didn't work. let me know how it goes for you, good luck!
i'm currently using Cm11, and bluetooth internet tether to my phone. Have also enabled USB reverse thethering through http://forum.xda-developers.com/showthread.php?t=1371345.
kulkat said:
I read in the past, that the touchpad WiFi, prefers channel 7 for WiFi. The only way to set that is to hard code that channel on your router!
Click to expand...
Click to collapse
How would I hard code it please...
My Tab S2 T719Y has started acting really weird recently. For some reason, it would stall trying to run any ROM that I flash to it.
I'm not certain if it's a LineageOS problem or something is dead in the tablet.
I can flash (the few available still maintained) ROMs offered on the forums for my specific model.
The flash would go fine and everything seems to boot fine. I can install GApps and all. Not a single error mesage.
Then it gets to the new device setup wizard and then it stalls with a black screen. Or in the case of having GApps installed, I can choose a language and press Start at the start of the setup wizard, but I end up in a "Just a min.." bootloop and the tablet is unable to do anything except go back to the language select startup page.
The tablet seems to be running fine beneath. The touch buttons light up and haptic feedback still works. By double tapping the Back button I can get the system UI to show that it's switching between apps, but leads to another blank screen. By pulling down from the top, I can even pull open the notifications bar and quick settings. And I'm able to switch them on an off fine.
I've even tried flashing old ROMs that I know for a fact would run fine, but those end up in the same dead screen.
I've tried wiping and formatting everything in the tablet: Dalvik, System, Data, Storage, Cache ... all to no avail.
What is going on here? I'm reading in some Reddit threads that there might be some data access problem?
How do I resolve this?
Restore the stock ROM using odin and 4-file firmware and check again. If it is OK, go ahead
Thank you! That miraculously revived the tablet back from the dead.
Game-R said:
Thank you! That miraculously revived the tablet back from the dead.
Click to expand...
Click to collapse
Where can I find 4-file firmware.? I tried using Odin to go back to stock 7.0, but the tablet after reboot stops at the Samsung logo. Tried flashing several times and same thing. Help!