Jump to content


Photo

Guiexception detected: Abnormal situation Code wifi_login_screen_required/ null


Best Answer gsDroid , 04 May 2013 - 10:12 AM

I think I have fixed the problem.  I wiped cache in stock recovery and cleaned up the Dalvik cache in Titanium Backup (root).  I haven't seen the message since.

Go to the full post


  • Please log in to reply
8 replies to this topic

#1 Doddits

Doddits

    n00b

  • Dedicated Supporter
  • Pip
  • 23 posts

Posted 23 April 2013 - 09:12 AM

I have been getting the below error pop up on my screen about 1-2 times daily since updating to JB. Anyone know why? It definitely happens on more than one wifi network and may even happen when not connected to any network. Thanks for the help.


Please Login or Register to see this Hidden Content

 

Please Login or Register to see this Hidden Content

  76.34KB   54 downloads

Sent from my DROID BIONIC using Tapatalk 2



#2 Ashgarden

Ashgarden

    n00b

  • Members
  • Pip
  • 1 posts

Posted 23 April 2013 - 11:25 AM

Same error here... Did a full FXZ using HoB hoping it would fix it... No luck.



#3 Zepplin76

Zepplin76

    n00b

  • Members
  • Pip
  • 2 posts
  • Current Device(s):Droid Bionic

Posted 23 April 2013 - 01:38 PM

Same error here... Did a full FXZ using HoB hoping it would fix it... No luck.

I did full FXZ using RSD, moto-fastboot (both manually and using HoB) cleared anything possible (int and ext sd included) to no avail. I totally feel the pain.



#4 rlewis312010

rlewis312010

    Member

  • Members
  • PipPip
  • 111 posts

Posted 23 April 2013 - 08:41 PM

I did full FXZ using RSD, moto-fastboot (both manually and using HoB) cleared anything possible (int and ext sd included) to no avail. I totally feel the pain.

Wow, I had that error for a while.  I had a bootstrap error (booted, chose nothing, and restrated to find "Encryption failed" message).  I pushed preinstall and system from 246, booted into recovery, and installed my JB update file from SDcard.  I figured it may have bene due to this.  I also had trouble getting root with new root tool (Linux only install). 

 

I went to FXZ but it gave me an error every time.  Sam gave me an XML code that erased all except emc?  Forget the full abbreviation.  I decided I wanted ALL reset so I opened normal xml filed in the fxz zip and edited it (deleted only lines containing "OEM").  FXZ then worked, root worked the first time, and no error message anymore.  I wanted it ALL reset.  If you tried to leave some data, like the emc thing (forget it and too lazy to look), odds are it could be in there.  OR something you installed conflicts with JB. 

 

I used RSD, no HOB.  Again, I only deleted TWO lines that I saw which had OEM (step 5 and ad the very end I believe).  To give an idea where they are.  Tex editor works, I believe I only used office 2007 word and after changes it made them in the xml file.  I did have Notepad+ on my phone and was playing with it there also on the bus, lol.  Save, pop that into your FXZ file, replace/copy and should be ready to go. 

 

Used RSD lite 5.7 (tried 6.1.5 before but wanted to stick with one that works for me (always).  Maybe some of this helps, annoying rear end error message.  Some more experience may have an EXACT fix.  If you are not too attached, try the FULL FXZ with RSD lite;-)  It said SD card (external) needed to be formatted also, and I said to do it, but MY FILES REMAINED WHEN IT WAS DONE.  Odd:-)



#5 Doddits

Doddits

    n00b

  • Dedicated Supporter
  • Pip
  • 23 posts

Posted 24 April 2013 - 06:12 AM

I decided to play with the settings to see if that would help. I disabled the 'Notify Me' setting and do far have not seen the error. Fingers crossed that it will be gone. That setting was annoying me anyway....

Please Login or Register to see this Hidden Content

 

Please Login or Register to see this Hidden Content

  62.68KB   36 downloads

Sent from my DROID BIONIC using Tapatalk 2
  • rlewis312010 likes this

#6 rlewis312010

rlewis312010

    Member

  • Members
  • PipPip
  • 111 posts

Posted 24 April 2013 - 08:13 AM

Simple, lmfao, thanks for sharing.

I decided to play with the settings to see if that would help. I disabled the 'Notify Me' setting and do far have not seen the error. Fingers crossed that it will be gone. That setting was annoying me anyway....

attachicon.gif

Please Login or Register to see this Hidden Content



Sent from my DROID BIONIC using Tapatalk 2



#7 GeoLund

GeoLund

    n00b

  • Members
  • Pip
  • 1 posts
  • LocationCO
  • Current Device(s):Droid Bionic

Posted 28 April 2013 - 09:42 AM

I'm having the same error message appear several times a day. My "Notify Me" has not been selected and I still get the message. 

 

I'm using a Droid Bionic and the error started appearing after getting a system update to Android 4.1.2



#8 gsDroid

gsDroid

    n00b

  • Members
  • Pip
  • 3 posts

Posted 30 April 2013 - 10:51 AM

I'm also getting this message more than once a day and I have 'Notify me' unchecked.  It started after the 4.1.2 update, FDR, and Ubuntu exploit to get root back.  It doesn't seem to cause a problem, but is annoying.



#9 gsDroid

gsDroid

    n00b

  • Members
  • Pip
  • 3 posts

Posted 04 May 2013 - 10:12 AM   Best Answer

I think I have fixed the problem.  I wiped cache in stock recovery and cleaned up the Dalvik cache in Titanium Backup (root).  I haven't seen the message since.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users