Latest OTA killed my WiFi. I dont have the receipt anymore and I might be screwed even though I only bought this tablet less than 3 weeks ago. Is there anyway to revert back to an earlier build. I'll do anything. Im not rooted or unlocked. Any help to fix this and I will donate to u I promise.
It looks like they are aware of the issue so I would wait a few days before freaking out. You can always push an update from your pc or SD card if it comes to it. My gf has the k1 and hers just has an update tonight that said it was fixing wifi issues. When did you install this update? What version was it?
Sent from my SHIELD Tablet using Tapatalk
TokedUp said:
Latest OTA killed my WiFi. I dont have the receipt anymore and I might be screwed even though I only bought this tablet less than 3 weeks ago. Is there anyway to revert back to an earlier build. I'll do anything. Im not rooted or unlocked. Any help to fix this and I will donate to u I promise.
Click to expand...
Click to collapse
You should be able to get the receipt reprinted at the store you got it from if you used a credit or debit card. Worse comes to worse I'm pretty sure Nvidia would be able to tell how old the unit is.
Im gonna go back to the store I bought it at tomorrow. I used my debit card so hopefully that will work. Thanks.
I just exchanged my K1 for a new one. Staying on 5.1.1 for a while. **** you Nvidia!
Mods please close
I took the OTA last night and had the WiFi problem. I was able to fix it by re-flashing the staging blob (source) and rebooting.
Incidentally, I switched to Bliss 6 and had the exact same issue, and solved it the exact same way. My guess is that the OTA didn't correctly patch the blob, but after all the work I have done today to try and get myself a working tablet who knows whether that was the root problem or not.
jeffober said:
I took the OTA last night and had the WiFi problem. I was able to fix it by re-flashing the staging blob (source) and rebooting.
Incidentally, I switched to Bliss 6 and had the exact same issue, and solved it the exact same way. My guess is that the OTA didn't correctly patch the blob, but after all the work I have done today to try and get myself a working tablet who knows whether that was the root problem or not.
Click to expand...
Click to collapse
Can I ask how you re-flashed this .img, I have had no wifi for 2 days now and am starting to get impatient waiting for a fix. Any help is appreciated, thanks!
roaming4gnome said:
Can I ask how you re-flashed this .img, I have had no wifi for 2 days now and am starting to get impatient waiting for a fix. Any help is appreciated, thanks!
Click to expand...
Click to collapse
I downloaded the file I linked to above, rebooted the tablet into the bootloader, and flashed it with fastboot (`fastboot flash staging blob.img`). There are plenty of tutorials already explaining how to boot into your bootloader and install adb/fastboot on your computer to accomplish this, so I won't fill up the Internet by duplicating it here.
Thanks! ya I'm familiar with the process, I decided to flash factory .img and back and running now
Bliss v6.0 Shield K1
jeffober said:
I took the OTA last night and had the WiFi problem. I was able to fix it by re-flashing the staging blob (source) and rebooting.
Incidentally, I switched to Bliss 6 and had the exact same issue, and solved it the exact same way. My guess is that the OTA didn't correctly patch the blob, but after all the work I have done today to try and get myself a working tablet who knows whether that was the root problem or not.
Click to expand...
Click to collapse
is it working for K1 tablet or original because my k1 have the same problem
I've had the same problem on my K1. (wifi)
A factory reset (launched by the android menu, not from bootloader) solved the problem.
It's long but it's normal.
Of course I had to set everything back, but my tablet was stock so I lost nothing.
Now it's rooted and everything is fine.
Toked, same issue. Was able to work around issue by turning on one of the options in developer mode. Turn on "use legacy dhcp client". Wifi back. Hopefully a permanent fix soon
Not meaning to necropost here, but turned on my shield after a long while off and had this same issue, changing to "use legacy dhcp client" worked! Thanks!
How to fix wifi
Step 1: Turn the Shield tablet off
Step 2: Remove SD card
Step 3: Turn tablet back on
WiFi should now be working
Step 4: Reinsert SD card.
Related
Got a notification this morning that there was a new update available for KitKat. I do not know what the update is as I postponed it. I am currently running KitKat 4.4.2 Kernel version 3.4.0. The build is D80020c. I am rooted. I have no other information except that it shows that an update is pending but it will not tell me what the update is and I do not know where to find out what it is.
Anyone have any ideas as to what this is? I am concerned because the last time an update rolled out, it soft bricked my rooted phone.
I spoke with tech support at AT&T and they claim that they do not know what it is and suggested that I call LG for an answer.....
NevetsDrassel said:
Got a notification this morning that there was a new update available for KitKat. I do not know what the update is as I postponed it. I am currently running KitKat 4.4.2 Kernel version 3.4.0. The build is D80020c. I am rooted. I have no other information except that it shows that an update is pending but it will not tell me what the update is and I do not know where to find out what it is.
Anyone have any ideas as to what this is? I am concerned because the last time an update rolled out, it soft bricked my rooted phone.
I spoke with tech support at AT&T and they claim that they do not know what it is and suggested that I call LG for an answer.....
Click to expand...
Click to collapse
Don't install it, it jacked up my phone. I was running the rooted mixed partition D80020c and I can't boot or get into download mode now. All I get it a constant reboot back to recovery. Cannot install another ROM, cannot restore a backup. My daughter was playing with my phone and pushed to continue with the install and now I'm trying to unscrew it.
Jank4AU said:
Don't install it, it jacked up my phone. I was running the rooted mixed partition D80020c and I can't boot or get into download mode now. All I get it a constant reboot back to recovery. Cannot install another ROM, cannot restore a backup. My daughter was playing with my phone and pushed to continue with the install and now I'm trying to unscrew it.
Click to expand...
Click to collapse
Is there any way to force a not install or deny it? The only option I have is to postpone the install and after 4 hours, it will run again and continue to run every 4 hours unless I find a way to break the cycle. How do I force a no install option?
That is what happened to me last time with the "q" update. I postponed the install (no option to not take it) and it installed itself after 4 hours when I left my phone on one night. I woke up to a bricked phone.....
NevetsDrassel said:
Is there any way to force a not install or deny it? The only option I have is to postpone the install and after 4 hours, it will run again and continue to run every 4 hours unless I find a way to break the cycle. How do I force a no install option?
That is what happened to me last time with the "q" update. I postponed the install (no option to not take it) and it installed itself after 4 hours when I left my phone on one night. I woke up to a bricked phone.....
Click to expand...
Click to collapse
I don't know how to permanently disable the update, but I'm sure there's a way. As info, I was able to easily fix my phone with the help of this thread posted by @thecubed: http://forum.xda-developers.com/showthread.php?t=2451696. I didn't read it all, but this might be what disables the update.
I'm not rooted. I took the latest update and all is fine. It's google+ fixes and Google wallet support. It actually let me set up tap & pay! I'll have to go somewhere to try it out.
Sent from my LG-D800 using Tapatalk
I got the notification too but figured that it would probably screw things up since I'm rooted and running TWRP so I did a little searching and came across this, http://forum.xda-developers.com/showpost.php?p=50454408&postcount=3 . It's been a few hours since I changed the setting and haven't seen the update notification again although AT&T pushed the update into CACHE/FOTA sometime this morning.
Well scratch that, the notification just came back. I'll try freezing it now.
Well if rooted just use TB to freeze software update. I am also running a mixed partition D80020c. I am on Straight Talk AT&T. Before rooting I tried taking the official OTA of KitKat but for some reason you can't enter an APN type so I couldn't get or send MMS. So I flashed back to the D firmware,rooted,added custom recovery,entered the APN type and then flashed the modified C firmware. You could also use Root Freezer instead of Titanium Backup to freeze
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
dwcosby said:
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
Click to expand...
Click to collapse
there have been quite a few people with this same issue. i havent seen any direct fix.
if you are locked, i would suggest you wait it out, or wait for the sbf file to get leaked. there is a way to sideload it, but its risky being locked and no sbf to save you if a problem comes up.
if you are unlocked, there are directions in the General forum to sideload the ota. there is no risk if you are unlocked.
if you are locked, the only thing i would suggest to try is re-flashing the stock 9.30.1 with rsd and see if it will pull the update afterwards. there is no guarantee this will work, but your phone will be 100% clean stock after the flash and give you the best chance to grab the ota if available.
dwcosby said:
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
Click to expand...
Click to collapse
Did you download it and then said to apply it later? If so, are you rooted? If so, hook up your phone to your PC and adb shell into it. Type "su" and hit enter to go into superuser mode.
Navigate to the /cache directory and you should see the OTA .zip file sitting in there. Copy it to your external SD card and then you can load it manually via the recovery.
If you're not rooted, then you won't be able to navigate into the /cache directory. Or, if you didn't have it download when you got the notice (or couldn't download it), then it won't be there.
More update issues
My wife & son both have the HD. My wife checked for the update this morning, said it was ready and proceeded to download. Update did as it was supposed to and when it was done, she had KitKat and that's when things went a bit wonky.
If she has Bluetooth turned on, WiFi connection drops after a few minutes. She googled possible workarounds and none really worked. As long as she is not using BT, WiFi stays up
Has anyone else seen this behavior? She refuses to let me root it and install a custom ROM as I have done on my Samsung GS4 from VZW.
In the mean time, we've told our son not to take the update until
we know more about a possible fix.
zeb carter said:
My wife & son both have the HD. My wife checked for the update this morning, said it was ready and proceeded to download. Update did as it was supposed to and when it was done, she had KitKat and that's when things went a bit wonky.
If she has Bluetooth turned on, WiFi connection drops after a few minutes. She googled possible workarounds and none really worked. As long as she is not using BT, WiFi stays up
Has anyone else seen this behavior? She refuses to let me root it and install a custom ROM as I have done on my Samsung GS4 from VZW.
In the mean time, we've told our son not to take the update until
we know more about a possible fix.
Click to expand...
Click to collapse
Fix was just posted recently. do a factory reset. It sucks, but its the only option.
Factory REst doesn't solve 4.4.2 WIFI issue on Razor MAxx HD
TXKSSnapper said:
Fix was just posted recently. do a factory reset. It sucks, but its the only option.
Click to expand...
Click to collapse
Android V 4.1.2 worked flawlessly since Nov 1023 upgrade. Decided to upgrade to KitKat via OTH. Had WIFI connection issues right away ( inability to obtain IP or lost connection, etc.) This happened with Bluetooth ON or OFF, no difference. The Signal strength was much lower than when on the previous android version and subsequent indicated connection speed was at least 1/2 of what I was getting previously.
Worked with Verizon and Motorola tech support personnel and did multiple factory resets with no improvement.
Since I wanted a factory solution and had insurance on the phone, I ordered a replacement phone. Thankfully, the new phone had 4.1.2 and worked perfectly. WIFI issues are gone.
Conclusion, KitKat is not ready for prime time yet. WIFI bug needs to be worked out before I will upgrade again.
egutwillig said:
Android V 4.1.2 worked flawlessly since Nov 1023 upgrade. Decided to upgrade to KitKat via OTH. Had WIFI connection issues right away ( inability to obtain IP or lost connection, etc.) This happened with Bluetooth ON or OFF, no difference. The Signal strength was much lower than when on the previous android version and subsequent indicated connection speed was at least 1/2 of what I was getting previously.
Worked with Verizon and Motorola tech support personnel and did multiple factory resets with no improvement.
Since I wanted a factory solution and had insurance on the phone, I ordered a replacement phone. Thankfully, the new phone had 4.1.2 and worked perfectly. WIFI issues are gone.
Conclusion, KitKat is not ready for prime time yet. WIFI bug needs to be worked out before I will upgrade again.
Click to expand...
Click to collapse
That's a shame because for me, the FDR fixed the Wifi/Blue-tooth issue as it did for many others. Might have been a hardware issue (faulty radio, etc).
I'm completely overwhelmed with this Shield at the moment. Can't even think straight, because it's frustrating me so much. I rooted it and unlocked the bootloader. Now, I tried to update to 99, but it won't let me. So, finally, I decided to change it back to stock. After several attempts at this, now when it loads it just sits at a black screen. Before I got it to work, but it wouldn't check for updates and oddly enough the Play Store was acting weird (downloading slow, operating slow). Not sure if that's relevant, but I get 1.8 MB/s download speed, so I know it's not me. Everything else downloads just fine.
I'm using this thing called Shield Ram which includes adb, cwm recovery, fastboot, and the likes.
***Update***
While typing this, I was able to get the Shield back up after trying to flash the stock rom, but I still have the issue where I can't update.
I go to About Shield/System updates/ and it says "Your system is up to date. Last checked for update at 3:46PM." With a Check now button that doesn't work.
I know that there's update 99 out, but it's on 68 refusing to update or even check for it. I fear that rooting and unlocking it screwed everything up!
Any help would be much appreciated.
Screwed Shield Up! (Solved - I think)
So, just in case anyone is having the same problems as me. I followed this thread to a T and so far it seems to be working. I didn't install the root, though, because it seems like that is what got me in trouble in the first place. Not sure if that was bad or if now it's not rooted and that's the end of it. Hopefully I can just update normally, but if all else fails, then I'll have to reflash or reroot. Again, hopefully it doesn't come down to that.
:good:
[Firmware] Nvidia Root-Friendly Updates [No Wipe]
How do you get root after the latest patch? The one shown in here not working for me currently. :\
Hello I am still dealing with a weird problem that I posted on this forum over a year ago that was never resolved. Basically my tablet is stuck running Android version 4.1.1 (Build JRO03C.US_epad-10.4.4.25-20121228) because if I upgrade to any new versions (whether I do it as OTA or via micro USB) my wifi card stops functioning (it does not see any networks). Anyways I even went so far as to RMA it and Asus said they fixed it, shipped it back to me, but in reality all they did was roll me back to 4.1.1, saw the wifi was working and shipped it back to me saying they "fixed" it. Well of course the second I got it back I installed the OTA and wifi broke again... So I just rolled back to 4.1.1 and said screw it, I just won't update it anymore. Well this week I figured I'd try installing the latest OTA and hoped that this version would not kill my wifi, unfortunately the same exact issue has occurred and thus I have once again rolled back to v4.1.1 and my wifi works perfectly...
TLDR; Anyways apologize for the rant/story but basically I am stuck with using version 4.1.1 of Android and am considering flashing a custom rom to try and resolve some issues I am having with the stock rom's wifi, however the official bootloader unlock tools only say they work on version 4.0 (ICS) or version 4.2 (JB). I'm stuck on v4.1.1 so which tool should I use (or am I out of luck)? Thanks
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
berndblb said:
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
Click to expand...
Click to collapse
Thanks appreciate the reply - I just wasn't sure if using the wrong unlocker could brick my device... I'll give 8 a try first then 7 if necessary. The ironic part is that it requires a network connection to complete the unlock operation (I guess so Asus can cross your S/N forever off of their list of devices under warranty).
I agree that this is a strange problem as I have not seen anyone else report it. Basically I tried resolving this about 13 months ago with the help of this board and as mentioned I finally had to RMA it, but ASUS just rolled the version back instead of fixing anything and at that point I just wanted to enjoy using my tablet more than I wanted to fight with ASUS's customer service reps who effed up the first RMA job (the language barrier was also apparent in my interactions with them)...
Since over a year has gone by since the last time I tried an OTA, I hoped that the latest update would not have the same issues but alas, I'm not that fortunate.
As far as what I've tried - I have tried connecting to different networks and changing router channels and checking for interference, but the thing is, I'm quite certain the problem is with the tablet. When I first had the problem I lived in an apt building where I could 'see' 10+ wifi networks at any given time on all different channels with different routers/security settings etc. As soon as I applied the OTA the tablet could no longer 'see' any of them (even as I sat with my laptop/phone connected to wifi right next to it). I now live in a house (and have a different ISP, and a different router) and tablet works perfectly when on version 4.1.1. I don't have as many wifi networks visible from my house, but can still see a few of my neighbor's wifi networks both on the tablet (v4.1.1) and on other devices. But the second that I upgrade, all of them disappear from the tablet's view (but continue to be visible/work on other devices). I have turned wifi on/off, turned airplane mode on/off, tried connecting via wifi direct, rebooted, cold booted, booted into recovery, factory reset all data, etc. but nothing works because the tablet cannot see any wifi networks. And the second that I rollback to version 4.1.1 the wifi works perfectly... I have upgraded and rolled back probably at least 6 times and it is always the same result.
I do also get another weird side affect when I upgrade - the tablet refuses to turn off when I'm on any version higher than 4.1.1. So if I press "Shut Down", the tablet displays "shutting down" and the screen goes black and becomes non-responsive (as do the buttons, just as you would expect when turning off), but it does NOT actually shut down because if I come back 30 mins, an hour, 2 hours later I can feel it running very hot. The only way to truly shut it down is to let the battery drain...
So maybe a better question on my part would have been, do you think installing a custom ROM will even help resolve this issue? Or should I continue using 4.1.1 and not risk making the situation worse with custom ROMS?
WiFi problems are often kernel related..... Did you always take the update OTA?
Did you ever try to flash the latest firmware version manually? OTA updates do go wrong sometimes....
Although repeatedly???? It's weird. Maybe the server your tablet pulled the OTA from hosts a bad copy????
If you do not want to unlock, manually flashing the firmware would be one thing to try. OTA's patch the existing system, replace old files with new ones where necessary. Manually flashing the firmware replaces everything - a totally new installation of everything: bootloader, recovery, kernel, system and data.
But you cannot make it worse by flashing a custom rom. You unlock, flash a custom recovery (which does not change anything else on your system), then you make a nandroid (backup) of your current 4.1.1 system before you flash a rom. So you would always be able to go back to where you are now. On a custom rom you could even try out different kernels, which often are the root cause of wifi problems..
The thing is: If you want to flash a current custom rom like CROMi-X, based on Asus JB 4.2.2, or CROMBi-KK/CM11 which are KK roms, you always have to update your bootloader first. Your .25 bootloader is too old for any current rom.
You can easily do it once you have a custom recovery installed, but even easier would be to update to the latest Asus firmware 10.6.1.14.10 (after unlocking), then flash the custom recovery (TWRP 2.8.1.0), then flash a rom of your choosing.
Downside of this route would be you wouldn't have that 4.1.1 nandroid I mentioned earlier.....
Nahhh - thinking about it, I would recommend you go this route:
Unlock,
flash an older version of TWRP compatible with your current bootloader (TWRP 2.6.1.0 is ok)
make a nandroid of your current system
do a full wipe of cache, Dalvik and data in recovery
flash the 10.6.1.14.10 bootloader in recovery (I can talk you through it)
flash TWRP 2.8.1.0
flash a rom of your choice
Check out my guide, link in my signature, and let me know if you have questions
Thanks - I was able to successfully unlock my device with v7 of the unlock tool (v8 wouldn't even install). Thanks too for the advice on how to flash a custom rom safely. I've never flashed a custom rom before (have rooted a different android device before tho), so I appreciate any help.
I downloaded the blob file for TWRP 2.6.1.0 from here (techerrata.com/browse/twrp2/tf700t), but not sure how to proceed next, (also I don't see a link in your signature to your guide, but I am running a bunch of script blocking addins so maybe that's why) seems like all the guides I am finding say I need to get a copy of a fastboot program (but don't provide links), where can I find that? Again, I appreciate the help.
Sorry, my bad, I don't have a signature on XDA - wrong forum. LOL
My thread is here: http://forum.xda-developers.com/showthread.php?t=2688891
Ask any questions you may have in that thread, but it should cover your questions - I hope
Just wondering if anyone had a fix or explanation for my situation. I Received an update on the Blu Vivo 5R this Friday, Android 7.0. Then in the process today of unlocking the bootloader and flashing twrp, it got screwed up. so I downloaded the stock rom and flashed it, no biggie. fixed the boot freeze issue. but now I'm back to 6.0 because that was the most up-to-date stock rom. I tried checking for updates, supposedly I'm up to date. I even called Blu support to see if they could push it to my IMEI or something with no luck. they said they release it in batches and the software team deals with that, anyone know a way I could resolve this
You can try manually setting the date ahead a few days and reboot, sometimes that will bring an update.
Char_G said:
You can try manually setting the date ahead a few days and reboot, sometimes that will bring an update.
Click to expand...
Click to collapse
Didn't do anything, thanks for the quick response though.