My in call volume is VERY low, it was working fine previously (a few days ago) but today, it has been almost impossible to hear anything, it is working but it definitely isn't possible to have a proper conversation.
So, I was attempting to get a train, and it was delayed by close to an hour, I needed to be somewhere, and my phone was impossible to use...
I tried rebooting, changing volumes etc. but nothing worked, I tried Googling and edited the ear volume in the mixer file, which seemed to improve it slightly when increased to 93. I then upped it again to 100. This caused the Audio FX program to crash, after every reboot I get constant notifications saying it has crashed. I cannot do anything on the phone itself.
How can I edit the file from my Mac, I have adb and fastboot and have used them before, but don't know how I can edit a system file, as I don't have root permissions from my laptop. How can I edit the file, is it possible to boot to AROMA without flashing, or edit the file from the command line from my mac? Or just stop the notifications so I can edit the file from my device itself?
Anyway, once that's fixed... I need to resolve the problem anyway. What can I do? It wasn't like this a few days ago, so i think it's more likely to be a hardware problem :/
I am assuming you are rooted and if so simply re-flash the rom and set everything back to normal
playya said:
I am assuming you are rooted and if so simply re-flash the rom and set everything back to normal
Click to expand...
Click to collapse
...Oh yeah, I didn't think of that. Where can I get the ROM from? I normally just flash them from my Mac, but I read that OnePlus took the ROM file down and made it difficult to flash, because people were doing it to the Chinese phones.
I can do it via Terminal or TWRP. Also, do I just leave off the -w flag when flashing?
what rom do you have stock? If so just search the forum and download it to your phone. If you only manipulated one file then find that file if you can and simply use adb to push it back to your phone and overwrite the one you have messed up.
7ewis said:
My in call volume is VERY low, it was working fine previously (a few days ago) but today, it has been almost impossible to hear anything, it is working but it definitely isn't possible to have a proper conversation.
So, I was attempting to get a train, and it was delayed by close to an hour, I needed to be somewhere, and my phone was impossible to use...
I tried rebooting, changing volumes etc. but nothing worked, I tried Googling and edited the ear volume in the mixer file, which seemed to improve it slightly when increased to 93. I then upped it again to 100. This caused the Audio FX program to crash, after every reboot I get constant notifications saying it has crashed. I cannot do anything on the phone itself.
How can I edit the file from my Mac, I have adb and fastboot and have used them before, but don't know how I can edit a system file, as I don't have root permissions from my laptop. How can I edit the file, is it possible to boot to AROMA without flashing, or edit the file from the command line from my mac? Or just stop the notifications so I can edit the file from my device itself?
Anyway, once that's fixed... I need to resolve the problem anyway. What can I do? It wasn't like this a few days ago, so i think it's more likely to be a hardware problem :/
Click to expand...
Click to collapse
Yeah thats where you messed up, the max value for in-call volume is 93. By having it above it, you're causing problems with the phone.
http://forum.xda-developers.com/oneplus-one/themes-apps/mod-volume-increase-mod-oneplus-one-t2835010
just flash that in recovery (adb sideload) and it should stop force closing.
playya said:
what rom do you have stock? If so just search the forum and download it to your phone. If you only manipulated one file then find that file if you can and simply use adb to push it back to your phone and overwrite the one you have messed up.
Click to expand...
Click to collapse
Yeah stock. When using push it tells me that it's a read only filesystem, is there a way I can use sudo to do this or something? It's rooted, and I have BusyBox installed.
7ewis said:
Yeah stock. When using push it tells me that it's a read only filesystem, is there a way I can use sudo to do this or something? It's rooted, and I have BusyBox installed.
Click to expand...
Click to collapse
its a system file I assume and if so you have to mount your system file prior to pushing it over. adb remount is the command or in recovery navigate to mount and check off system then use adb to push it to your phone. When done uncheck system and reboot
playya said:
its a system file I assume and if so you have to mount your system file prior to pushing it over. adb remount is the command or in recovery navigate to mount and check off system then use adb to push it to your phone. When done uncheck system and reboot
Click to expand...
Click to collapse
Thank you, that's very useful to know! I ended up flashing the zip file someone liked above, but it's always good to learn how to do things the proper way!
7ewis said:
Thank you, that's very useful to know! I ended up flashing the zip file someone liked above, but it's always good to learn how to do things the proper way!
Click to expand...
Click to collapse
I like your attitude :good:
zephiK said:
Yeah thats where you messed up, the max value for in-call volume is 93. By having it above it, you're causing problems with the phone.
http://forum.xda-developers.com/oneplus-one/themes-apps/mod-volume-increase-mod-oneplus-one-t2835010
just flash that in recovery (adb sideload) and it should stop force closing.
Click to expand...
Click to collapse
Ah okay, I thought it may have been 99 didn't realise it was 93! I flashed that and all it working again now, thank you!
Do you have any idea why the mic is doing this then? Even on 93 it was so quiet, unlike previous days where it appeared to be normal... Can't wait for them to push a proper OTA fixing all these bugs!
playya said:
I like your attitude :good:
Click to expand...
Click to collapse
Haha! I'll never understand why people want to use toolkits etc. to root, it's so easy to do it without, and you can learn what you are actually doing to your phone.
I just tried a call again, and it is still so quiet... If it's just me, then this must be a hw issue? I haven't changed anything and it's worse than before... Any ideas? I shouldn't have to manually adjust the speaker volume, even when I did it was quiet.
7ewis said:
Haha! I'll never understand why people want to use toolkits etc. to root, it's so easy to do it without, and you can learn what you are actually doing to your phone.
I just tried a call again, and it is still so quiet... If it's just me, then this must be a hw issue? I haven't changed anything and it's worse than before... Any ideas? I shouldn't have to manually adjust the speaker volume, even when I did it was quiet.
Click to expand...
Click to collapse
Which one did you flash from that page because I flashed the in call volume only zip a couple of days ago and it has helped. That's really the only thing I had issues with as far as volume
playya said:
Which one did you flash from that page because I flashed the in call volume only zip a couple of days ago and it has helped. That's really the only thing I had issues with as far as volume
Click to expand...
Click to collapse
I went back to the default, flashed the whole OS again, then tried flashing Default+ the one you have. It's still almost impossible to hear people, I could just manage it in a quiet room inside.
7ewis said:
I went back to the default, flashed the whole OS again, then tried flashing Default+ the one you have. It's still almost impossible to hear people, I could just manage it in a quiet room inside.
Click to expand...
Click to collapse
yea its funny sometimes with me its too loud then its not loud enough... LOL
it can be rather annoying
playya said:
yea its funny sometimes with me its too loud then its not loud enough... LOL
it can be rather annoying
Click to expand...
Click to collapse
I've contacted their technical support, honestly think it will be hardware unfortunately.
It's a shame because my screen and everything else is great!
I have the same issue, In Call Volume is too low and the phone its completely stock. :/
samarain said:
I have the same issue, In Call Volume is too low and the phone its completely stock. :/
Click to expand...
Click to collapse
Is it usable at all? I thought the volume was okay when I last spoke to someone on the phone, but it is definitely not usable at the current level.
May have to RMA this one
7ewis said:
Is it usable at all? I thought the volume was okay when I last spoke to someone on the phone, but it is definitely not usable at the current level.
May have to RMA this one
Click to expand...
Click to collapse
Check this first
http://forum.xda-developers.com/oneplus-one/help/speakerphone-volume-low-calls-t2801938
samarain said:
Check this first
http://forum.xda-developers.com/oneplus-one/help/speakerphone-volume-low-calls-t2801938
Click to expand...
Click to collapse
Are you referring to the acdb files? I haven't tried that yet. The mixer xml file edits haven't worked for me
7ewis said:
Are you referring to the acdb files? I haven't tried that yet. The mixer xml file edits haven't worked for me
Click to expand...
Click to collapse
Which ones did you try? They do work. Did you try? http://forum.xda-developers.com/oneplus-one/themes-apps/mod-volume-increase-mod-oneplus-one-t2835010
Related
Hi all,
Rumor has it I picked up a DEFY last week. Most people in the community know me for my work on the cliq/backflip/cliqxt. It's been quite some time since I posted any mods/work here on XDA so here we go. First I'd like to say thanks to Koush & Tenfar for the work they've done. They laid the ground work. I simply needed/wanted to improve on it more. I wanted to include the latest 2.5.1.x version since it has some bug fixes/new features also. So here you go. This recovery includes the latest 2.5.1.8 ClockworkMod Recovery, fixed fix_permssions script, and updated adb that allows root access when using adb shell. All your backups, downloads will reside in the clockworkmod directory on your sdcard just like a standard clockworkmod recovery. If you haven't noticed the fix_permissions script don't run properly via the recovery on the DroidX/Droid2/Defy. I simply fixed the script so it does work properly. Thanks again to both Koush & Tenfar. I'm looking into resolving the problem when you have USB debugging enabled you can't boot into recovery mode properly. This release still has that issue, just FYI. If you choose to use this version over Tenfar's, you'll need to un-install his version, install this one, & choose the option to install recovery once. After that, it's works the same way. Take care.
UPDATE: I've uploaded a new version to my 4shared as well as included it here. This new version simply adds a power off option to the menu & was a quick attempt to try to resolve the USB debugging option. I'll give it another try when I have time, until then, I hope you like having the option to power off your Defy from the recovery menu. I've also provided a link to the original version. Take care.
Steve, kb7sqi
Edit: Due to requests, I'm re-adding the link for this updated version. While I do have plans to come back to #android soon, until then, this will be unsupported by me till then. I'm glad it's been useful to others. Take care.
Latest Version:
Older version:
http://goo.gl/NtsTV
Steve
Great work! Will try it out asap.
installed seems to be working fine btw whats key test?
S1dew1nder said:
installed seems to be working fine btw whats key test?
Click to expand...
Click to collapse
It's does exactly what it sounds like. It simply returns the "key" value when you touch keys/buttons on your phone. It's handy if you're wanting to update a recovery to use certain keys if your phone has them. Perfect example, on the cliqxt the phone has a touch pad. So in the version I created for it, instead of needing to use the volume up/down, you could also use the touchpad for up/down/select as well. Take care.
Steve
kb7sqi said:
It's does exactly what it sounds like. It simply returns the "key" value when you touch keys/buttons on your phone. It's handy if you're wanting to update a recovery to use certain keys if your phone has them. Perfect example, on the cliqxt the phone has a touch pad. So in the version I created for it, instead of needing to use the volume up/down, you could also use the touchpad for up/down/select as well. Take care.
Steve
Click to expand...
Click to collapse
thanks for the answer dude, just did a back up with it all went well only diff was it made a new folder btw it will restore older back ups right?
kb7sqi said:
It's does exactly what it sounds like. It simply returns the "key" value when you touch keys/buttons on your phone. It's handy if you're wanting to update a recovery to use certain keys if your phone has them. Perfect example, on the cliqxt the phone has a touch pad. So in the version I created for it, instead of needing to use the volume up/down, you could also use the touchpad for up/down/select as well. Take care.
Steve
Click to expand...
Click to collapse
How can I can quit key test?
Power+VolUp results in a black screen.
pull the bat?
S1dew1nder said:
pull the bat?
Click to expand...
Click to collapse
that's what i did. but would've been nice to have long press (power button) to quit instead of battery-pull.
Ah, well, wouldn't need to use it twice anyway.
I'm gonna try restoring an older img, report back in a few.
S1dew1nder said:
thanks for the answer dude, just did a back up with it all went well only diff was it made a new folder btw it will restore older back ups right?
Click to expand...
Click to collapse
Yeah, you should be able to restore other nandroid backups.
racca said:
How can I can quit key test?
Power+VolUp results in a black screen.
Click to expand...
Click to collapse
You guys do know you don't have to pull the battery out right? You can hold down volume down button & hit the power button to turn the phone off while in the recovery. When you power the phone on, it'll boot up like normal. Take care.
Steve
Restore doesn't work. "can't find directory"
I will switch back to the old version
Andy
morphin said:
Restore doesn't work. "can't find directory"
I will switch back to the old version
Andy
Click to expand...
Click to collapse
try renaming the goapkrev folder on your sdcard to clockworkmod it should be able to find the directory then
S1dew1nder said:
try renaming the goapkrev folder on your sdcard to clockworkmod it should be able to find the directory then
Click to expand...
Click to collapse
You took the words right out of my mouth. I was just getting ready to type that. lol Thanks!
Steve
kb7sqi said:
You guys do know you don't have to pull the battery out right? You can hold down volume down button & hit the power button to turn the phone off while in the recovery. When you power the phone on, it'll boot up like normal. Take care.
Steve
Click to expand...
Click to collapse
ahhhhhh, i tried power+volup
thanks for the refreshment, and again for the great work!
now if only we can be rid of the annoying "debugging" bug.
racca said:
ahhhhhh, i tried power+volup
thanks for the refreshment, and again for the great work!
now if only we can be rid of the annoying "debugging" bug.
Click to expand...
Click to collapse
Thanks. I'm working on it. I got a little tired of rebooting my defy over 100 times yesterday when I was working on this. lol After I get my version done for the Motorola Charm, I'll get back to working on that.
Steve
kb7sqi said:
You took the words right out of my mouth. I was just getting ready to type that. lol Thanks!
Steve
Click to expand...
Click to collapse
lol np bud, btw is there any way to rename backup folders with out having a md5 miss match error?
S1dew1nder said:
lol np bud, btw is there any way to rename backup folders with out having a md5 miss match error?
Click to expand...
Click to collapse
i have no such problem ever. renaming always works and no such info is stored in the md5 file
do you think it could of happened because i edited the file name via my computer while my phone was in usb mass storage mode?
kb7sqi said:
Thanks. I'm working on it. I got a little tired of rebooting my defy over 100 times yesterday when I was working on this. lol After I get my version done for the Motorola Charm, I'll get back to working on that.
Steve
Click to expand...
Click to collapse
no pressure then, it's fine as it is.
i just need to remember, like really hard, to turn it off.
i wish i didn't make the same mistake not turning it off over and over again
S1dew1nder said:
do you think it could of happened because i edited the file name via my computer while my phone was in usb mass storage mode?
Click to expand...
Click to collapse
It's a good chance that could've caused it. I've had some wierd stuff happen doing things like that when in usb mass storage mode.
After installing the newest Virtuous Infinity (although I'm not sure if it is related to the rom), things were great.
After 3 or 4 days though, I woke up to my phone not responding. It almost seems as if the phone processor is running at 1/8th the speed. The touch screen doesn't seem to respond very fast, in fact, I can never get past the lock screen because it does not take my input in properly.
When I try to boot into Clockwork, the phone is stuck with only the clockwork icon there, and any key stroke will cause the phone to reboot again.
When I try to boot into the bootloader, the phone will either freeze and require a battery pull, or this image will come up ->
http://imgur.com/2zHLH
Therefore, when I hook up via USB, I cannot use fastboot to reflash the phone, since it seems to be stuck at that point on bootloader.
Any clue what's broken??
Thanks in advance!
Did you happen to have any zip files inside your sd card?
All the symptoms above seems to point at the sdcard as the problem.
try removing your sdcard and boot it up
thanks!
however, even after removing the sdcard, the phone is still messed up.
any other suggestions? what would be the best method of wiping and restoring the phone if i cannot get into the bootloader or recovery?
n3rdftw said:
thanks!
however, even after removing the sdcard, the phone is still messed up.
any other suggestions? what would be the best method of wiping and restoring the phone if i cannot get into the bootloader or recovery?
Click to expand...
Click to collapse
MAN! How weird! If it just started that out of the blue and was working fine before and you can't get into recovery either it sounds like you've had some kind of failure on the motherboard. You shouldn't have any problem swapping one with a hardware failure like that if that's actually what it is. I can't imagine ANYthing about a ROM that would do all that to one.
It COULD maybe be that your PG59IMG.zip file is corrupt & just stopping it. Can you delete & replace that file on the card and put it back in & reboot it?
n3rdftw said:
thanks!
however, even after removing the sdcard, the phone is still messed up.
any other suggestions? what would be the best method of wiping and restoring the phone if i cannot get into the bootloader or recovery?
Click to expand...
Click to collapse
what do you mean by still messed up? same exact issues as before?
mattlowry said:
what do you mean by still messed up? same exact issues as before?
Click to expand...
Click to collapse
yea, identical response from the phone
does this issue have anything to do with this ->?
http://forum.xda-developers.com/showpost.php?p=17384086&postcount=4
looks like something about how the phone looks for a list of PG54 files before boot is completed, any clues if that may be why my phone is dying?
n3rdftw said:
does this issue have anything to do with this ->?
http://forum.xda-developers.com/showpost.php?p=17384086&postcount=4
looks like something about how the phone looks for a list of PG54 files before boot is completed, any clues if that may be why my phone is dying?
Click to expand...
Click to collapse
This is what WeekendsR2Short is talking about.
WeekendsR2Short said:
MAN! How weird! If it just started that out of the blue and was working fine before and you can't get into recovery either it sounds like you've had some kind of failure on the motherboard. You shouldn't have any problem swapping one with a hardware failure like that if that's actually what it is. I can't imagine ANYthing about a ROM that would do all that to one.
It COULD maybe be that your PG59IMG.zip file is corrupt & just stopping it. Can you delete & replace that file on the card and put it back in & reboot it?
Click to expand...
Click to collapse
Riyal said:
This is what WeekendsR2Short is talking about.
Click to expand...
Click to collapse
Thanks Riyal. I get wordy sometimes.
**If replacing the PG59IMG file & rebooting DOES work, don't forget to go back & delete it or your system will find it and install it every time you reboot.**
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Maybe if you could give some more detail about what exactly you can and can't get the phone to do, what screens can be accessed, and what you did that lead to this condition, we could offer some advice.
Also, no offence to the devs, but twrp is the devil lol. Most issues I have had in the past have led back to it in one way or another, so I never use it. (Just my opinion)
Tappin G2 Style
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
scoobaspeaz said:
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Click to expand...
Click to collapse
Nope, my status us unlocked: 3. But when I get home, I'll try the mfastboot instead if fastboot.
kungpowchicken said:
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
Click to expand...
Click to collapse
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
bweN diorD said:
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Click to expand...
Click to collapse
Testing now.
UPDATE: Still no go.
kungpowchicken said:
Testing now.
UPDATE: Still no go.
Click to expand...
Click to collapse
Well that sux.
Your problem is different than what I made this for but I was hoping it would work for you.
What did it do, fail all the way through?
When I tested it on my phone it reported flashing the partitions ok. There was actually extra text displayed while it was doing it that I didn't put into the script, that's how I knew it was working.
Tappin G2 Style
Failed all the way.
kungpowchicken said:
Failed all the way.
Click to expand...
Click to collapse
im running out of suggestions
if you havent tried to put stock recovery back on yet, how about we try that and see what happens.
if you dont know how to do it through adb, just grab the 1.34 utility from the dev forum, it will push it through fastboot.
something is obviously wrong with twrp, maybe we can fix that first.
I tried flashing even the stock Recovery manually and through the 1.34 utility. Always comes up failed. :sad:
Did you try the manual steps that I posted in my links?
i hope that works, but im doubtful.
the utility essentially flashes exactly as you would manually.
he doesnt have a partition issue, im guessing something is wack with the permissions.
if twrp somehow screwed up the permissions to read only, i believe even the partition file cant overwrite it. i could be wrong.
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
kungpowchicken said:
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
Click to expand...
Click to collapse
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
penser said:
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
Click to expand...
Click to collapse
he defiantly has the right fastboot, its in the utility that has been downloaded thousands of times.
if its write protected some how, its not going to flash no matter how you try it.
what i was wondering is if recovery can fix permissions that deep, not sure he said he tried that.
What do you mean with recovery?
kungpowchicken said:
What do you mean with recovery?
Click to expand...
Click to collapse
go into twrp, advanced (i think thats the right section) and look for a line that says "fix permissions" and do it.
Keeps saying it can't mount anything.
kungpowchicken said:
Keeps saying it can't mount anything.
Click to expand...
Click to collapse
thats what i figured would happen
So I sold an unopened, sealed Nexus 5 to someone last night and he's having a problem activating the device.
Here is his description of what happened:
"I popped in the SIM card, the loading proceeded as normally. It said it was activating and then a box popped up saying that "android is upgrading system files" or something like that. It restarted and went back to the language selection screen. I pressed English, next and then it went to the connect to wifi screen, froze and then restarted before I could even connect. Now it just loads on the boot"
I had him boot into recovery and do a factory reset, but the result is the same. I had him do a 2nd factory reset just be sure, but again, same result.
My thought is the system upgrade didn't happen correctly and not is corrupted.
What's the best course of action? Can I use the WugFresh toolkit to flash stock and unroot, or would I have to do it through ADB since the phone can't boot into the system?
I don't want to leave the buyer hanging, he seems like a nice guy, but I'm just not sure how to proceed?
Use ADB and flash the factory image for him.
Synyster06Gates said:
Use ADB and flash the factory image for him.
Click to expand...
Click to collapse
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.
SeanPlunk said:
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.
Click to expand...
Click to collapse
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!
switchfo0t said:
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!
Click to expand...
Click to collapse
Hello, I am the buyer of this Nexus device. I was able to successfully do these steps above, and reload the stock image for the Nexus 5. However, I am still running into issues.
WITH SIM:
I was able to get to the home screen after the initial setup, sent a few test text messages to my Google Voice number successfully, and browse on Chrome for a little bit before the device froze and restarted. After it restarted, I let it load up again, tried setting up my Google account on the device, then it froze again. All of the freezing happens within 3-5 minutes of using the phone.
So I decided to go into the bootloader, and do a factory wipe/cache wipe, and proceed without having the sim card in. I was able to get to the wifi selection screen, select my router, but as soon as the keyboard was suppose to pop up, the device froze and restarted. I am now just stuck on the welcome screen.
Any ideas now?
---------- Post added 29th November 2013 at 12:45 AM ---------- Previous post was 28th November 2013 at 11:56 PM ----------
Update: So I'm not sure what happened, but I ended up locking the device through Wug's Nexus Toolkit, inserted my sim card, and proceeded to set up the phone normally. So far everything has been working perfectly fine. I can receive/send texts, make and receive calls, and do normal functions with the phone without it locking up and restarting. Fingers crossed it'll stay like this.
Any idea on why this would've happened in the first place with the device?
---------- Post added at 01:38 AM ---------- Previous post was at 12:45 AM ----------
Update 2: Well, I noticed that it will randomly reboot every half hour or so it seems. It's kind of random, but I'm not sure what else could be causing these random reboots. The phone itself is working fine, but I just started experiencing random restarts.
Are you still on the stock rom or custom?
neomorphix said:
Are you still on the stock rom or custom?
Click to expand...
Click to collapse
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
---------- Post added at 01:49 AM ---------- Previous post was at 01:48 AM ----------
Jaybot said:
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
Click to expand...
Click to collapse
It was working fine earlier. I put it on the charger and got it to about 50%, used it for a little bit, then bam. It froze, and restarted all over again. I can use the phone maybe 5 - 10 minutes before it starts to recharge. Sometimes It'll automatically reboot after even unlocking the device.
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.
Jaybot said:
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.
Click to expand...
Click to collapse
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.
neomorphix said:
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.
Click to expand...
Click to collapse
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.
Jaybot said:
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.
Click to expand...
Click to collapse
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.
neomorphix said:
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.
Click to expand...
Click to collapse
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.
Jaybot said:
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.
Click to expand...
Click to collapse
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Jaybot said:
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
Ok. This just sucks. But as with any mass produced product there is bound to be the ocasional issue.
neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.
theesotericone said:
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.
Click to expand...
Click to collapse
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.
Jaybot said:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
neomorphix said:
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.
Click to expand...
Click to collapse
Just saw that. OP by your earlier symptoms I rules out a stuck power button. With the new info I'd look into it further. If the phone is just looping over and over it could be a stuck power button, Mash the power button repeatedly for a minute. Then try and reboot. A few other people have had this on the N5 already and it's a notorious issue on some Samsung phones.
neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
If it comes to that, how do I go about transferring the warranty over?
I feel really bad, I just don't get it. I bought two of them, the other buyer hasn't had any problems. Both brand new, sealed, in the box. Go figure.
Greetings, everyone. So I got an OP6 a few days ago from someone I know and it has two problems - first one is that there is no sound at all from the phone, the speakers, the headphone jack, even audio through bluetooth don't work (when trying to play audio through bluetooth the phone starts lagging like hell). Second is, the fingerprint reader doesn't work too, there is no option in the system, only on the first setup screen (after a reset) where it doesn't work anyway.
The guy said it happened after an update. I tried re-flashing it many times because it kinda looks like like a software issue, but nothing help. Diffrent roms, stock or not, doesn't matter, tried unbrick tool, no luck aswell. Disassembled the phone in the end to check for water damage or loose cables, but even that didn't help, everything seems normal inside. And it's pretty wierd to have 2 separate things not working at all.
There is no official support for Oneplus in my country, the phone is imported so getting an official repair is not an option. Anyone got any idea what I should be looking into?
Thanks.
Guy you switch off the mute button over the power, press down and voil
Toni Moon said:
Guy you switch off the mute button over the power, press down and voil
Click to expand...
Click to collapse
Thanks for the advice, but don't you think I tried that before physically disassembling the phone?
Gottylol said:
Thanks for the advice, but don't you think I tried that before physically disassembling the phone?
Click to expand...
Click to collapse
Well.. we had people that didn't try it...so no point in thinking and skipping questions...
have you tried to reflash the whole stock rom with using fastboot images ?
I've got that problem too before, it's becaused I flash a stereo sound mod, and updating the software. and I lost all of my sounds.
Azhar_Fahry said:
have you tried to reflash the whole stock rom with using fastboot images ?
I've got that problem too before, it's becaused I flash a stereo sound mod, and updating the software. and I lost all of my sounds.
Click to expand...
Click to collapse
Interesting, did you not have any sound at all too? From the speakers as well as headphone jack?
But yes, I tried to flash from fastboot, even did the unbrick tool which seems like the best method to get a complete factory reset. I'm not sure if there's some part of the firmware that can still be corrupted even after flashing though the tool.
Gottylol said:
Interesting, did you not have any sound at all too? From the speakers as well as headphone jack?
But yes, I tried to flash from fastboot, even did the unbrick tool which seems like the best method to get a complete factory reset. I'm not sure if there's some part of the firmware that can still be corrupted even after flashing though the tool.
Click to expand...
Click to collapse
yep. no sound at all.
Btw here's the link that I use to unbrick my phone
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/page1
hope it helped.
Azhar_Fahry said:
yep. no sound at all.
Btw here's the link that I use to unbrick my phone
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/page1
hope it helped.
Click to expand...
Click to collapse
Thanks, I'll try again later just to make sure.
Sadly, didn't work again. Flashed all the partitions that can be flashed with that tool, but still got no sounds, so probably it's a hardware issue in the end, but it's hard to imagine what exactly is broken.