yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] jazzdude555:
Last week my Nexus 7 (2013 wifi) updated to 4.4.3 and it has been working fine for the last few days.

Then suddenly it stopped connecting to my home wifi, in the space of a few seconds, the signal goes from excellent to weak even though I am only a few metres away from the router. It will not automatically try to connect, but when I hit connect it goes from a strong signal icon, saying 'connecting' then back to 'saved' then to 'disabled', then 'not in range' then strong again etc. Each time I try to connect it tries to connect then a second later goes back to 'saved' without trying to do it again.

I have tried static ips, changing the settings on the router, taking off security completely, changing channels, and it acts just the same.

It was rooted and with the toolkit have tried reverting back to stock and unrooting it and although the process says it is a success, I cant get past the first page as you have to log on to a wifi network and it still is doing the same thing.

Is this a hardware or software issue?

All the other devices in the house connect to the wifi network without a problem it is just this now which without wifi is basically a brick.
[Nexus 7 (2013) Q&A] Aerowinder:
I don't understand this: you updated for 4.4.3, then reverted back to stock. Can you elaborate on this point, please?

If you did not try a data wipe, you can try deleting the following two folders and rebooting: /data/misc/dhcp, /data/misc/wifi
[Nexus 7 (2013) Q&A] jazzdude555:
By stock I meant flashing a stock image and unrooting it. It was stock anyway but rooted. I also tried a full data wipe in custom recovery.

The problem is, I now can't get past the first page when starting up as you have to log into a wifi network before you can get into the phone.
[Nexus 7 (2013) Q&A] meekrawb:
(1)Try rebooting your router.

(2)You may be able to bypass the welcome screen by tapping on the four corners of the screen starting from top left and going clockwise.

[Note: I borrowed number 2 from Mooem on android central. You should thank him if that one works for you.
[Nexus 7 (2013) Q&A] jazzdude555:
Thank you, but rebooting was the first thing I tried.

I also just tried tapping the four corners of the welcome screen but that didn't work either.

It is becoming apparent that perhaps it has a hardware fault as I would have thought a hard reset would have cleared up any software issues.
[Nexus 7 (2013) Q&A] jazzdude555:
After a few more frustrating hours, I managed to flash a custom rom on it, no joy, then flashed back stock, did a full erase, nothing.

I then sat on the router settings, took off security, changed channels, changed frequency, still the same.

The I took the back off, the 4 springs are still there so it is not a connection problem.

So has the wifi just died?

The strange thing is after most logging on attempts, the wifi signal for the router dissapears or says disabled and then comes back again about 10 seconds later.

I cant get past the login screen to put debugging on so that I can lock the tablet so that I can at least take it back to where I bought it from. The tapping the four corners thing doesn't work with this rom although it strangely did with the custom rom (CleanRom 4.4.3).

Do I just bin it and buy another one?
[Nexus 7 (2013) Q&A] meekrawb:
I don't think you need to have debugging on. Just boot into the bootloader manually and then you should be able to lock it.
[Nexus 7 (2013) Q&A] zfrank2:
If you turn off bluetooth, then all is ok. Seems to be a bug in update to 4.4.3
[Sprint Samsung Galaxy S III] congaman59:
I am rooted with a stock rom on 4.1.2 with Oden. I'm having some problems updating my prl and other things on sprint. I wondered if I can use xdaforums.com/showthread.php?t=2738533 to jump to 4.4.2 instead of going back to sprint stock unrooted 4.1.2? please let me know my phone is acting screwy!
[Sprint Samsung Galaxy S III] JoHnNYBlaZE716:
Dont really understand what your asking
[Sprint Samsung Galaxy S III] roirraW "edor" ehT:
You can Odin the stock ND8 tar.

Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
[Sprint Samsung Galaxy S III] congaman59:
I think I fixed my post.
[Sprint Samsung Galaxy S III] roirraW "edor" ehT:
The answer is yes.

Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
[One (M7) Q&A, Help & Troubleshooting] dr.kis:
After the update to Sense 6.0, the ring volume spontaneously reduced to a minimum. Set it to desired level, but after some time again to reduce.

I try to uninstall software market, did not help, did a hard reset and nothing happens, the problem still exists.

What is this, is there a similar problem?

Is it a update problem?

Becomes a little irritating for mised calls
[One (M7) Q&A, Help & Troubleshooting] Fain11:
Mostly when it rings in your pocket, no?

Try cleaning the proximity sensor, sometimes it helps.

If not, just install a Sense 5.5 Rom, like ARHD 53.0.
[JASJAR, XDA Exec, MDA Pro General] Greenarcher707:
i'm on cingular using my unbranded xda exec and the reception is freakin terrible.. is there a way to enable 850 Mhz support on the phone? i already have upgraded ROM and a 64k Sim but no luck. Please help, i don't want to switch carriers.
[JASJAR, XDA Exec, MDA Pro General] 100thMonkey:
extremely sad but extremely true....no 850 on the Universal...grab a TyTN
[JASJAR, XDA Exec, MDA Pro General] Greenarcher707:
i don't like the tytn's looks... but the feature set is ok. mebbe i should switch carriers.
[T-Mobile Samsung Galaxy S 4] mnm24:
I was on a custom rom though that wasnt TW... This problem started after I installed Insane Rom.. I dont think its a hardware because this problem only occured after installing Insane ROM. Because if it was a hardware issue then the S-Voice, Skype, Google Now, etc would not work. Before that, every ROM I installed was no problemo.... I tested it with S-Voice and Skype and it was working fine.

Something went wrong after I flashed the Insane ROM that screwed up my phone :(
[T-Mobile Samsung Galaxy S 4] mrzhadow:
We 1st need to know if you took the OTA nb4 firmware. Are you on mdl, mk2 or nb4 bootloader?
[T-Mobile Samsung Galaxy S 4] Android_Monsters:
You download the stock image from:

http://www.sammobile.com/firmwares/

Then you go into download mode while connected to your laptop and use Odin to flash the stock image.
[T-Mobile Samsung Galaxy S 4] mnm24:
How do I check this
[T-Mobile Samsung Galaxy S 4] mrzhadow:
Boot in download mode and tell me if you have Knox.

---------- Post added at 01:05 PM ---------- Previous post was at 01:00 PM ----------

Download this https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo and tell me the bootloader name
[T-Mobile Samsung Galaxy S 4] mnm24:
M919UVUEMK2 bootloader and modem are the same M919UVUEMK2
[T-Mobile Samsung Galaxy S 4] mrzhadow:
OK. You already have Knox so your warranty is void. This is what you will have to do. Download Fennys full nb4 firmware and flash it. You need to do a full wipe before you flash in Odin. Get Odin ready uncheck auto-reboot and load fennys file. Boot in recovery and wipe data, cache, dalvik, system and then do a factory reset. Once you finish wiping stay in recovery and choose to reboot in download mode. Once in download plug phone to your PC and you should see the com light light up. Once you see the light click start and wait for it to say pass. Once you pass pull the battery out and reboot in recovery by pushing power+volume up and wipe data, cache and dalvik and factory reset. Once you have wiped reboot phone and profit. I would like you to find Fennys thread and thank him. Here's the link for the file you need http://xdaforums.com/showthread.php?p=52924856
[T-Mobile Samsung Galaxy S 4] mnm24:
Ok so I'm downloading that file right now

A) So after its done, I put it on my phone and flash it right?

B) Which part do I load that file in Odin, bootloader, phone, pda, etc?

C) After I flash it, wipe everything and how do I do a factory reset?
[T-Mobile Samsung Galaxy S 4] serio22:
A) no, flash in PC

B) PDA

C) only thing you will be able to do is factory reset which is fine.. Just boot into recovery and factory reset
[T-Mobile Samsung Galaxy S 4] mnm24:
Everytime I try to flash that it gives me aborted message :(
[T-Mobile Samsung Galaxy S 4] mnm24:
OK I wiped everything in recovery, now got the phone into download mode, now going to put the firmeware in PDA and then going to take out battery and wipe it again.

so after doing all that it should be good?
[T-Mobile Samsung Galaxy S 4] mnm24:
i still have the error of not anyone hearing me during calls
[T-Mobile Samsung Galaxy S 4] mnm24:
People can only hear me when my phone is in speaker
[T-Mobile Samsung Galaxy S 4] serio22:
Try flashing it again.. No wipe
[T-Mobile Samsung Galaxy S 4] mnm24:
The mic is working because I just tested it with S-Voice but on calls people can only hear me when I put it on speaker
[T-Mobile Samsung Galaxy S 4] mnm24:
Still the same thing, they can't hear me without speakerphone on :(
[T-Mobile Samsung Galaxy S 4] mnm24:
Tested it with S-Voice and Google Now and it is working fine, but why is the calls not working?
[T-Mobile Samsung Galaxy S 4] mrzhadow:
There's something that's not getting wiped. Were you on CM by any chance?

---------- Post added at 06:38 PM ---------- Previous post was at 06:03 PM ----------

I hate to say it but most users that experience your problem end up having a hardware issue. If you have insurance you are better off getting a replacement.
[T-Mobile Samsung Galaxy S 4] mnm24:
No I was on a custom rom though that wasnt TW... This problem started after I installed Insane Rom.. I dont think its a hardware because this problem only occured after installing Insane ROM. Before that, every ROM I installed was no problemo.... I tested it with S-Voice and Skype and it was working fine.

Something went wrong after I flashed the Insane ROM that screwed up my phone :(
[T-Mobile Samsung Galaxy S 4] mrzhadow:
Actually the problem is putting Aosp or Cm on your phone and then going back to TW. It is a well known issue. Aosp and CM leave files behind in your internal SD that you cannot wipe through recovery. To fix that you will need the superwipe zip and then you can go back to TW. Google superwipe and flash the file to wipe your phone completely. Then flash whatever ROM you want. Insane KitKat is flawless. There is no bugs unless you modify with xposed.
[T-Mobile Samsung Galaxy S 4] mnm24:
Can I use this superwipe?

http://xdaforums.com/showthread.php?t=2379103

Can't find anything else for SGHM919
[T-Mobile Samsung Galaxy S 4] mnm24:
Should I just use this to megawipe it: http://www.usoftphone.com/t82766.html
[T-Mobile Samsung Galaxy S 4] mnm24:
I just did the super wipe and still the same problem. I think it's the modem problem because after the super wipe, i installed evil's 4.3 wicked_v10 and my modem is NB4
[T-Mobile Samsung Galaxy S 4] mrzhadow:
You are on the latest modem note so you should not be having any problems. After doing a super/megawipe you should've been good to go. I'm leaving towards the hardware having a problem. Hardware problems are usually repaired for free or even replaced. You just have to pay shipping. I usually pay $5 for a bad hardware replacement.
[T-Mobile Samsung Galaxy S 4] mnm24:
Who do I send it to? Can you please elaborate on this?

How long does it take?

Will I get a new phone?
[T-Mobile Samsung Galaxy S 4] mrzhadow:
Your carrier. Just tell them that you are having problems. Tell them you took the latest OTA update and now people can't hear you while you make calls.
[T-Mobile Samsung Galaxy S 4] serio22:
they'll send you a refurb and you send your device when you get it with the box it comes in
[T-Mobile Samsung Galaxy S 4] mnm24:
I bought the S4 and paid it off full price from T-Mobile in May and still have service with them. So I just tell them that?
[T-Mobile Samsung Galaxy S 4] mnm24:
Samsung will send one or T-Mobile will? I bought the S4 and paid it off from T-Mobile and still have service with them as well.
[T-Mobile Samsung Galaxy S 4] mnm24:
Just got off with the T-Mobile agent and he's saying he can't do it.... I bought the S4 last May 2013

Agent:

I see. Thanks for the information. In regards to the warranty, please be advised that coverage is good for 12 months. If the month of purchase is correct, which is on May 2013, then I'm sorry to say but it's already past the warranty period.

I understand that the problem started after an OTA update, but so far there is no known OTA-related issues documented on our end in relation to this update.
[T-Mobile Samsung Galaxy S 4] mrzhadow:
Do you have insurance on the phone? If you don't I would insure it and call a few days later and put in the claim. Also the year warranty is Samsung's warranty not tmobiles. If you don't want to wait then take it to an actual store and tell them you tool the OTA and now are having issues. Before you do that you will have to flash the stock image. I'm almost sure that the store will replace it for you since you will physically show them your problem. Just don't mention anything about rooting or any modifications you made. Good luck!
[T-Mobile Samsung Galaxy S 4] mnm24:
EDIT:

I called Samsung and they said it is under warranty and gave me a UPS label to send to them. What do I put the phone in? They said to put it in any box. I just put it in a brown envelope.

Is that fine?
[T-Mobile Samsung Galaxy S 4] mnm24:
I called Samsung and they said it is under warranty and gave me a UPS label to send to them. What do I put the phone in? They said to put it in a box. I just put it in a brown envelope.

Is that fine?
[T-Mobile Samsung Galaxy S 4] mrzhadow:
No envelope unless its bubble wrapped and labeled fragile. Good for you!! Glad its gonna work out for you.
[T-Mobile Samsung Galaxy S 4] mnm24:
Okay, I found the S4 Original box.

Can I just put the phone in the S4 box and then put it in a padded envelope?

Also, should I reset the phone to original stock before I send it?
[T-Mobile Samsung Galaxy S 4] mrzhadow:
Yes and yes.
[Moto G General] Landrea:
Hey there, it's been a while since my last post.

This is what happened to me:

my (beautiful, beloved, perfectly tuned, 3-months-old) Moto G decided to shut itself off about 10 days ago and never come back alive.

It's likea brick, no fastboot or recovery mode, just a "blink" of the led the moment I plug it into charge.

I've sent the phone to Motorola, I hope they could fix it.

My Moto is unlocked and rooted, I don't know if this can be a problem for the warranty... I hope not, because I think the issue is absolutely not related with rootingor so.

I'll keep you posted.

A hug from my old phone (Xperia mini pro)
[Moto G General] kirmr:
I think that as you are in EU, unlocked bootloader is not a problem.
[Moto G General] SbM_:
Knowing how it turns out will be interesting though, as EU legislation is open to interpretation. So yes, please keep us posted, and meanwhile: good luck :)
[Moto G General] Senexis:
I'm sorry to say, but your warranty is definitely void.

Quoted from the Bootloader Unlocked Warning:

"Your device's bootloader has been unlocked, allowing critical software components to be altered in a manner that may cause damage to the device or result in injury to users.

Motorola disclaims any liability for harm to person or property resulting from use of this device. Except for Developer Edition devices, all warranties are null and void."

Will definitely be following your story though. Would like to know what happens next. Keep us posted! :)
[Moto G General] rogeriorp:
Should've just simply hold power for 2 minutes while plugged in on a power source, the battery is most likely dry.

Enviado de meu Moto G usando Tapatalk
[Moto G General] FelzPT:
Same thing happened to mine a while ago... one day i had like 15% battery and put it to the charger during the night, next morning it was shut off.. I tried to start it and the only thing that would show up was the 0% battery screen... eventually i tried and got into the bootloader screen, and pluged it into my pc inhopes to reflash the stock rom cuz i thought it was some kind of software related problem, but by plugging it in during bootloader i noticed it didnt even recognise my pc and it didnt charge up. But now all it does is blink the led when plugged in... and when it is plugged into my pc i can hear the sound of something being plugged in and out over and over again..

I already contacted Amazon UK and got a replacement, didnt even contact Motorola cuz they have no stores in Portugal...

I think it must be some software problem or maybe micro-usb related problem... or even the battery being dry..

Ah by the way i tried lots of thing and none worked like holding power while conected, holding power and vol-down..

So if you cant even get in the bootloader screen i dont think you have to worry about warranty, cuz there is no way to access the phone..

Sorry for my bad english...
[Moto G General] eemgee:
That's the motorola warranty, the European warranty over rides that and is for two years.
[Moto G General] denzel09:
Good luck buddy :good:
[Moto G General] ChavitoArg:
This. [emoji106]

Enviado desde mi XT1032 mediante Tapatalk
[Moto G General] Landrea:
Thank you ALL for your support :)

I'll keep you posted as I get something new.

10 days now since they got the broken Moto - still silence.

See you soon, friends!

My dearest,

of course I tried this procedure. No luck.
[Moto G General] satanas17:
Hi,

Hope the best for you & your beloved...
[Moto G General] Boss442:
Use my tutorial on "android original development" to recover the bootloader, if is loaded like "qusb_bulk" on the pc (check this) the tutorial allow you to recover it
[Moto G General] mint-an:
okay i got it working....

plug your phone into charger (not usb pc port).

wait until the display goes black.

press volume-down and power the same time AND hold it for 3 second

release both

If you are now on the bootloader/fastboot screen next step, if not redo until you are

do not do anything just wait and let the device charge // or // press normal bootup

My phone booted after 5 min with 3 % battery.
[Moto G General] eemgee:
Any news on the poor moto?
[Moto G General] Leproso_Ivan:
It is really sad to read this. May you recover!

Sorry for my bad english.

Iván!
[Moto G General] Landrea:
UPDATE:

HORRIBLE NEWS

They call me, they have fixed the MOTO G, but they found out it's ROOTED and UNLOCKED = warranty void.

I have to pay 91 euros if I want the phone back.

10 euros must be payed in any case.

WHAT WOULD YOU DO?

91 it's a lot, I payed it 170 three months ago.

It's very very frustrating, Motorola.
[Moto G General] adizz4:
I'd pay if I were you 'cus I love my phone. But could you enquire them about the european warranty thing.

Also ask them what was wrong, maybe its something you could fix yourself if they havent already fixed it.

You should have asked around a bit before you sent your phone to moto.

You were one the first ppl to reply to my thread in the moto g section. So, I remember you :)
[Moto G General] denzel09:
They have proofs that damage is caused by root/unlock?

I think not.

The first year is covered by seller. Where you bought it?
[Moto G General] SbM_:
Well they specifically warn you that your warranty is void if you ask for the unlock code, regardless of the damage.
[Moto G General] Landrea:
I bought it on Amazon marketplace, they cover 3 months, then it's Motorola.

Of course they don't have any proofs, but they play dirty with the rooting thing :/

I'm pretty sure the damage isn't related with the rooting... But you're right, the warranty is void indeed.
[Moto G General] SbM_:
I'm sure it doesn't, but they don't give a ****. It gives them an excuse to charge you for the repair…
[Moto G General] helinhof:
Keep Calm

Same thing happened to me.

I tried like 20 methods i found on the internet to solve this, it's similar to that fully drained battery problem, none of them worked.

when connected to pc it'd recognize the phone (that little sound, win xp) and "disrecognize" it soon after. it's like it was bootlooping.

The most i could get was a black screen, little vibrations and led blinks so i sent it to a repair shop.

I was confident they'd at least replace the battery with a new one...

turns out.. they called me the day after saying that they gave an electric shock on the battery and it had risen from the dead. Just like the battery, i was shocked, and they even charged me nothing. Free. $0.00

Well i hope this helps you and people with the same problem looking for answers. Good luck and greetings from Brazil :fingers-crossed::)

P.S.: Sorry for any silly english mistake, not using translators.

EDIT: Mine was also unlocked and rooted and i can assure you, it has nothing to do with with the problem. It's BATTERY related stuff. I also couldn't access fastboot or recovery, just black screen.
[Moto G General] Landrea:
Thank you for the feedback, I'll let you know if I can figure out something good!
[Moto G General] BlueFlame4:
That's the point. European warranty applies only to the seller, not the manufacturer. So if your device has a defect within 6 months you can send it back to the seller regardless of what you have done with it (except harsh things like throwing it on the ground, etc.). The seller then has to proof that your modification (aka bootloader unlock, root) has caused the malfunction. This would normally not happen so you're good to go.

After 6 months there is a 180° turn and YOU have to proof, that the malfunction isn't caused by your modification (which can be hard sometimes).

Since you sent it back to Motorola itself and not to the seller (Amazon Marketplace), you have to pay the money I think. Sorry :/
[Moto G General] Landrea:
Yes you may be right, but the warranty seller is 3 months, not 6, in my case (the seller is Macaway, ltd)

Btw I've decided to take it back broken, and try to fix it myself. I'll keep you updated!
[Moto G General] NextGenGTR:
No you dont understand, amazon it self says 3 months and thats because most people dont know the law, send the phone to amazon if you have had it less than 6 months and let them fix it, show them you have good understanding of the law and explain exactly everything and blame it on them :/
[Moto G General] Landrea:
It's not Amazon itself, it's an amazon shop , Macaway.
[Moto G General] NextGenGTR:
You should stil try to get it repaired for free, i mean we are all trying to save you some cash.
[Moto G General] Landrea:
The first thing I did was writing to Amazon and ask for free support. They told me time was over, and I needed to send it to Motorola.

What am I supposed to do? Send it to Amazon with a threatening letter? XD
[Moto G General] Elador:
I'd phone Amazon again. In the EU, they (in your case the Marketplace shop) have to give you 6 months, no way out of it. Phone up Amazon, then Macaway.
[Moto G General] Landrea:
OK, I am trying to contact Amazon right now.

Thanks, I'll let you know :)
[Moto G General] Landrea:
UPDATE:

I phoned Amazon, they definitely WON'T repair or give me a new MOTO G.

So I refused to pay 91 € and I've just take it back (broken) from Motorola.

They attached a sheet saying "ATTEMPT TO UNLOCK THE BOOTLOADER - WARRANTY VOID"

So at the moment I've my brick back.

What would you do? Please suggest me, now.

I can't access fastboot or recovery mode.

It's like DEAD, apart from BLINKING LED (once and shortly) if I plug it into charge (usb and wall) AND

If, plugged, I press the power botton for like 5 second, the led blinks.

I don't know what to do.

Can I try something to fix it myself?
[Moto G General] pokey9000:
Did you try boss442's suggestion earlier? If it's in Qualcomm bootloader mode then there's a chance. Don't worry that the screen isn't turning on, since it won't if it's in this state.
[Moto G General] Landrea:
I haven't tried yet.

How can I know if the phone is recognized in That mode by the PC? Nothing happens when I plug it to USB.
[MENTION=4749802]Boss442[/MENTION] thanks!
[Moto G General] Boss442:
Check the device manager