I have a warranty replacement M8. I am s-off (via Sunshine) and rooted with TWRP recovery. I cannot turn my wifi on. If i go into the settings and try to turn it on it just sits there for a minute or so and does nothing. Doesn't come on and no error.
Any ideas?
dneiding said:
I have a warranty replacement M8. I am s-off (via Sunshine) and rooted with TWRP recovery. I cannot turn my wifi on. If i go into the settings and try to turn it on it just sits there for a minute or so and does nothing. Doesn't come on and no error.
Any ideas?
Click to expand...
Click to collapse
In case anyone has this problem in the future i think i found the problem. I flashed the wrong insecure boot image and this disabled wifi (http://forum.xda-developers.com/showthread.php?t=2708686&page=4).
After fixing that my wifi is back to working.
Related
I was having an issue with google music not playing any audio although other apps worked fine so I decided to restart my phone. When I did I got stuck in a bootloop, my phone turns on to the white htc screen then immediately shuts off. I'm unable to access my bootloader or recovery and my phone will randomly turn on to the white htc screen without any input from me and then proceed to turn off again. There is slight heat from my phone so I can assume even though the screen is shutting off the phone isn't off. At first I was able to use adb to access recovery and did a factory format from there but that failed to solve my problem and now I am able to get adb to recognize my phone is connected anymore. I'm running stock rom rooted with s-off. I would greatly appreciate any help on this matter.
Natokoa said:
I was having an issue with google music not playing any audio although other apps worked fine so I decided to restart my phone. When I did I got stuck in a bootloop, my phone turns on to the white htc screen then immediately shuts off. I'm unable to access my bootloader or recovery and my phone will randomly turn on to the white htc screen without any input from me and then proceed to turn off again. There is slight heat from my phone so I can assume even though the screen is shutting off the phone isn't off. At first I was able to use adb to access recovery and did a factory format from there but that failed to solve my problem and now I am able to get adb to recognize my phone is connected anymore. I'm running stock rom rooted with s-off. I would greatly appreciate any help on this matter.
Click to expand...
Click to collapse
Oh buy. You don't factory reset from recovery... If you can use adb, push a rom to the sdcard and flash it in recovery, assuming you have a custom recovery.
ironbesterer said:
Oh buy. You don't factory reset from recovery... If you can use adb, push a rom to the sdcard and flash it in recovery, assuming you have a custom recovery.
Click to expand...
Click to collapse
When I try to use adb it doesn't detect my phone, I do have twrp installed as my custom recovery.
edit: was able to use adb to enter recovery after letting the phone completely discharge
Natokoa said:
When I try to use adb it doesn't detect my phone, I do have twrp installed as my custom recovery.
edit: was able to use adb to enter recovery after letting the phone completely discharge
Click to expand...
Click to collapse
Flash a rom. You should be all set.
ironbesterer said:
Flash a rom. You should be all set.
Click to expand...
Click to collapse
Thanks for the help, got it all sorted out.
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?
ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/
If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:
Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!
You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.
Hi,
a while ago my OPO fell down and since that bluetooth and wifi isn't working anymore.
On the Phone was Paranoid Android installed and everytime I tried to turn on bluetooth or wifi it rebooted.
Today I flashed the original CM with fastboot.
After the phone started up it reboots after 1-2 seconds.
There is no time to complete the Setup and turn off Wifi/Bluetooth.
After that failure I wanted to install PA again but I can't copy the .zip to the phone. I tried it with sideload and
adb push in TWRP and also in CWM Philz Touch but it's not working (protocol failure).
Anyone got an idea how I can flash a (for me) working OS on my OPO?
Thx
Erik State said:
Hi,
a while ago my OPO fell down and since that bluetooth and wifi isn't working anymore.
On the Phone was Paranoid Android installed and everytime I tried to turn on bluetooth or wifi it rebooted.
Today I flashed the original CM with fastboot.
After the phone started up it reboots after 1-2 seconds.
There is no time to complete the Setup and turn off Wifi/Bluetooth.
After that failure I wanted to install PA again but I can't copy the .zip to the phone. I tried it with sideload and
adb push in TWRP and also in CWM Philz Touch but it's not working (protocol failure).
Anyone got an idea how I can flash a (for me) working OS on my OPO?
Thx
Click to expand...
Click to collapse
First off, I would recommend TWRP recovery.
Connect your OPO to your computer and flash TWRP in fastboot (assuming you know how to).
After which transfer all your information from your internal storage to your PC.
After that, follow the guide here to return your OPO to stock: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Now try and see if your wifi and bluetooth works. If they don't, my guess is to send it back to OnePlus
Bobbi lim said:
First off, I would recommend TWRP recovery.
Connect your OPO to your computer and flash TWRP in fastboot (assuming you know how to).
After which transfer all your information from your internal storage to your PC.
After that, follow the guide here to return your OPO to stock: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Now try and see if your wifi and bluetooth works. If they don't, my guess is to send it back to OnePlus
Click to expand...
Click to collapse
I've done that already.
Even when I try to return to stock the OPO it's not working.
The OPO Support tried the same over Teamspeak but it didn't work.
I first wanted to send it back to OnePlus but then some fluid flow over the phone.
Of course I dried it and luckily it's still working like before. But I'm sure I can´'t send it back because the water indicators changed their color.
Erik State said:
I've done that already.
Even when I try to return to stock the OPO it's not working.
The OPO Support tried the same over Teamspeak but it didn't work.
I first wanted to send it back to OnePlus but then some fluid flow over the phone.
Of course I dried it and luckily it's still working like before. But I'm sure I can´'t send it back because the water indicators changed their color.
Click to expand...
Click to collapse
I guess the only way out is to send your OPO back for repairs as you can't get this phone repair at a normal phone store
I think your logicboard (mainboard) are broken ... Send your One back
As per title, it just happened while I was using the phone while charging. Trying my luck as I'm not in the country(Australia) that I bought my Pixel from. Grateful for any suggestion that the sub can provide. Non rooted stock rom
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Yes only bootloader. What you have mentioned do not require recovery mode right ? Cos I can't boot into it. Thanks for your reply
k.s.deviate said:
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Click to expand...
Click to collapse
The bootloader would have needed to have been unlocked already.
indifferent1 said:
The bootloader would have needed to have been unlocked already.
Click to expand...
Click to collapse
no it doesnt, I suggested unlocking the bootloader first, that way it factory resets. this might fix the problem, if not its unlocked so he can flash the factory image.
Bump? I'm having this problem as well.
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
graymoment said:
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
Click to expand...
Click to collapse
I'm having the same issue. My wife's Pixel entered a continuous boot loop today. It only loads the white screen that says "Google." I can enter the bootloader, but when I select "recover," it goes back to the bootloop. As far as I know, she is on Android 8.1, debugging mode is off and the phone is 100% factory.
If anyone has solved this issue, it would be greatly appreciated!
Thanks
has anyone figured this out?? this happened to me today, i was using the phone, the poof it restarted itself and stayed in a boot loop. i can get into the recovery, i tried wipe/factory reset. any suggestions? google told me i need to send it to whatever company to get it fixed or get a new phone. verizon told me to go through insurance. insurance told me to go through verizon because i may be able to use the extended warranty. went back to verizon but they wont take it because the screen cracked a year ago. its not a deep crack and it didnt affect the phone at all, never had an issue. so now i go back to assurion and now they need an affidavit about my screen being cracked. im at a loss.... i havent rooted a phone since my droid x, then s3 days. so im essentially new again!
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
thedosbox said:
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
Click to expand...
Click to collapse
I had the same thing happen yesterday (not long after the Android 10 update). I was finally able to get it to boot after multiple tries and it stayed up long enough for me to enable "OEM unlocking" in Developer options. Now at least I have the option of unlocking the bootloader and re-flashing the OS with an image directly from Google.
Has anyone been able to get past this problem by reflashing the image? I suspect the underlying problem is some kind of hardware fault with eMMC, DDR, or the SOC itself.
One other interesting behavior I noticed is that the only way to shut it down and stop the bootloop is to select the "Power off" option in the bootloader menu. However, if I plug it in to charge when it is fully powered "off", it will start up the bootloop again.
Same sitution here. A couple of days after installaing it suddenly went inte a G-bootloop frenzy.
Erratic though, sometimes I could boot up (2-3/40 boots) but then it froze and started again.
Also Recovery and Safemode is very hard to get into.
Got in once or twice out of 100 boots, Bootloader Fastboot is generally reachable though.
It exhausted the battery and now I'm holding off trying to interfere, until I get more info off the net.
This is the informatoin I get:
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
Keeps looping
Hard or soft reset want help.
What to to?
Tried Odin, but it want make connection
Tried taking out battery without help.
you cant force it in to stock recovery?
leo5111 said:
you cant force it in to stock recovery?
Click to expand...
Click to collapse
I can't force it into anything it seems. It just keep rebooting all the time.
It's a battery connection issue. Look it up on YouTube. It's a simple fix. The battery connects to the main board via a connector. That connector can get loose.