hello xdadev,
i really need your help. I am a newbie in android world [just purchased my first android device] last month [samsung galaxy tab p6800]. since then, i was really excited to explore android world and its features where I was led to this site.
now, heres my problem: just this afternoon, at first, i used my wifi to access a shopping mall internet connection. but minutes after turning my wifi off, when i turned it on again to connect to another network, i was surprised that it wont start and when i open the settings menu, under it says error. im really worried.
had my unit restored to factory settings but still no changes. Rooted my galaxy tab but today, i unrooted it thinking that the rooting caused the trouble.
im also hoping to update my tab to ICS but with this problem, im really stuck! i dont know how to access my apps in the appstore.
is this a firmware error or a hardware problem? please help me. my tab helps me a lot.
thanks in advance. im willing to add some details if you could help me.:crying:
try to go back to the mall where it 1st connected, if it still doesn't connect, then use your warranty and ask for replacement.
7.7 is notorious for being a bit choosy when it comes to wifi, sometimes, it just stuck with "obtaining IP address" then will revert back to scanning.
I also encountered your error before, but I just simply turn the wifi on and off again
before going back to your retailer, try to totally deplete the battery first (it's like removing the battery) then charge your unit and try to connect again
good luck
the last thing i could remember was busybox got updated but failed to install. is there any possibility that the failure caused the problem?
nope
biopsin said:
nope
Click to expand...
Click to collapse
Ah, sorry, busybox could, and may very likely be the culprit! An older version did just that to my (I have the 6810), and a number of others, tabs.
This was for Stericson's version 8.0 and here was his reply to my email:
Sadly you fell prey to a bug that was in Version 8.0 of my installer. I fixed it in 8.1, but it seems many still got the bugged version.
To fix the issue, you need to reflash your current rom. You do not need to wipe or clear any data.
You can also look in this thread: http://forum.xda-developers.com/showthread.php?t=1691410&page=2
It has an update method that should fix your issues.
Again, I apologize for this error
Please let me know if you need anything else from me.
I did just that and reflashed my rom using Odin and then re-rooted. I haven't, since, re-installed Stericson's busybox although later versions supposedly fixed the problem. I see there has just been another update in the Play store.
Damn I got the same error today, also after a lot of updates came trough.
Still working on fixing it. Will restore backup first after full wipe..
EDIT : Ok just went to recovery via power+volume up , factory reset, a nandroid restore and wifi working again.
Phew.
Ah! Got my tab working again. Thanks guys for the link and comments. The (update. Zip), did fix the issue. Busybox related bug. Starting to re download my apps again since I got my tab data wiped. :-(
Sent from my GT-P6800 using xda app-developers app
Not rooting my phone as of now. Will wait for the ICS first before rooting again. Tab is fully working already.
Sent from my GT-P6800 using xda app-developers app
Hello folks,
I've been using a few builds of ParanoidAndroid on my 16gb N7 (grouper) for quite some time.
Last update, thou, has broken my tab's NFC. Whatever NFC signal I try to use (tag, N4, Gnex), nothing happens, not even an error message. I tried several restoration and full wipes with no success and then decided I might as well go back to stock since 4.2.2 seems to fix most issues I had with it.
So I flashed the latest factory image, with a clean install (manually erased boot, system, userdata, etc. thru fastboot) and the problem is still here ! I performed 2 more factory reset without any success.
So before I return my tab (and that will be annoying cause it's probably gonna take them a month before it comes back), is there a way that would help me check if the problem is hardware or sofware related ? If it's software, there has to be a way I can fix it myself, so I won't bother send it to be repaired.
Any help would be appreciated, thanks a lot to anyone.
(and sorry if this question already exists, I couldn't find a thread about it).
You've already eliminated the probability of it being software.
Sent from my Nexus 7 using Tapatalk HD
Hi guys , I've got a problem with my Nexus 4. Basically whenever I try to copy over my pictures using the standard MTP method It'll crash and say my device isn't responding or not compatible to transfer with my PC. When I first got my phone it was all fine but recently it's given me these problems. Even if I use the PTP method still crashes. I'm running Kitkat 4.4.2 with Franco's Kernel and everything else is stock.
Any solutions?
Thanks
Hi!
I just bought a Nexus 4 with broken touch screen which I replaced myself.
After I replaced it, I decided to start fresh and updated the device directly to stock 4.4 using fastboot commands and got stuck in bootloop (4 circles going on for hours).
Then I tried different factory images and managed to boot under official Android 4.2.2 and it worked flawlessly until I tried to update with 4.3 OTA (with radio .83)
I found out that downgrading radio from .83 to .48 (or .53) allows the device to boot under Android 4.3.
I'm now stuck at this stage because the same trick does not work after 4.4 OTA (from 4.3).
The issue seems to be acknowledged by Google but they don't seem to have an official software fix for it since they only go for a replacement.
I'm considering an RMA but since I replaced the screen myself, I'm facing the risk to be charged 200€ if my warranty gets void (if they really control the device as they say).
Anyone managed to fix this issue? It seems to be linked to the radio (can't go further than radio .48 / .53)?
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
neoantho said:
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
Click to expand...
Click to collapse
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
varun037 said:
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
Click to expand...
Click to collapse
Did you find a solution?
Not yet. I will definitely post if I am able to find one. Researching on the topic currently.
I've got the same problem with 4.3 bootloop. Could this be fixed with custom rom?
Try flashing 4.2.2 rom - custom or stock
I'm with 4.2.2... and that's not what I asked. I want 4.4.2. Is it possible to load custom kit kat with this kind of sensor problems?
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
varun037 said:
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
Click to expand...
Click to collapse
I'm on 4.3 and the sensors dont work ... the proximity, gyro... nothing works... any solution?
Hello friends, i have a similar problem.
I went to replace the glass and warmed him a lot and damaged the lcd. I bought a complete lcd with touch, but when installing it the cel came in infinite boot, Flashed the 4.2.2 and booted but sensor is working by testing q I did for an app, the problem is they do not find my network and baseband ta as unknown, been through the radio's 4.2.2 (the version I am now). the motherboard was not with the screen when I get heated to the glass, were in housing with the display flex earpiece with proximity sensor and flex usb that has the microphone and led, everything is normal, the LED only that does not work. One would like some light please. I thought about buying the flex usb to see if it resolves, but does not want to risk spending for nothing. Thank you very much!
Sorry for my english, I'm using google translator
Sorry to Disturb
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Gloftking said:
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Click to expand...
Click to collapse
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
FEW
varun037 said:
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
Click to expand...
Click to collapse
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Gloftking said:
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Click to expand...
Click to collapse
Follow this. It has the reset flag removed and will not wipe your data
http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app
Hi,
I am facing the same issue .. Nexus 4 is stuck at boot loader after screen replacement .. is there any solution that I can follow to resolve this .
Regards,
Ripu Daman
The same problem with me, i did replaced my phone screen. I didn't notice that could damaged the phone. :crying:
so, theres no way to solve ??
Only way is to downgrade the os version to 4.2.2 and stay there.
nexus 4 stuck at boot loop.
Hi guys i have the same problem as you are describing, o got a nexus 4 android 4.2.2 JQRW build I've flashed it from all different ways and i just got flash cm10.2 and carbon rom but only stuff jeallybean and as someone said here i used adb sideload to push the update 4.3 and got stuck at the boot but i flash the radio 84 to 48 and my phone boot Fine but i am stuck at jeallybean yet and i want chroma rom android 7
---------- Post added at 03:00 AM ---------- Previous post was at 02:56 AM ----------
Please we need a wise man to fix this problem. I am tired of flashing stock img and custom ron for nothing.
hi everyone
recently i am facing few problem with my Nexus 7 2012 , android 4.3 , non rooted
1st - I am facing copy bug which is crashing any app from which i copy and
2nd - which is quite strange
my 4.4.2 update (which has been downloaded for quite sometime and was ready to install) gets automatically deleted
and now its showing android 4.3 as upto date whwnwver i check for update in settings..
where are my 4.4.2 downloaded files i have no idea...
i havent deleted anything
Any help!!
Is this some sought of a bug or system update file which has been deleted will get replaced by android 4.4.4 later ?
have i done something wrong
i am all confused ..
plz help