Related
Hi. I just upgraded from CyanogenMod 3.6.8.0 to 3.6.8.1 (I had a theme put on) and it gave me an error while updating. I used the Incremental Update package.
After that, I realized that I couldn't hear the people from the other end of the line,though the could hear me. Then I tried puting it in speaker, and it worked fine. The headphones also work.
I wiped the phone and installed CyanogenMod 3.6.8.1 from scratch, and nothing. I reupdated the radio to the latest, and nothing.
Any idea of what happened, or what should I do?
The Radio is 2.22.19.26I
Thanks in advance!
RSchmauk said:
Hi. I just upgraded from CyanogenMod 3.6.8.0 to 3.6.8.1 (I had a theme put on) and it gave me an error while updating. I used the Incremental Update package.
After that, I realized that I couldn't hear the people from the other end of the line,though the could hear me. Then I tried puting it in speaker, and it worked fine. The headphones also work.
I wiped the phone and installed CyanogenMod 3.6.8.1 from scratch, and nothing. I reupdated the radio to the latest, and nothing.
Any idea of what happened, or what should I do?
The Radio is 2.22.19.26I
Thanks in advance!
Click to expand...
Click to collapse
Have you tried downgrading your ROM to make sure it is something to do with 3.6.8.1?
I just did, still doesn't work.
RSchmauk said:
I just did, still doesn't work.
Click to expand...
Click to collapse
... hardware error? Are you sure that the ROM flashed correctly? Incomplete flashes can be a problem... Maybe try flashing RC29 and see if you get audio there. If you do, re-root and reflash the ROM that you actually want.
h.nocturna said:
... hardware error? Are you sure that the ROM flashed correctly? Incomplete flashes can be a problem... Maybe try flashing RC29 and see if you get audio there. If you do, re-root and reflash the ROM that you actually want.
Click to expand...
Click to collapse
I unrooted, and still doesn't work... Now I'm a little worried...
RSchmauk said:
I unrooted, and still doesn't work... Now I'm a little worried...
Click to expand...
Click to collapse
If it still doesn't work I would contact Tmobile, sounds like a dead ear speaker?
xsnipuhx said:
If it still doesn't work I would contact Tmobile, sounds like a dead ear speaker?
Click to expand...
Click to collapse
If it is (and your phone is not under warranty), the speaker is easy to replace. I have a second G1 with a bad speaker. Took me about 5 minutes to get it out (can do it in under a minute now that I have done it a few times).
The speaker is about 45 dollars on the internet (just google it).
I'm not sure how, but now it's working. I wiped and flashed the 3.6.8.0, but I had done that before, so I'm not really sure... Anyways, thanks, and I'm relieved it wasn't a hardware problem.
Hello!
Just today I bought myself a second-hand Oneplus 3T that had issues booting into the system. The start of the boot animation would show, but after that the screen just goes black and a white notification light turns on. Confident in my basic skills, I bought it and started trying things.
It boots into recovery and fastboot, all nicely, so first I tried wiping everything with stock recovery and then installing OOS that I downloaded from oneplus. Installed it through the stock recovery ADB Sideload, didn't change a thing. So since the bootloader is locked and cannot be opened, I went on to tryin the Qualcomm 9008 unbrick. Went through with it got a green text in MsmDownloadTool and all, but still nothing. Tried to install that same OOS on this "fixed boot partition" but the only change I noticed that I couldn't even get the start of the boot animation. Just the oneplus logo splash screen and black with white light after that....
If the device is powered down it shows the offline charging screen and a green notification light.
The device is out of warranty, I need the help of you people.... I might try installing twrp and formatting the system partition and installing on that, that is if I can get twrp installed in this kind of a situation.. Thanks!!
EDIT; Tried installing twrp, of course cannot flash it through fastboot but I also tried tricking MsmDownloadTool to install twrp instead of stock to no avail. I got the boot animation starting back but nothing else, also clicking "Install from internal storage" in recovery does absolutely nothing, doesn't bring up a file explorer like I would have expected..
Have you tried the Qualcomm MSMtoool to completely reinstall OOS? That may work. Don't try to install TWRP through the MSM tool.
This is an usual brick that takes place when someone has tried to relock the bootloader when a ROM/Recovery has been flashed which is not signed by OnePlus. It has been solved many times, so please do a search on XDA and OP Forums before posting a new question.
thes3usa said:
Have you tried the Qualcomm MSMtoool to completely reinstall OOS? That may work. Don't try to install TWRP through the MSM tool.
This is an usual brick that takes place when someone has tried to relock the bootloader when a ROM/Recovery has been flashed which is not signed by OnePlus. It has been solved many times, so please do a search on XDA and OP Forums before posting a new question.
Click to expand...
Click to collapse
Man I searched for this kind of brick for a few hours, only found a couple, one on xda and another on oneplus forums, and those didn't get solved. The MSM tool package I'm using does write the system.img so I guess it at least tries to install OOS.... Could you point me in the direction of similar brick situations? This doesn't get fixed by wiping any partitions..
Thanks!
MrMatson said:
Man I searched for this kind of brick for a few hours, only found a couple, one on xda and another on oneplus forums, and those didn't get solved. The MSM tool package I'm using does write the system.img so I guess it at least tries to install OOS.... Could you point me in the direction of similar brick situations? This doesn't get fixed by wiping any partitions..
Thanks!
Click to expand...
Click to collapse
I'm guessing you used this guide (https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) and you did install the drivers correctly yeah?
What error do you get when you MSM tool tries to flash the images? Is it the Sahara error?
Try another computer, or switch USB ports. Also try to download the firmware packages by yourself, and select it from the MSM tool. Also try to let the in-program download flash.
Try going into Fastboot and erase everything, from Internal Storage to the System partition, and then re-try the MSM tool.
thes3usa said:
I'm guessing you used this guide (https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) and you did install the drivers correctly yeah?
What error do you get when you MSM tool tries to flash the images? Is it the Sahara error?
Try another computer, or switch USB ports. Also try to download the firmware packages by yourself, and select it from the MSM tool. Also try to let the in-program download flash.
Try going into Fastboot and erase everything, from Internal Storage to the System partition, and then re-try the MSM tool.
Click to expand...
Click to collapse
Bootloader is locked, nothing can be done through fastboot. I get no errors in MSM, it's just this white light brick when booting to the system. I found a third guy on page 46 of that thread (that's a bit of reading) who had a similar sounding issue. He got it fixed by using a newer MSM version I believe. I am currently downloading the one he said he used. So far I've tried 2 diffrerent MSM packages so far. One other guy in that thread said that the white light should mean a kernel panic... I really hope I can get it working
How can I choose what firmware MSM installs? Or is that even what you mean by "download the firmware packages by yourself, and select ir from the MSM tool"?
I appreciate your help. This really is a frustrating kind of error.
MrMatson said:
Bootloader is locked, nothing can be done through fastboot. I get no errors in MSM, it's just this white light brick when booting to the system. I found a third guy on page 46 of that thread (that's a bit of reading) who had a similar sounding issue. He got it fixed by using a newer MSM version I believe. I am currently downloading the one he said he used. So far I've tried 2 diffrerent MSM packages so far. One other guy in that thread said that the white light should mean a kernel panic... I really hope I can get it working
How can I choose what firmware MSM installs? Or is that even what you mean by "download the firmware packages by yourself, and select ir from the MSM tool"?
I appreciate your help. This really is a frustrating kind of error.
Click to expand...
Click to collapse
As I'm aware, you can select packaged files which you have downloaded. It is basically the same file the MSM tool downloads, but it could be a higher version. (I.E: MSM tool downloads OOS 3.5.6 by default, but you could flash a file which you downloaded yourself, which can be OOS 4.0 or so.)
Correct me if I'm wrong, I've only used the MSM tool once or twice, and I'm speaking from reading about it on other threads.
Don't panic, your phone can get into fastboot and recovery, so you can definitely save it. Its just a little annoying, but it's not like its a Samsung device. I've myself had the white light. It can be easily fixed.
Supporting each other is what a community is for. Helping each other is what we do.
Good luck, and update us on what happens.
Update: Tried versions 3.0.6 and 3.0.8 of MSM in addition to the version 3.0.0 I had before. No luck. I'm starting to feel like I've tried everything there is to try... The device works everywhere else like it should, it just doesn't boot into system. Recovery and fastboot and Qualcomm mode are available, just can't seem to fix this with those... I need some help
It could be some sort of hardware damage. Following liquid ingress, my oneplus 3t had the exact same symptoms. The problem in my particular case happened to be with the board with audio jack on it at the bottom, I could use the phone normally (without hardware keys/fingerprint scanner) by disconnecting and blocking the two connectors for those components, until a replacement board arrived. The board cost me £8.50. There could be loads of reasons for this blank screen and white LED though, gluck mate!
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
bluuquthug said:
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
Click to expand...
Click to collapse
He said in OP he can't flash TWRP.
krombopulos said:
It could be some sort of hardware damage. Following liquid ingress, my oneplus 3t had the exact same symptoms. The problem in my particular case happened to be with the board with audio jack on it at the bottom, I could use the phone normally (without hardware keys/fingerprint scanner) by disconnecting and blocking the two connectors for those components, until a replacement board arrived. The board cost me £8.50. There could be loads of reasons for this blank screen and white LED though, gluck mate!
Click to expand...
Click to collapse
Yup, cannot flash twrp throguh ususal means... But you saying you had a similar problem, phone wouldn't boot with those parts connected, but did go just fine with them disconncted? If that's the case, I will start trying it with different parts. I really want to get this thing working! Thank you for both of your inputs!
bluuquthug said:
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
Click to expand...
Click to collapse
Yea... I got my bootloader locked so no luck there... Thanks anyway!
MrMatson said:
Yea... I got my bootloader locked so no luck there... Thanks anyway!
Click to expand...
Click to collapse
Yeah You need to UBL first bro, try via fastboot to flash twrp.
Im using msm tool first, then flashing OOS, next UBL
I don't think UBL will help either, as I am stuck on stock reocevoery.
Update: https://forum.xda-developers.com/general/rooting-roms/installing-twrp-locked-bootloader-t3669879 this guy seems to have succeeded in doing what I tried on a Xiaomi phone. I don't know if it's possible to replicate on a oneplus though... No luck so far
MrMatson said:
Yup, cannot flash twrp throguh ususal means... But you saying you had a similar problem, phone wouldn't boot with those parts connected, but did go just fine with them disconncted? If that's the case, I will start trying it with different parts. I really want to get this thing working! Thank you for both of your inputs!
Click to expand...
Click to collapse
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
my friend op3 also had similar problem, the problem only occur after changing camera module. change back to original faulty modules seems fixed the issue. after he order other camera module and assemble it back, the device worked normally, it seems that any hw dmg will prevent the phone from booting system.
krombopulos said:
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
Click to expand...
Click to collapse
Oh... As I have stock recovery, the back key can be used to go back, and it seems to work... Well, any hardware modifications will have to wait, as I do not have a T2 driver and there seems to not be a single one in stock in Finland anywhere, gotta wait out on one from china.... But maybe trying some other parts will work The navigation keys also light up briefly when booting, for a second or so. Thanks!
krombopulos said:
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
Click to expand...
Click to collapse
koax88 said:
my friend op3 also had similar problem, the problem only occur after changing camera module. change back to original faulty modules seems fixed the issue. after he order other camera module and assemble it back, the device worked normally, it seems that any hw dmg will prevent the phone from booting system.
Click to expand...
Click to collapse
Thanks to you, I have that tingling sensation of trying again! I hope this is not on the motherboard, everything else I can manage.... Just gotta survive the wait for my T2 screwdriver..... This is a nice feeling
MrMatson said:
Thanks to you, I have that tingling sensation of trying again! I hope this is not on the motherboard, everything else I can manage.... Just gotta survive the wait for my T2 screwdriver..... This is a nice feeling
Click to expand...
Click to collapse
Just curious, did the seller give you any information about why the device was bricked?
Cause if he was just trying to modifying the software without knowing what he was doing you should have resolved it by now, as MSM-download-tool does not show specific errors I assume it's able to write software correctly to the corresponding partitions but then something prevents it from booting up to android system, unfortunately the chances for any hardware related problem are definitely there, even very likely...
So if you bought the device assuming a software related problem but got a hardware defect it could look just the same from outside, only further possibilities I see is by having a look inside and even then you'll need some luck finding the issues...
Don't know if you have one of these little phone repair shops around but they're helpful sometimes getting advice about hardware, etc. also YouTube is a great resource for tutorials...
Just my 2 Cents, good luck
- hope you succeed in the end!
Sent from my OnePlus 3T using XDA Labs
Hello everyone! I am looking for a fix for my phone after updating to Android Pie. My Bluetooth microphone is low, as well as a wired headset volume. This was not the case before the update. I have restarted the phone, set the phone's audio to mono, and still low volume. My wife turned the volume all the way up on her phone and it doesn't matter. I even went to developer options and shut off the Bluetooth moderation setting.
Any suggestion short of rooting me would be much appreciated.
startreksuite said:
Hello everyone! I am looking for a fix for my phone after updating to Android Pie. My Bluetooth microphone is low, as well as a wired headset volume. This was not the case before the update. I have restarted the phone, set the phone's audio to mono, and still low volume. My wife turned the volume all the way up on her phone and it doesn't matter. I even went to developer options and shut off the Bluetooth moderation setting.
Any suggestion short of rooting me would be much appreciated.
Click to expand...
Click to collapse
Have you tried reflashing the full firmware? Backup everything (photos/music/videos/etc) and then reflash the entire firmware. It will fully reset/format the phone, but it should fix it. I had that problem from an OTA update in the past, and that was how I was able to fix it.
xfrobex said:
Have you tried reflashing the full firmware? Backup everything (photos/music/videos/etc) and then reflash the entire firmware. It will fully reset/format the phone, but it should fix it. I had that problem from an OTA update in the past, and that was how I was able to fix it.
Click to expand...
Click to collapse
Can you point me in the direction of a guide on how to do so? I am really reluctant to brick my phone, don't have a backup if this fails!
Thanks in advance!
startreksuite said:
Can you point me in the direction of a guide on how to do so? I am really reluctant to brick my phone, don't have a backup if this fails!
Thanks in advance!
Click to expand...
Click to collapse
So I bit the bullet, reflashed the firmware, and same problem. Bummer!
startreksuite said:
So I bit the bullet, reflashed the firmware, and same problem. Bummer!
Click to expand...
Click to collapse
Try the Rescue and smart assistance . I bricked my G6 and this program brought it back to life
Download page
AXng said:
Try the Rescue and smart assistance . I bricked my G6 and this program brought it back to life
Download page
Click to expand...
Click to collapse
Thanks, but that is what I used to reflash the firmware. Everything else pretty much works except for the low volume issue.
startreksuite said:
Thanks, but that is what I used to reflash the firmware. Everything else pretty much works except for the low volume issue.
Click to expand...
Click to collapse
Have you try a different version of stock firmware?
Moto G6
Hi folks,
I recently got a problem and by the things I already tried, if possible, only XDA can help me.
One day my pop up cam stucked out, so far so good, I got it back in with the Motor APK.
Now, the cam stucks in, and can't get out since I hear some crunchy noises from the motor.
When I press calibrate on the original MIUI 12.0.4.0 ROM it tells me "calibration failed".
While calibrating the cam moves properly, but then stucks in with the message above.
Xiaomi Repair Center didn't repair it because of "warranty got screwed due to water damage".
Which is clearly not true since I opened the device after that myself.
I got myself a new motor and put it in yesterday, but it didn't work.
So I dismantled the complete device on top, cleaned the camera parts and the camera holder and put all back together.
The phone works flawlessly but the damn motor, neither the old nor the new one are working and calibrating is still failing.
Please, do you guys have an Idea?
Thanks in advance.
I'm you're helper
If you're bootloader is unlock, flash orangefox recovery, download the latest persist.img in miui rom, flash persist.img (select persist_image)with orangefox recovery
Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?
Seems different?
Well I would try Odin and an official ROM anyway, no pain no gain right?
What exactly were you doing before this occured?
You try the old delete usb driver, restart computer, install usb driver then restart computer and restart phone and try again.
SirDigbyCC said:
Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?
Click to expand...
Click to collapse
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something
flairepathos.info said:
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something
Click to expand...
Click to collapse
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.
To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.
SapphireEX said:
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.
Click to expand...
Click to collapse
Oh I see the issue now you need to wipe all and re-flash full firmware when flashing the device using Odin
if that doesn't work flash the partitions with the kernel drivers and system partition
I had a similar issue with my current mtk phone and it was because the boot/preloader partition bilieved i had flashed the wrong firmware for my device(it was just a different firmware release for my phone
Just to be safe some ota updates break wehn the bootloader is not unlocked (when updationg from say android 8(oreo) -9(pie)...)
especially because of code errors in the update, cache/vendor partition being too full after downloading update
SirDigbyCC said:
To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.
Click to expand...
Click to collapse
If you're telling the truth, and it wasn't a bad module / firmware / etc, it is possible your eMMC got too hot and melted some solder. I've seen it happen before.
You'll want to diagnose everything you can. If you're on Windows, does it recognize a USB device or a COM device? If linux, does lsusb return anything useful about it?
If it's not being detected, and multiple wires doesn't change anything, are you able to access sahara mode / download / DFU? If so, go to those and try again.
If you are lying, and this is a bad firmware flash / OTA brick, you'll need to tell us otherwise we'll be going in circles.
So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?
SirDigbyCC said:
So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?
Click to expand...
Click to collapse
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.
SapphireEX said:
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.
Click to expand...
Click to collapse
I appreciate the vote of confidence, I don't think it was an OTA update that did it this time, it usually requests to do updates which I highly doubt I would have pocket approved through a flip case only short after pressing play on Spotify.
So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!
SirDigbyCC said:
So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!
Click to expand...
Click to collapse
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!
shriom_manerker said:
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!
Click to expand...
Click to collapse
It was free, turned out to be a hardware issue internally so I think covered by warranty as I have Care+ which has an excess of £40 which they didn't make me pay. They also replaced the screen due to some dead pixels, and the battery! Happy days!
Thanks all for your suggestions!