My Pixel used to be fine, until month ago the wifi and bluetooth burned. I'm sure this is not a ROM or system problem since those device didn't work at all even I factory reset it or flash another ROM.
The wlan0 is disappeared so it's not a problem. However, the malfunctional bluetooth device still there, which cause system froze.
Is there any method or ROM that has such ability to unload the bluetooth module or make system ignore it, so can I have it boot and works like a feature phone?
The phone is unlocked and rooted, but I can NOT adb access without recovery mode since it didn't boot.
First time post here, if any problem please let me known.
Related
Hi!
My Nexus 5 device seems to have many issues, some that I have resolved, some that appeared next. Here is some history.
- The first issue that I had was that some sensors were not detected, and the others were not working. Sensor testing applications found some of them (but they didn't work), and others like the accelerometer didn't even show up in the list.
- For a couple of months now, once in a while (at each ~2 weeks), I find my Nexus 5 powered off, and bricked (the boot process stops at the Google logo)
- Each time, flashing the original images worked (simply using flash-all.sh)
- After one of these flashes, I had no wifi. Flashing the original image did not work. Rooting/installing TWRP recovery, erasing cache, etc. did not work. I finally got it to work by installing a custom ROM, and never understood why it worked.
- Device bricked again, flashed the original image back. Wifi still works, but no SIM card detected. Absolutely no sensors are detected. The device reboots after a couple of minutes. This is where I am now.
What I tested so far :
- Rooting the device, running e2fsck on the partitions, some of them showed errors. None of them show bad sectors.
- Moving the content of /persist (to try to fix the SIM card problem)
- Flashing custom ROM, stock ROM, old ROM, different radio, etc.
- Removing/inserting the SIM card
I really am out of ideas, does anybody have ideas that I could test? I'm starting to think that I have an hardware issue but I still hope to repair the device... The issues started to appear right after the guarantee was expired.
EDIT: I found many threads about power button issues, however right now if I boot to Android the device reboots after few minutes, but when the phone is in TWRP recovery it stays open and never reboot. I therefore think that the reboot problem is not related with the power button.
I tried several methods before.
First was flashing the modem to work with GSM cards on calls and messages, but no data. I tried getting the MSL somehow but that didn't work. I flashed next TWRP without knowing anything about wiping the cache after installing SuperSU. I had to download the stock firmware again, and it was working stable until it shut down again when I flashed the new modem. I'm not sure what's causing the problem.
Keep in mind that I have two J3 Emerges, the one I'm modding and another one that has a cracked screen which functions very well. And I don't wanna mod the second J3 because of reasons.
EDIT: I just found out that formatting data via TWRP just causes the phone to behave normally, until somehow its connected to something... USB wasnt connected, and I think it has to be because of the phone checking the status of itself, despite being 'custom'.
EDIT 2: Found out, that the phone goes on a boot loop whenever I connect to the internet. Obviously, something must be going on.
EDIT 3: Looks like configuring the network was the issue... DANG. Anyone know of a way to bypass this bootloop?
hello, recently i bought myself a new op6, as it was good for modding and such. unlocked the bootloader, flashed twrp, and rooted it the day after, used it for a couple of days, before I installed elementalX. was happy with that for some days. then I decided I wanted to try out lineageOS, in order to de-google my self, in my quest for privacy.
TL;TR:
mtp is not working after flashing, neither is twrp, cant even access it through fastboot with booting the .img file.
does this have something to do with the a/b partition thing on these phones, perhaps?
I would guess that I flashed lineageOS the wrong way, and that is the issue, but since I cant access twrp, I cant restore and reflash the correct way.
more detailes below
--------------------------------------
backed up before installing elementalX, to have something to go back to, in case of failure
rebooted into twrp, and wiped everything, exept internal storage (i looked this up several places, prior to flashing, that this was the way to do it, so assumed this was the correct way)
flashed lineageOS 15.1
wiped dalvik and rebooted
took ages to boot, so figured id reboot again a couple of times, with no succsess
tried to boot to twrp, to restore back state prior to flashing, but ended up in lineageOS' own recovery.
tried to boot from fastboot, and reflash twrp
goes out of bootloader and screen turns black, led turns on, and nothing. tried waiting for a bit, but nothing seems to happen
have to manually turn of phone, and reboot. tried this several times, but same result.
after reboot i turned to the recovery to look after any solutions there, but nothing
started adb, just to check, and it says "device unauthorized"
sortof gave up, so figured I could atleast get going installing apks, but after downloading f-droid, I couldnt get it to install
found out this was some sort of permission issue, so had to move it to internal storage to get it to install
after installing some apks, I was going to transfer my contacts from my pc, but cant get mtp working..
if someone know a soulution to this, I would be really greatfull, as Im at a loss. cant seem to find anyone who has had a simillar issue..
You can always use EDL and MsmDownloadTool. Check that thread
thanks, will definetly check that out.
now it apears that I have another issue, the key for adb is no longer valid. i did get the prompt when I connected the usb, but that didnt appear to do anything. have tried to revoke it, reanable, reboot both phone and pc, also delete the keys on my pc. I have no root access anymore, so cant really enter the root on my phone, to pull out the keys there, neither can i push my own keys, as it seems atleast. I may be doing it wrong too, for all i know..
If you can enable debugging and see your phone with adb devices, you can adb push /sdcard/<romfile>.zip
I am able to enable debugging mode, yes. Will this enable me to push my own key, or any other existing key for that matter, to remove the unauthorized label?
Id also like to at that i done goofed when flashing lineageOS. Ive come to and understanding that I have to flash OOS 1.5.1 (i think that was it) on both slots, before then flashing the custom rom onto the device, and reflashing twrp after that. Which i did not do. I also were running pie at that time, so theres another mistake I made to begin with. Neither was I really aware of the concept of a/b partition system at hand..
Can i switch slots in fastboot, and then boot inton twrp, and reflash back to OOS 1.5.1, on both slots, and then reflash LOS 15.1? And ofcource reflash twrp and root afterwards, which totally slipped my mind..
I was trying to root my main driver, a Google Pixel 3 running the most recent version of Android. Initially I was going to flash TWRP and then install Magisk, but TWRP for some reason wouldn't flash, so instead I went about trying to go about the Magisk Canary route. I patched the boot image of the most recent Pixel 3 update and proceeded to flash that in the bootloader. That is when everything went wrong. When the phone rebooted, I found that my touchscreen was no longer working. I tried flashing the boot image using platform tools in the bootloader, but I deleted the -w line in flash_all.bat to prevent a full reset; however this did not solve the issue as I had hoped. I then went into device recovery mode and tried the factory reset option there, but that did not work either. The phone booted and I was in the setup screen with no way to press the buttons using the screen, so I connected an OTG USB device to set the device up only to find that the WiFi is not turning on. I believe there are issues with the mobile network as well as I put in a SIM card but it wan't able to connect to the network; however it did read the SIM card successfully as I was able to "turn on" mobile data. I cannot enable USB debugging to flash anything because I cannot allow the computer's USB debugging request; I either have the computer or my OTG device plugged in. Any ideas on what to do? Thank you in advance!
i have almost the exact problem.
could someone please help
Sounds like the option is, factory image flash-all with the wipe. I believe the OP did not disable/remove modules from magisk before updating. That is something that we all should be aware of at this point. Cost me two bootloops and complete resets, but I learned my lesson. Also backup your stuff. I lost a few pictures, but most of my data and such were restored through Tibu.
I got my Nokia 3.1 in a bit of a weird situation trying to flash the stock ROM. I feel like it's a lost cause, but since I can still boot in recovery mode, there may still be a solution, I will explain in case someone can help.
It started when I tried to update from Android 8.0 to 10.0 (none of the previous OTA updates had worked and would always reboot in Oreo 8.0). This time, it didn't work and got the phone stuck in a boot loop.
The phone is still under warranty, but because I bought it overseas and there's no Nokia care centre here is New Zealand, I had no option but trying to repair it myself.
A wipe/factory reset didn't help, but after changing the active slot from B to A (using fastboot), it booted again in Oreo 8.0. Only problem is that I could no longer start a fresh Oreo 8.0 install without updating first and since all updates failed, I was stuck.
I suspect slot B is damaged or corrupt, hence the impossibility to update. To check it, I switched back the active slot to B after a factory reset, and that was not a great idea, the phone wouldn't even boot and looked hard-bricked.
But I still managed to use SP tool to download firmware, so I did that with the original Nokia 3.1 stock ROM (ES2).
However, I could not flash all files, I'm not too sure why.
I had the error message:
ERROR: STATUS_SEC_INSUFFICIENT_BUFFER
Verified boot is enabled
Please download signed image (sutinfo-verified.img) or disable verified boot
I didn't know how to do either of these, so I skipped the three problematic files: sutinfo.img, systeminfo_a.img, and cda_a.img (not sure what they do?).
It worked and un-bricked the phone, but it now boots to recovery mode only. What puzzles me is that I also no longer have access to fastboot, even when I reboot to bootloader (as if it skipped bootloader and went straight to recovery). I suspect it is because it still boots on slot B but I don't know how I can check that or change it back to slot A without fastboot access.
I tried using adb: adb shell getprop ro.boot_suffix but although it can see the device, it failed because it says device is unauthorized. I've tried all the fixes for this I found, to no avail.
So that's where I am, able to boot to recovery (but with adb unauthorized), able to flash firmware (except those files that must be signed), and unable to access fastboot.
I'm giving up hope that it's repairable, but I'd love to at least understand what happened, if someone has any idea...
Sorry for the long story...