Got my phone right after the last update and I went to root it with superoneclick and it hasn't had sound now for about 3 months. Wondering if anyone knows what I can do. I've tried just about everything I could think of but for some reason my phone just doesn't seem like it interacts with the pc right.
halp.
Thanks in advance.
you said a failed root, so if it's still stock you might be able to bring it in.
depending on who your with they will take your phone, send it in, upgrade the firmware (or re-flash it if it is the newest) and send it back to you for free.
i had mine rooted and with a custom firmware on it, and bell still took it and flashed V11a for me.
if you plug headphones in do they work?
hope you get everything sorted out
Thanks, I'll see what I can do, although as I have service with AT&T I can only expect a long harrowing process with nil results. :/
Yes, when I plug in headphones/auxiliary cords it's fine.
lol yea...it only took 7 days to get my phone back...
it's interesting that your headphones work, and it wouldn't be physical damage, because you said it happened after trying to root it.
i would re-try to root it, or downgrade/upgrade your firmware to see if that works before sending it in (if you do that)
sorry i can't be of much help, good luck though
Related
Yesterday my roommate decided that he wanted to join the party and root his Evo after seeing the pure unfiltered awesomeness of mine, but he ran into a problem. While trying to flash a custom recovery he kept getting the an error message about a "bad block 000x0000010000" or something similar. So, unless I'm way off, I told him he must have bad handset hardware.
Well, he decided to take the phone back to the Sprint store and see if he could talk them into swapping one out due to the defect. They said no, because after running whatever tests it is that they do that there wasn't a reproducible problem. The sales person did say though, that if his phone were to "unexpectedly crash" then he would easily just replace it.
So... my question at this point, is there a way to get around this "bad block" error, or is there a way to brick the phone without it being obvious that anything voiding the warranty was done? I searched the forums about this error, but everything if found said they eventually got it to work by trying different recoveries, or they swapped out the phone. We have a tried a few different recoveries, but none are working and we have tried more times than I can count.
Its fraud. Nobody on this forum is likely to help you since its BS claims like that which caused the deductible to raide to $100.
I understand how one could see it that way, but the way my roommate sees it is that he was sold a bad device. I don't know, I'm not here to argue semantics nor ethics, I'm just wondering if anyone has some advice for the guy. We would prefer to just keep the phone if we can manage to get the device working the way we would like.
Intensentropy said:
Yesterday my roommate decided that he wanted to join the party and root his Evo after seeing the pure unfiltered awesomeness of mine, but he ran into a problem. While trying to flash a custom recovery he kept getting the an error message about a "bad block 000x0000010000" or something similar. So, unless I'm way off, I told him he must have bad handset hardware.
Well, he decided to take the phone back to the Sprint store and see if he could talk them into swapping one out due to the defect. They said no, because after running whatever tests it is that they do that there wasn't a reproducible problem. The sales person did say though, that if his phone were to "unexpectedly crash" then he would easily just replace it.
So... my question at this point, is there a way to get around this "bad block" error, or is there a way to brick the phone without it being obvious that anything voiding the warranty was done? I searched the forums about this error, but everything if found said they eventually got it to work by trying different recoveries, or they swapped out the phone. We have a tried a few different recoveries, but none are working and we have tried more times than I can count.
Click to expand...
Click to collapse
Have you tried flashing eng build and flashing recovery from bootloader?
we flashed the engineering build through the bootloader but not the recovery. The method we used to flash recovery was though adb. we'll take a look and see if we have any better luck. my roommate said that he read something about using fastboot, but I'm not sure about that. We'll give it a try.
Just be careful not to run out of power "accidentally" while flashing a new radio... that could have devastating effects on phone usage... "Hint... Hint..."
though i highly doubt that your friends problem lies with the phone itself... should try to redo all the steps... and if you can repeat the error post more details on here...
wrx4memp said:
Just be careful not to run out of power "accidentally" while flashing a new radio... that could have devastating effects on phone usage... "Hint... Hint..."
though i highly doubt that your friends problem lies with the phone itself... should try to redo all the steps... and if you can repeat the error post more details on here...
Click to expand...
Click to collapse
lol, we are running though the whole process again right now. Thanks for the suggestion, though we are trying to avoid such a devastating event.
Well... Thanks for all your suggestions! We got everything to finally work though. I don't know why I didn't think of it earlier but we tried the simple root method and let the automated process handle all the labor. We got the exact same error with this method, but the program recognized the issue and moved the recovery to a section with no bad blocks. Doing it manually didn't allow for us to chose a different section to write to. Donation can be expected from my roommate! Thanks for the great application!
So, before I start, I've been attempting to follow this guide http://forum.xda-developers.com/showthread.php?t=920876 (literally done it 7 or 8 times, word for word). The problem is, it wont work. I flashed LeeDroid's rom onto my phone, and I need to return to stock rom, as my phone needs repairs. Unfortunately, every time I do this, nothing seems to happen once the phone reboots. (It just returns to LeeDroid's rom). Any help would be greatly appreciated.
Hashed said:
So, before I start, I've been attempting to follow this guide http://forum.xda-developers.com/showthread.php?t=920876 (literally done it 7 or 8 times, word for word). The problem is, it wont work. I flashed LeeDroid's rom onto my phone, and I need to return to stock rom, as my phone needs repairs. Unfortunately, every time I do this, nothing seems to happen once the phone reboots. (It just returns to LeeDroid's rom). Any help would be greatly appreciated.
Click to expand...
Click to collapse
What's the reason your phone needs repair from htc? Mayb that's the reason it won't work...?
Physical reasons, not software related the microphone stopped working (its working fine now, but I'd rather not risk having it stuff up later) and the volume key is broken. They're mainly physical damage (possibly water damage, although I doubt it as I've never spilt water anywhere near it, or dropped it in water)
You can run the official ruu.exe on your pc, it will give you a stock rom and because your mic is broken i think they don't care what software u are running. Flashing this official ruu gives your phone the stock look and i think this will work for you.
MichDHD said:
You can run the official ruu.exe on your pc, it will give you a stock rom and because your mic is broken i think they don't care what software u are running. Flashing this official ruu gives your phone the stock look and i think this will work for you.
Click to expand...
Click to collapse
Thanks for that Mich. I know that as I have a hardware issue, they probably won't check the software, but I just wanted to make sure they don't have any reason to reject my claim.
Hello, so im a relative noob in the forums per say, by my post count, bt ive been stalking the xda forums since my HTC Touch Pro 2..Usually, with enough searching i can fix my problems on my own, bt I can't afford to break this fone..
Here is the story. (sry if im giving TMI) (THE ACTUAL QUESTION IS AT THE END. RELATIVE INFORMATION IS AS FOLLOWS)
I was content with my stock EL29 rom,bt I wanted to try the new ICS update. So, I manually updated to FF18 using this link:
http://android.clients.google.com/p...bbe3997e3067.SPH-D710_update_EL29_to_FF18.zip
I used QBKing's video's steps to update. Big shout out to him, btw.. So after i wanted to root to eventually flash a custom rom. So i rooted using sfhub's one click for FF18 :
http://forum.xda-developers.com/showthread.php?t=1721229
Now, i few days of reading later, i decided to install the recovery to start installing custom roms. However, my fone got a bit wet a few days ago from a thunderstorm video recording adventure and I couldnt install the recovery.
I plugged in my fone and it wasnt recognized by any of my three computers at home. I uninstalled and re installed the samsung drivers numerous times. Keep in mind that I had previously used sfhub's one click sucessfully, so it is unlikely to be a computer problem.
So a few days later my fone starts telling me that im charging it (or its overvoltage) when its nt even plugged in. Now, it wont even turn off. it restarts as soon as it turns off.
-------------
So basically, I have come to the conclusion that I have a hardware usb port phone problem. Now, since its rooted,just with a stock FF18 rom, will Sprint give me problems if its an obvious hardware problems?
Is there a way to unroot without plugging it into my computer? Im thinking mobile ODIN,bt i heard it cant flash modems? would that be a problem if im from a rooted FF18 going to EL29? Or shud I just go back to stock unrooted FF18?Or shud I just take it to Sprint and hope they dont check the phone software wise?
I wud appreciate multiple opinions or even confirmations of other ppls ideas. Bt thanks for reading all this.. Hope I didnt put u guys to sleep
Thanks for all the help in advance guys...u guys rock..
Solution
wsteeven said:
Hello, so im a relative noob in the forums per say, by my post count, bt ive been stalking the xda forums since my HTC Touch Pro 2..Usually, with enough searching i can fix my problems on my own, bt I can't afford to break this fone..
Here is the story. (sry if im giving TMI) (THE ACTUAL QUESTION IS AT THE END. RELATIVE INFORMATION IS AS FOLLOWS)
I was content with my stock EL29 rom,bt I wanted to try the new ICS update. So, I manually updated to FF18 using this link:
http://android.clients.google.com/p...bbe3997e3067.SPH-D710_update_EL29_to_FF18.zip
I used QBKing's video's steps to update. Big shout out to him, btw.. So after i wanted to root to eventually flash a custom rom. So i rooted using sfhub's one click for FF18 :
http://forum.xda-developers.com/showthread.php?t=1721229
Now, i few days of reading later, i decided to install the recovery to start installing custom roms. However, my fone got a bit wet a few days ago from a thunderstorm video recording adventure and I couldnt install the recovery.
I plugged in my fone and it wasnt recognized by any of my three computers at home. I uninstalled and re installed the samsung drivers numerous times. Keep in mind that I had previously used sfhub's one click sucessfully, so it is unlikely to be a computer problem.
So a few days later my fone starts telling me that im charging it (or its overvoltage) when its nt even plugged in. Now, it wont even turn off. it restarts as soon as it turns off.
-------------
So basically, I have come to the conclusion that I have a hardware usb port phone problem. Now, since its rooted,just with a stock FF18 rom, will Sprint give me problems if its an obvious hardware problems?
Is there a way to unroot without plugging it into my computer? Im thinking mobile ODIN,bt i heard it cant flash modems? would that be a problem if im from a rooted FF18 going to EL29? Or shud I just go back to stock unrooted FF18?Or shud I just take it to Sprint and hope they dont check the phone software wise?
I wud appreciate multiple opinions or even confirmations of other ppls ideas. Bt thanks for reading all this.. Hope I didnt put u guys to sleep
Thanks for all the help in advance guys...u guys rock..
Click to expand...
Click to collapse
Now, I haven't had this problem, but on my old moment, what I did was flash it back to an old version of Stock (say EL29 [on this phone use MobileODIN]), then try to apply the OTA update, or even download the OTA update files and place them on your SD card and try that way. Then you phone would look stock when you take it in, just make sure have a battery as full as possible.
thanks for the suggestion. I ended up bringing it to Sprint and as soon as I left my car, the power button stopped working for some reason.
They ended up focusing on that and ordered me a replacement phone. I guess since it was still on the stock rom, they didnt realize it was rooted.
So, my phone reset itself randomly today and I noticed it was unable to turn on Wi-Fi for some reason. I uninstalled an app I've had for a long time called Power Toggles as I know it also can turn on/off the Wi-Fi (to make sure the phone and it weren't fighting) and I got the idea to check the root using Root Checker. Turns out, it failed . . . So something funny is going on.
I have not knowingly taken any type of update but every once in a while, my phone has tried to update and then said it aborted it due to suspected root. Not sure if that's what happened this time around as it happened while it was in my pocket (or at least it was working before I put it away and then later on, it basically stopped working and just seems to continuously reboot for funsies).
I tried rooting my phone using Kingoroot, an LG one click method (both script and GUI) with no luck. I've never had trouble rooting my phone, especially with one click roots before! I reinstalled LG drivers, disabled and re-enabled USB debugger, switched between MTP and PTP connections, etc. I can't seem to get it to recognize the phone. When doing one root method though, it reminded me to accept the RSA fingerprint and I realized that my phone is not asking me for the RSA fingerprint for my computer. I even tried revoking previous fingerprints and no luck there either. So I'm not sure what might be repressing that option but I'm assuming that's the "root" of my rooting issue.
Anyway, does anyone know
a) why my phone would suddenly be acting this way (I think I read someone else had similar symptoms in one of the one click root forums. Tried searching for more mentions but the website seems to be halting and letting me know the issue has been sent to administrators or something to that effect).
b) how do I solve this?
Below is what I'm running:
Android Version
5.0.1
Kernal Version:
3.4.0
Build Number:
LRX21Y
Software Version:
D85021I
Security Software Version:
MDF v1.1 Release 2
I have a TWRP backup made from quite a while ago (possibly a year ago) so i can try and utilize that but I'm not sure if that will do me any good if I can't root my phone first. I don't want to do anything out of desperation that's going to put me into more trouble down the road. At least as of now, my phone boots up correctly (even if it does seem to reset fairly regularly and has a constant battery drain from trying to turn on the wifi).
Any help you guys can give me would be greatly appreciated. Hopefully, I won't just have to buy a new phone . . . Thanks in advance!
Turns out Bluetooth no longer works either. Just thought that might be worth mentioning.
http://forum.xda-developers.com/lg-g3/help/wi-fi-bluetooth-fm-radio-d855-t3284582 Old problem, not much that can be done :|
jbrookley said:
So, my phone reset itself randomly today and I noticed it was unable to turn on Wi-Fi for some reason. I uninstalled an app I've had for a long time called Power Toggles as I know it also can turn on/off the Wi-Fi (to make sure the phone and it weren't fighting) and I got the idea to check the root using Root Checker. Turns out, it failed . . . So something funny is going on.
I have not knowingly taken any type of update but every once in a while, my phone has tried to update and then said it aborted it due to suspected root. Not sure if that's what happened this time around as it happened while it was in my pocket (or at least it was working before I put it away and then later on, it basically stopped working and just seems to continuously reboot for funsies).
I tried rooting my phone using Kingoroot, an LG one click method (both script and GUI) with no luck. I've never had trouble rooting my phone, especially with one click roots before! I reinstalled LG drivers, disabled and re-enabled USB debugger, switched between MTP and PTP connections, etc. I can't seem to get it to recognize the phone. When doing one root method though, it reminded me to accept the RSA fingerprint and I realized that my phone is not asking me for the RSA fingerprint for my computer. I even tried revoking previous fingerprints and no luck there either. So I'm not sure what might be repressing that option but I'm assuming that's the "root" of my rooting issue.
Anyway, does anyone know
a) why my phone would suddenly be acting this way (I think I read someone else had similar symptoms in one of the one click root forums. Tried searching for more mentions but the website seems to be halting and letting me know the issue has been sent to administrators or something to that effect).
b) how do I solve this?
Below is what I'm running:
Android Version
5.0.1
Kernal Version:
3.4.0
Build Number:
LRX21Y
Software Version:
D85021I
Security Software Version:
MDF v1.1 Release 2
I have a TWRP backup made from quite a while ago (possibly a year ago) so i can try and utilize that but I'm not sure if that will do me any good if I can't root my phone first. I don't want to do anything out of desperation that's going to put me into more trouble down the road. At least as of now, my phone boots up correctly (even if it does seem to reset fairly regularly and has a constant battery drain from trying to turn on the wifi).
Any help you guys can give me would be greatly appreciated. Hopefully, I won't just have to buy a new phone . . . Thanks in advance!
Click to expand...
Click to collapse
Well ok, you have that TWRP backup, how about accessing TWRP?
Can you enter recovery?
Does it display your IMEI in system settings, what does it do when you try to enable wifi?
Can you make backup of your current ROM in TWRP, then try to restore the old one, try restoring only system partition if the backup was made on same Android Lollipop 5.0.1. ?
Well, I was able to get into recovery and run an old image but it appears to have the same issue. My IMEI is fine (I did a full backup including IMEI but it had a valid IMEI before as well) so that wasn't the issue. Looking at that other thread someone posted, it looks like my phone is just screwed and this is a well known issue. It looks like people were able to fix it by replacing the motherboard, which is obviously not an option for me. If that's the case, I'm guessing this is my first and last LG phone. I've never had this kind of issue with a Samsung. In fact, I'm now back on an old S4 until I can figure out what to do. Not sure what phone to get at this point.
Natus, to answer your question, the Wi-Fi icon just kinda goes in a loop like it's trying to start it up. Opening up the Wi-Fi menu has it say it's starting up the Wi-Fi but never gets there. Unfortunately, it eats up battery fast, heats it up quickly, and eventually restarts.
I'm open to any other ideas but I'm guessing it's a hardware problem at this point. Thanks for the info, everyone! I do appreciate the help!
If you have any suggestions for a new phone, I'm all ears. Trying to stay out of a payment plan so I'm looking at the Nexus 6P but I'm wondering if there's one coming down the pipeline I might want to hold off for. I'd rather buy directly from the manufacturer than go through AT&T, given the option. Might need to start a new thread for that one though . . . Thanks!
jbrookley said:
Well, I was able to get into recovery and run an old image but it appears to have the same issue. My IMEI is fine (I did a full backup including IMEI but it had a valid IMEI before as well) so that wasn't the issue. Looking at that other thread someone posted, it looks like my phone is just screwed and this is a well known issue. It looks like people were able to fix it by replacing the motherboard, which is obviously not an option for me. If that's the case, I'm guessing this is my first and last LG phone. I've never had this kind of issue with a Samsung. In fact, I'm now back on an old S4 until I can figure out what to do. Not sure what phone to get at this point.
Natus, to answer your question, the Wi-Fi icon just kinda goes in a loop like it's trying to start it up. Opening up the Wi-Fi menu has it say it's starting up the Wi-Fi but never gets there. Unfortunately, it eats up battery fast, heats it up quickly, and eventually restarts.
I'm open to any other ideas but I'm guessing it's a hardware problem at this point. Thanks for the info, everyone! I do appreciate the help!
If you have any suggestions for a new phone, I'm all ears. Trying to stay out of a payment plan so I'm looking at the Nexus 6P but I'm wondering if there's one coming down the pipeline I might want to hold off for. I'd rather buy directly from the manufacturer than go through AT&T, given the option. Might need to start a new thread for that one though . . . Thanks!
Click to expand...
Click to collapse
I'd wait for note 7 or even iphone 7 =]
I've tried searching around here for an answer, but I haven't really been able to find anything solid regarding the issue that I'm experiencing. The other day I popped my sim card into my sgh-i467, as I do from time to time, to check for any OTA updates. This device is usually mounted in my vehicle, so I don't regularly check for updates. Sure enough, an OTA update was available. Tablet was at maximum charge, so I went ahead and chose to do the update. Unfortunately, the update failed at around 93% and went into a boot loop. There was nothing crucial on the device, so I figured it'd be no big deal to just re-flash the firmware if need be. However, I can only seem to find a KIES image for 4.1.2, and while I didn't think to verify exactly what version I was on before the bootloop/brick, I'm fairly certain I was on 4.2.xx.
From what I understand, the bootloader updates with 4.4, correct? With the bootloader getting updated, downgrading to 4.1.2 isn't possible or feasible, right? I didn't think to confirm this before I attempted to flash the KIES image for 4.1.2 via odin (kies never seems to actually see my device), which fails every attempt. I was originally able to get into recovery, but I kept seeing that /system wasn't found. I'm assuming that the OTA update partially installed, before failing, and either corrupted the partition scheme or updated the bootloader but not the system?
I'm dead in the water at this point, and AT&T is obviously no help. Plus, I don't the device on contract with them anyway, so I'm starting to think that my only option is to contact Samsung. However, I really don't want to have to send the unit in, and given it's age, I don't think it's worth investing anything in it if the repair isn't covered somehow. Plus I enjoy tinkering, I'm not new to the scene, and I'd really like to come up with a solution that doesn't require Samsung.
I don't suppose any kind people out there have any suggestions, similar experiences, etc. do they? I'd really like to hear from anyone who's got something to offer! Thanks in advance for your help!
pbrady5 said:
I've tried searching around here for an answer, but I haven't really been able to find anything solid regarding the issue that I'm experiencing. The other day I popped my sim card into my sgh-i467, as I do from time to time, to check for any OTA updates. This device is usually mounted in my vehicle, so I don't regularly check for updates. Sure enough, an OTA update was available. Tablet was at maximum charge, so I went ahead and chose to do the update. Unfortunately, the update failed at around 93% and went into a boot loop. There was nothing crucial on the device, so I figured it'd be no big deal to just re-flash the firmware if need be. However, I can only seem to find a KIES image for 4.1.2, and while I didn't think to verify exactly what version I was on before the bootloop/brick, I'm fairly certain I was on 4.2.xx.
From what I understand, the bootloader updates with 4.4, correct? With the bootloader getting updated, downgrading to 4.1.2 isn't possible or feasible, right? I didn't think to confirm this before I attempted to flash the KIES image for 4.1.2 via odin (kies never seems to actually see my device), which fails every attempt. I was originally able to get into recovery, but I kept seeing that /system wasn't found. I'm assuming that the OTA update partially installed, before failing, and either corrupted the partition scheme or updated the bootloader but not the system?
I'm dead in the water at this point, and AT&T is obviously no help. Plus, I don't the device on contract with them anyway, so I'm starting to think that my only option is to contact Samsung. However, I really don't want to have to send the unit in, and given it's age, I don't think it's worth investing anything in it if the repair isn't covered somehow. Plus I enjoy tinkering, I'm not new to the scene, and I'd really like to come up with a solution that doesn't require Samsung.
I don't suppose any kind people out there have any suggestions, similar experiences, etc. do they? I'd really like to hear from anyone who's got something to offer! Thanks in advance for your help!
Click to expand...
Click to collapse
You need to upgrade to keis 3.0 and reboot, then start kies, then boot note into download mode and have kies detect and reload the update.
Too bad you let the Note update to Kit Kat, Jellybean is better, on the LTE Note.
gooberdude said:
You need to upgrade to keis 3.0 and reboot, then start kies, then boot note into download mode and have kies detect and reload the update.
Too bad you let the Note update to Kit Kat, Jellybean is better, on the LTE Note.
Click to expand...
Click to collapse
Thank you very much for the information! Unfortunately, I've tried Kies 3.0. It notifies me that my device isn't compatible with Kies 3.0. With the other version of Kies, 2.6 maybe(?), it never ends up being able to connect. I've tried manual initialization, but when after I enter my model number, it won't accept my serial.
Take it to a BEST BUY with a Samsung Experience Center (Kiosk (Most all of them in larger cities have them) and they will fix your SGH-i467 for free. I did almost the same exact thing as you (trying to solve a EFS problem) and was stuck. I have posted about it on here before. They will not charge you BUT you may run into a clueless rep now and then. If you do, ask them to call for help and they will get you fixed up in a hurry. Hope this helps.