Related
Update Failure from 45.2.7 to 45.3.6 SOLVED!!!!
LOTS of people who purchased NEW Photons in the past few weeks have phones that shipped with a faulty image from the factory. These phones shipped with Software Version 45.2.7, but are ABSOLUTELY UNABLE to upgrade to 45.3.6. Anytime you try to update, the installation stops at 30% and quits. The common error message has something to to with the AccountAndSyncSettings.apk file.
I've figured out a FIX to the update failure. It may seem like it's a bit risky, but if you're on the last day of the 14 after initial purchase when you can swap out the phone no questions asked, it's worth a try. Actually, it's pretty simple without a lot of heavy lifing. Keep in mind, the phone this worked on had very few apps installed and was NOT rooted. I work in the IT field, but have NEVER done any modding - and I found it quite easy to do.
Some Background: My phone was purchased NEW direct from Sprint on 10/08/2011. It came with software version 45.2.7. When attempting to upgrade to 45.3.6, I received the now infamous error that has something to do with the AccountAndSyncSettings.apk file. Tried EVERYTHING the first few days with the phone - no upgrade success (about 15 factory resets). Made multiple posts on this board and read all of the responses for days. NO UPDATES from Sprint or Motorola. So, I took the phone back to a Sprint store for a 'no questions asked within 14-days exchange'. Never activated email, didn't even sync my contacts. Just went straight to the update. The new phone was also a 45.2.7 Software Version phone, and as you can probably guess, Update Failed on the 2nd phone as well. Went to THREE Washington, DC area Sprint authorized repair facilities to see if they can 'manually' update the phone, or even re-image the phone. Sprint was USELESS!!! Not only did the 'technicians' (and I use that word VERY loosely) not know anything about our problem, they had NO means to manually apply an update or write a new base SBF (system boot file) to the phones. Finally, after sitting in traffic coming home from work today, I had reached my breaking point.
The Fix: After days of scouring websites and phone calls to Motorola and Sprint (those were nothing more than a waste of cell minutes), I figured maybe I could mess with it myself. I had been hesitant because I was afraid of 'bricking' the Photon and then I'd have nothing more than a $200 paperweight. Then it hit me. What if it was already 'bricked'? Somebody has had to have done it to their Photon already. If they had, they must have looked for a solution. If there was a 'recovery solution' for a bricked Photon, maybe that fix may solve the problems we are all having with our BRAND NEW Photons.
Searching last night, I found a link from a few months ago. As a new member, I'm not allowed to post the link. But if Google these exact words, the VERY FIRST return is a page from the AddictiveTips website.
Came home from work, poured myself a cocktail and I went to work. First I downloaded the SBF. Now this takes the phone back to the version PRIOR to 45.2.7 (sorry, forgot to write that down when taking my notes). When you follow the link to download the SBF, there are a bunch of link options. Some have been taken down, others are still working. The file you want to download is 471MB and has this filename:
1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US
Then I downloaded the RSDLite software and drivers. I used a 32-bit Windows 7 laptop and installation went without a hitch. There are 64-bit drivers, but I'm not sure how they work. I did read where 'some' people had problems with the 64-bit varieties, so that's why I made a point of doing it on a 32-bit PC. From there, the instructions on the above listed link worked PERFECTLY.
There are a few things to keep in mind. BE PATIENT. This does take a while, and there were a few times that I wondered if something went wrong. It may hang at some stages for a few minutes, be patient.
Once I flashed the phone with the SBF and it was done installing and rebooting, (much to my amazement) all of my apps and customizations were in tact. I pulled my SD card to be safe, but I suspect it wouldn't have messed up my SD card. I would pull it prior to flashing just to be safe. If you want to take one extra step just to ensure success, you could do a factory Reset PRIOR to doing the flashing. I didn't have to, but it probably wouldn't hurt.
Literally seconds after it booted into the OS for the first time post SBF flashing, I was alerted to a software update: Update 45.2.7 (6.5MB). Downloaded rather quick and promted me to install now or later. I pressed install and away it went. Once again, be patient. It takes a few minutes. The progress bar moves rather steadily until it reaches 75%. Then it appears to stall/hang there for a few minutes. Then, the install progress bar vanishes and the OS boots up. A few seconds later, I got the message "Software update was successful. Your phone has been upgraded to 45.2.7". I went to SETTINGS, ABOUT PHONE, SYSTEM UPDATES and queried for additional updates. Sure enough, 45.3.6 was available. Forgot to document the file size. Downloaded and clicked INSTALL. Much like the previous update, progress moved steady till about 75%. Then progress bar and Android character vanished and the phone booted into the OS. About a minute later, the words I have been looking for for over a week:
"Software update was successful. Your phone has been upgraded to 45.3.6"
Queried software update again, and it said your phone was UP TO DATE. Yipee!!!!
I was getting NO SOUND. I think it was beause I inserted the SD card while the phone was still powered on. So, I rebooted the phone and EVERYTHING works perfectly.
If you want to wait for Mark (forum manager) to come up with a fix, I understand. In fact, it's probably the right thing to do. But if you're beyond frustrated (like I was) in the lack of information and lack of solutions from Sprint or Motorola; and want to take matters into your own hands; this worked for me.
do u happen to have a link for the 64 bit drivers ?
I'm unable to locate one.
Thanks for your help.
daddymikey1975 said:
do u happen to have a link for the 64 bit drivers ?
I'm unable to locate one.
Thanks for your help.
Click to expand...
Click to collapse
See here.
http://forum.xda-developers.com/showthread.php?p=18642169
This method has been on XDA for some time. The sbf of 198_6 was even posted way before Motorola started to push it out. Just takes a peek into the dev section.
Glad you got it working.
Thanks!
This has worked for me.
I just followed the instructions.
@OP - Thank you so much! I had a slow, laggy Photon with the "Sleep of Death", and needed to get it to update so that I wouldn't experience that issue anymore.
I followed your instructions, and got the phone working again. At one point, I wanted to throw the phone at a wall.
Now, I love my MoPho.
Thanks for making me fall in love with my phone all over again!
By the way, you are a Junior Member, this is your first post, and I gave you your first thanks. You are very intelligent, I must say! I am very proud of you. Your first post, and you did something this amazing! I must say, you are a genius! You will make a great Senior Member, it takes time to become a Senior Member, and you will make a great one! Very proud of you. Thanks a lot! I really appreciate it !!!
Motorola has re-issued the 198_6 build to address this problem. Also, 198_7 is available in the MoPho dev subforum
tbhausen said:
Motorola has re-issued the 198_6 build to address this problem. Also, 198_7 is available in the MoPho dev subforum
Click to expand...
Click to collapse
Well for me it does not fix....still the same old fail at about 30% install
Sent from my MB855 using XDA App
After failing 4 dozen times, I can happily report that the update FINALLY works!
HAPPY HAPPY JOY JOY!!
Riggy
I'm glad that it works. I used the same method, had a few issues but eventually got it to work.
Fyi...the NEW ota still did not work for me....spoke to sprint who spoke to moto tech support....moto wanted me to send them the phone (and be without a phone for week while they played around...sad moto..very sad)
Sprint is replacing my phone for free..good on Sprint
As for moto..this will be my LAST! moto phone..their service on this whole issue has been bad...and the joke of a support forum and "Mark" motos party line [email protected]%$!!!!...kiss my
... bye
Sent from my MB855 using XDA App
Hi Everyone,
This is my wife's phone, so i'm not very familar with it. She handed it to me today saying to won't boot. If connected to a charger, the screen would come on saying "RDS protocol starting..." and "Battery too low to flash".
After doing a little research her, I asked her if it had asked to do an update. She said yes, but that she's been hitting "no". So i guess it's been asking her for a while. I'm assuming she either hit yes, or it went ahead and did a force install anyway.
I took it to Sprint and they told me there was nothing they could do but replace it, which they have ordered the replacement, but that they cannot recovery anything from the internal memory (pictures, contacts, etc). So all I need to do is get the phone working enough to get data off of it, if at all possible.
The phone has NEVER been rooted. The bootloader is NOT unlocked. She's never let me touch it before.
I have no idea what version it was on (think it was 2.3.4) nor what version the OTA was trying to install.
I recharged the battery a little using a usb cable with the end cutoff and attached the red/black wires to the +/- pins. (about 30 mins or so). The "Battery too low to flash' message is gone and the phone is recognized in RDS Lite (good sign I hope).
Can I just flash "1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US.zip" to it using RDS Lite? Or should I use a later version like 198_7? I downloaded the 154_5 from http://forum.xda-developers.com/showpost.php?p=20331570&postcount=3)
I eagerly await a helping hand.
Thanks,
EB
Hmm, it varies.
I will try to help you, when I will get some more time today.
peetr_ said:
Hmm, it varies.
I will try to help you, when I will get some more time today.
Click to expand...
Click to collapse
Thanks.. looking forward to hearing from you. All I really need is to be able to get pictures and contacts off of it.. and perhaps SMS history. I don't care if any of the services work, since Sprint is sending us a replacement phone.
Euclid's Brother said:
Thanks.. looking forward to hearing from you. All I really need is to be able to get pictures and contacts off of it.. and perhaps SMS history. I don't care if any of the services work, since Sprint is sending us a replacement phone.
Click to expand...
Click to collapse
I thought I remembered seeing somewhere where there is a way to block this update from installing
but i cant find it ( i tried lol)
can you or someone please tell me how to do it
i keep hitting later but ive read that at some point it can just download and install anyways and i really dont want that
thanx
Modo-mopho said:
I thought I remembered seeing somewhere where there is a way to block this update from installing
but i cant find it ( i tried lol)
can you or someone please tell me how to do it
i keep hitting later but ive read that at some point it can just download and install anyways and i really dont want that
thanx
Click to expand...
Click to collapse
Contacts are synced to googles servers, so that's not a problem. As far as pictures, were they on the sd card or internal phone storage? If on sdcard, just put the card in a card reader on a laptop or pc. Or you may be able to install bootstrap recovery and mount either internal or sdcard. Or, if you were on 2.3.4, flashing any of those sbfs will work.
You can block the update by changing a line in the buildprop. But that would require being rooted. Id sbf then do the update immediately after since she obviously doesn't care about root or unlock.
Thanks.. I'm sure the pictures are on the internal sdcard. It's the pictures taken by the camera over the past few months. I already have older ones copied to my PC.
peetr_ sent me a custom sbf for an unlocked bootloader + twrp. I'll try that when I get home to see if i can get into that way. (Thanks peetr_)
I'll keep everyone posted.
What line in the build.prop file do I change?
Sent from my MB855 using xda app-developers app
Modo-mopho said:
What line in the build.prop file do I change?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Can't remember ill try to find out for ya.
HUGE thanks to peetr_ for all the help he gave me. I managed to get it booted into Electrify and saved everything I needed. *whew*
I now believe the whole issue was not a failed update, but a sticky volume button that's causing it to go to RSD mode. Whenever I power it down, then backup, it always goes direct to RSD mode. But then I can pull the battery, put it back in.. then hit the non-volume side of the phone against the heel of my hand (fairly hard) 5 or 6 times, then power it on, and it boots normally. Then while it's running, I'll see the volumne adjust up and down randomly.
Then if i reboot it, it's back to the RSD mode.
It doesn't work every time, but I've managed to boot it several times like that.
Hello guys!
For about 2 or 3 weeks now I have the problem that the speaker on my TF201 does not work anymore. Headphones are working fine.
It also does not recognize any USB Sticks anymore. The Dock is not dead, it works fine and also has current on the USB Port (the USB stick LED is activated but does not blink for accessing it). Also the SD Card slot does not work anymore. The MicroSD slot on the tablet itself works fine...
And the next thing: My PC does not recognize the tablet anymore when I connect it. It does load when I connect it to the adapter but I can't transfer files anymore via PC. Cable is not broken but to minimize this risk I already offered a new one just in case.
Do you guys have any idea what this maybe is caused from? Maybe broken hardware? Or maybe a not properly connected cable in the tablet? But if so why is USB and stuff not working?
Please help me, I don't wanna lose such an awesome tablet
And I may can't even RMA it cause I've unlocked and flashed a new ROM on it...
EDIT 12.06.2013: When the tablet is fully turned off and USB is plugged in (PC, not charger) it suddenly powers up. I still can't use USB ports...
EpicLPer said:
Hello guys!
For about 2 or 3 weeks now I have the problem that the speaker on my TF201 does not work anymore. Headphones are working fine.
It also does not recognize any USB Sticks anymore. The Dock is not dead, it works fine and also has current on the USB Port (the USB stick LED is activated but does not blink for accessing it). Also the SD Card slot does not work anymore. The MicroSD slot on the tablet itself works fine...
And the next thing: My PC does not recognize the tablet anymore when I connect it. It does load when I connect it to the adapter but I can't transfer files anymore via PC. Cable is not broken but to minimize this risk I already offered a new one just in case.
Do you guys have any idea what this maybe is caused from? Maybe broken hardware? Or maybe a not properly connected cable in the tablet? But if so why is USB and stuff not working?
Please help me, I don't wanna lose such an awesome tablet
And I may can't even RMA it cause I've unlocked and flashed a new ROM on it...
Click to expand...
Click to collapse
Do you have one of the Prime to USb connectors? I wonder if the issue is in the dock or the tablet connector.
poofyhairguy said:
Do you have one of the Prime to USb connectors? I wonder if the issue is in the dock or the tablet connector.
Click to expand...
Click to collapse
Sadly no. I never ever would have used that cause I have the dock. And Dock can't be broken, the problem appeared since the speaker is not working too.
I tested MicroHDMI output now. Works fine, audio is there too. Hm... Strange...
Hidden "Camera Version" function?
Sorry, wrong thread ^-^" Please delete this entry!
My first guess is that something may have gotten disconnected inside the Prime. It's unlikely, but worth a check. Have you ever opened your prime?
When you have a dock, you have two options of connecting it to your PC. You can put the Prime into the dock then connect the two to your PC or you can just set the dock aside and connect the Prime directly. Have you tried both ways?
Jgrimoldy said:
My first guess is that something may have gotten disconnected inside the Prime. It's unlikely, but worth a check. Have you ever opened your prime?
When you have a dock, you have two options of connecting it to your PC. You can put the Prime into the dock then connect the two to your PC or you can just set the dock aside and connect the Prime directly. Have you tried both ways?
Click to expand...
Click to collapse
Jup I tried both ways.
And no I never opened it up. May I should look for a tutorial. Does iFixIt have an tutorial for it?
I don't think that iFixIt has one. At least they didn't about 6 months ago when I needed to replace my glass. There should be links to tutorials buried in these forums. Also, a little Googling should find you something too.
Regarding the HDMI audio working: Not too much of a surprise. Remember that the micro-hdmi port is sending a data stream with the audio embedded/encoded as 1s and 0s. It seems like something may have (hopefully) come disconnected related to the built-in speaker.
Jgrimoldy said:
I don't think that iFixIt has one. At least they didn't about 6 months ago when I needed to replace my glass. There should be links to tutorials buried in these forums. Also, a little Googling should find you something too.
Regarding the HDMI audio working: Not too much of a surprise. Remember that the micro-hdmi port is sending a data stream with the audio embedded/encoded as 1s and 0s. It seems like something may have (hopefully) come disconnected related to the built-in speaker.
Click to expand...
Click to collapse
I opened it up but I saw no unconnected or partly connected cable. I only lifted up the touchscreen, about the other parts I was too afraid to ruin something... Didn't unscrew so I wasn't able to see the under connectors.
Anyway, I don't think it's an unconnected cable. But if it's a software fault why are suddenly without flashing anything like Kernel or Bootloader so many things not working? That's just... What the hell o-O
Also I don't want to RMA it again. It's flashed and unlocked so I may have to pay 100€ for it... I could easily spend that money on a Galaxy Tab or something. But would still be awesome to have that one as "backup tablet" then just in case so I don't want to just throw it away.
Good on ya for taking a look. If you disconnect the robbon cables that connect the digitizer and LCD to the mainboard, you can set the top part (the screen and glass) aside and take a much better look. I completly understand your reluctance for fear of damaging. I felt the same way when I took mine apart the first time to replace the digitizer glass.
In devices like this, the headphones and the built-in speaker have separate amplifiers. They're not like very old transistor radios where the headphone jack is connected to the speaker wires with an interlock. I found this out when my Viewsonic 4.5" video player had digitally garbled sound in the headphones but not in the built-in speakers. Weirdest thing that I wouldn't expect being old-school...
The upshot is that you simply may have failed components, which is a real bummer since these are (imho) still pretty sweeet tablets.
You *could* always contact ASUS support and describe the problem and see if they can share any familiarity or knowledge with you. Sadly, I've found ASUS support to be bag-of-hammers dumb and patently useless, despite having a decent product.
Jgrimoldy said:
Good on ya for taking a look. If you disconnect the robbon cables that connect the digitizer and LCD to the mainboard, you can set the top part (the screen and glass) aside and take a much better look. I completly understand your reluctance for fear of damaging. I felt the same way when I took mine apart the first time to replace the digitizer glass.
In devices like this, the headphones and the built-in speaker have separate amplifiers. They're not like very old transistor radios where the headphone jack is connected to the speaker wires with an interlock. I found this out when my Viewsonic 4.5" video player had digitally garbled sound in the headphones but not in the built-in speakers. Weirdest thing that I wouldn't expect being old-school...
The upshot is that you simply may have failed components, which is a real bummer since these are (imho) still pretty sweeet tablets.
You *could* always contact ASUS support and describe the problem and see if they can share any familiarity or knowledge with you. Sadly, I've found ASUS support to be bag-of-hammers dumb and patently useless, despite having a decent product.
Click to expand...
Click to collapse
Opened up again, tried to push a few connectors in a bit but nothing... Looks like I really have a hardware failure...
But what now? When I send it to ASUS (or the shop where I bought it) they might say "Nope, you opened that thing". Also flashing back Stock ROM is... Yeah... Many work... I already was on the 4.1.2 Bootloader, upgraded to 4.2.1 now. I don't know how seriously they take that whole hacking/flashing thing, maybe they even repair a flashed tablet.
I dont know if it helps anyone further pin-point the problem because i havent been able to but i have the same issues and for me the sound comes back once i have the screen separated from the tablet. i can restart the tablet many times and audio still works as long as the screen is not fully in its place. If i clip the screen back in its place audio still works until i turn off or restart the tablet.
Sent from my Transformer Prime TF201 using xda app-developers app
Hello i've got the same problem and i'm praying someone can help.
Since updating from Androwook Hairy Bean V2.11 to V2.2 RC1;
there is no sound from the external speaker; playing media, notifications, alarms etc
dock doesnt recognise usb stick
pc doesnt recognize the tablet
on V2.2 RC1 i got the update pad firmware message and i accepted it, not sure if this is the cause because others have done the sam and reported everything working fine.
Also starting getting a notification on startup "unable to detect driver for loudspeaker" on V2.2 RC1. So i downgraded to Hairy Bean V2.11 thinking it would solve the issue but it hasn't, nothings changed.
I've tried a factory reset, cold boot, downloaded dsp manager and not been successful.
Has anyone come across this problem and found a solution?
Please help me
Thanks
zillar5 said:
Hello i've got the same problem and i'm praying someone can help.
Since updating from Androwook Hairy Bean V2.11 to V2.2 RC1;
there is no sound from the external speaker; playing media, notifications, alarms etc
dock doesnt recognise usb stick
pc doesnt recognize the tablet
on V2.2 RC1 i got the update pad firmware message and i accepted it, not sure if this is the cause because others have done the sam and reported everything working fine.
Also starting getting a notification on startup "unable to detect driver for loudspeaker" on V2.2 RC1. So i downgraded to Hairy Bean V2.11 thinking it would solve the issue but it hasn't, nothings changed.
I've tried a factory reset, cold boot, downloaded dsp manager and not been successful.
Has anyone come across this problem and found a solution?
Please help me
Thanks
Click to expand...
Click to collapse
That is very strange mate.
The firmware update was just for the pad and if it had already installed on 2.11 and was working fine then that was done. The only person who ever had a problem with it happened as he was installing it and we fixed that.
Upgrading to 2.2 changed nothing from 2.11 except a slightly newer base and some newer kernels. Even if the kernels were not supporting your hardware when you downgraded back to 2.11 you would have been back on the old kernels and back to how you had it working before.
This does confuse me.. As a test because I cannot think of anything else except hardware failure at the moment can you try getting the downgrade zip from the hairybean thread that takes you back to 4.1.1 bootloader and compatible twrp and then try flashing hairybean 1.51 instead.
Read the instructions thoroughly under the downgrading section.
flumpster said:
That is very strange mate.
The firmware update was just for the pad and if it had already installed on 2.11 and was working fine then that was done. The only person who ever had a problem with it happened as he was installing it and we fixed that.
Upgrading to 2.2 changed nothing from 2.11 except a slightly newer base and some newer kernels. Even if the kernels were not supporting your hardware when you downgraded back to 2.11 you would have been back on the old kernels and back to how you had it working before.
This does confuse me.. As a test because I cannot think of anything else except hardware failure at the moment can you try getting the downgrade zip from the hairybean thread that takes you back to 4.1.1 bootloader and compatible twrp and then try flashing hairybean 1.51 instead.
Read the instructions thoroughly under the downgrading section.
Click to expand...
Click to collapse
Thanks for the assistance Flumpster and I've been following your thread, you've done some damn amazing work!
Just for the record 2.11 + that kernel had my prime running the best it ever has! after doing all the wipes, formats I flashed v2.2 and got the update pad firmware then and missing speaker driver notification? I dismantled my prime and checked for a loose connection on the speaker but it looks ok.
I'll try the downgrade tomorrow (going to bed now) and if that doesn't work, i still have audio through the headphone jack.
Thanks again
zillar5 said:
Thanks for the assistance Flumpster and I've been following your thread, you've done some damn amazing work!
Just for the record 2.11 + that kernel had my prime running the best it ever has! after doing all the wipes, formats I flashed v2.2 and got the update pad firmware then and missing speaker driver notification? I dismantled my prime and checked for a loose connection on the speaker but it looks ok.
I'll try the downgrade tomorrow (going to bed now) and if that doesn't work, i still have audio through the headphone jack.
Thanks again
Click to expand...
Click to collapse
Just to make sure... Are you saying this happened straight after the firmware update on the next reboot or are you saying it happened when updating the rom ?
flumpster said:
Just to make sure... Are you sayig this happened straight after the firmware update on the next reboot or are you saying it happened when updating the rom ?
Click to expand...
Click to collapse
Honestly I don't know because afer I flashed 2.2 the homescreen loaded and the update firmware message appeared straight away. I dont think the notificatipns were sounding as the apps were restoring? Sorry i'm not 100% sure it happened pretty quickly
zillar5 said:
Honestly I don't know because afer I flashed 2.2 the homescreen loaded and the update firmware message appeared straight away. I dont think the notificatipns were sounding as the apps were restoring? Sorry i'm not 100% sure it happened pretty quickly
Click to expand...
Click to collapse
Ok mate.. Well try the downgrade option first and if that doesn't work then first of all I want you to drain your battery completely and leave for an hour. After that charge it up a little and try ( I know this sounds crazy and I thought the same when I first read it in another thread but it fixed our one guy who had problems with the firmware upgrade )
If this still does not work then upgrade back to 2.2 and once you are in the OS I will try to talk you into downgrading that firmware update to see if that helps.
If that still doesn't work after downgrading the firmware update then it is hardware sorry.
flumpster said:
Ok mate.. Well try the downgrade option first and if that doesn't work then first of all I want you to drain your battery completely and leave for an hour. After that charge it up a little and try ( I know this sounds crazy and I thought the same when I first read it in another thread but it fixed our one guy who had problems with the firmware upgrade )
If this still does not work then upgrade back to 2.2 and once you are in the OS I will try to talk you into downgrading that firmware update to see if that helps.
If that still doesn't work after downgrading the firmware update then it is hardware sorry.
Click to expand...
Click to collapse
i did what the 1st page of the ROM says and rebooted into recovery, tried installing 4.1.1 bootloader and recovery zip from my external sd card and failed - unable to open zip? strange...
zillar5 said:
i did what the 1st page of the ROM says and rebooted into recovery, tried installing 4.1.1 bootloader and recovery zip from my external sd card and failed - unable to open zip? strange...
Click to expand...
Click to collapse
ok micro sd card was coming up write protected, so formated and downloaded new files and managed to downgrade to 4.1.1 bootloader and v1.51 - still no sound from external speaker, also sd slot and usb still not working on dock. Tried running the battery flat and leaving it for over an hour then charged a little and powered on still no change.
I'm leaving work now and have limited internet access tonight so i download the v2.2 zip tomorrow and see if that works, otherwise could be hardware hey.
So the other day I went to use Snapchat to take a photo of something and noticed it wouldn't switch to my rear camera. After some investigation I discovered that the rear camera wasn't working. I went further and tried using a flashlight app, a few different camera apps from the Play Store and some other ideas that I thought might work. None of them did. Not only that but the front "selfie" camera was now taking very elongated and flipped upside down pictures in the standard camera app. Snapchat they're just fine, reversed like in a mirror, but fine aside from that.
For the next step I did a complete wipe, data and cache as well as a factory reset. Again, this didn't resolve my issue. So I started looking into hardware fixes and decided I would order a new rear camera. They weren't expensive and I felt comfortable enough to install it.
While waiting for the camera to come in from Amazon I went about using my phone as normal, no big deal to not have a camera. One day I left my camera in the car on a fairly warm day and when I came back it said the phone had shut off due to overheating. No biggy, I restarted the phone and for whatever reason decided to check the camera for s&g's and voila! The rear camera was working just fine...until I replied to a message and went to use the camera again. Back to not working. Damn.
Replacement camera arrives and I install it, easy peasy. I restart my phone and....nothing. Still doesn't work. I thought maybe it could be a software thing so I was going to root it and try a Rom, but I have a revision (2) PCB, so I guess that's completely out of the question.
Does anyone have any ideas? Anything I could try? I love this phone and would hate to have to get a new one before the new Nexus arrives. Thanks for any help
Revision 2 only affects things if under your battery there's a K at the end of the VS985 model # such as VS985WK.
I've had a revision 2 PCB all this time this last year and a half, and it doesn't affect me since I don't have a K submodel.
Do if you don't either, definitely flash the 10B TOT and if the camera doesn't work on 10B then it's definitely not a software issue.
http://forum.xda-developers.com/showthread.php?p=67945841
http://forum.xda-developers.com/showthread.php?p=68040923
http://forum.xda-developers.com/showpost.php?p=68098895&postcount=1470
roirraW "edor" ehT said:
Revision 2 only affects things if under your battery there's a K at the end of the VS985 model # such as VS985WK.
I've had a revision 2 PCB all this time this last year and a half, and it doesn't affect me since I don't have a K submodel.
Do if you don't either, definitely flash the 10B TOT and if the camera doesn't work on 10B then it's definitely not a software issue.
http://forum.xda-developers.com/showthread.php?p=67945841
http://forum.xda-developers.com/showthread.php?p=68040923
http://forum.xda-developers.com/showpost.php?p=68098895&postcount=1470
Click to expand...
Click to collapse
Well, wish I would've saw this post before I updated my phone this morning. Latest OTA update change the rooting?
There is no K after the model, but the pcb does have a (2). So just the standard rooting procedure that you linked? And the latest Verizon OTA?
premedicated said:
Well, wish I would've saw this post before I updated my phone this morning. Latest OTA update change the rooting?
There is no K after the model, but the pcb does have a (2). So just the standard rooting procedure that you linked? And the latest Verizon OTA?
Click to expand...
Click to collapse
See my thread about the 48A OTA in the General section regarding downgrading. You can't take OTAs once you're rooted. It'll download but fail to apply. Once you're rooted and on @xdabbeb 's stock 47A firmware in the Development section - also in my signature below, flash any of my debloat zips in the third post of that thread including the No OTA debloat zip. I only leave OTAs non-debloated on all the other debloat zips by default because I want to be aware when an OTA is available, although someone usually reports it on here before I get the notice.
roirraW "edor" ehT said:
See my thread about the 48A OTA in the General section regarding downgrading. You can't take OTAs once you're rooted. It'll download but fail to apply. Once you're rooted and on @xdabbeb 's stock 47A firmware in the Development section - also in my signature below, flash any of my debloat zips in the third post of that thread including the No OTA debloat zip. I only leave OTAs non-debloated on all the other debloat zips by default because I want to be aware when an OTA is available, although someone usually reports it on here before I get the notice.
Click to expand...
Click to collapse
I've always rooted my phones previously, but my last g3 I dropped and shattered the screen. This is the replacement which was already updated.
I'll poke through there and get it rooted tonight and hopefully that'll solve the camera problem. However at this point I'm worried that it might be another piece of hardware related to the camera. Maybe the laser focus or flash, not sure. That's the only other thing I think it'll be if it isn't software related.. (obviously)
premedicated said:
I've always rooted my phones previously, but my last g3 I dropped and shattered the screen. This is the replacement which was already updated.
I'll poke through there and get it rooted tonight and hopefully that'll solve the camera problem. However at this point I'm worried that it might be another piece of hardware related to the camera. Maybe the laser focus or flash, not sure. That's the only other thing I think it'll be if it isn't software related.. (obviously)
Click to expand...
Click to collapse
Understood. I doubt if it's software but it's still worth a try. Rooting itself won't be the solution, but flashing the 10B TOT might. If the camera doesn't work after flashing the stock 10B TOT, then it won't work no matter what you'll do software-wise (rooting, etc). If you got this replacement through a warranty, I'd act fast as they might have a time limit under which you can re-exchange this faulty replacement without considering it a new claim.
roirraW "edor" ehT said:
Understood. I doubt if it's software but it's still worth a try. Rooting itself won't be the solution, but flashing the 10B TOT might. If the camera doesn't work after flashing the stock 10B TOT, then it won't work no matter what you'll do software-wise (rooting, etc). If you got this replacement through a warranty, I'd act fast as they might have a time limit under which you can re-exchange this faulty replacement without considering it a new claim.
Click to expand...
Click to collapse
Yeah, that's kinda what I gathered. I just figure it'll be my last ditch effort to try before giving up and saving for the new nexus.
premedicated said:
Yeah, that's kinda what I gathered. I just figure it'll be my last ditch effort to try before giving up and saving for the new nexus.
Click to expand...
Click to collapse
Good luck! Let us know how it goes.
Well, didn't work. I tried different camera apps and none of them will work on the rear camera.
At this point I'm not really sure what else to do since I've already replaced the camera. It might be the laser not working and causing the camera to in turn not work...or maybe the flash (?) but regardless, not sure what it is. I guess I'll just abandon it and wait for late October to pick up a new nexus and go back to paying Verizon more $$$... womp womp wooommmmppppp....
Thanks for all your help roirraW "edor" ehT
Sorry to hear that! You're welcome, hope we all find decent solutions when its time for us all to upgrade.
I'm having the exact same issue. Only front camera works, back camera doesn't. I do think it's a hardware issue related to overheating. My phone got hot one day and the camera started acting weird (not focusing correctly, glitchy pictures). Then a few days later it gave me the same error as yours. I flashed a stock ROM to no avail. I even tried safe mode which also didn't work. I'm going to try to mess with the insides next and see if that works.
benthe1 said:
I'm having the exact same issue. Only front camera works, back camera doesn't. I do think it's a hardware issue related to overheating. My phone got hot one day and the camera started acting weird (not focusing correctly, glitchy pictures). Then a few days later it gave me the same error as yours. I flashed a stock ROM to no avail. I even tried safe mode which also didn't work. I'm going to try to mess with the insides next and see if that works.
Click to expand...
Click to collapse
My camera is working again! I ended up not opening up my phone. Instead I flashed the camera mod that is supposed to allow 1080 recording at 60 fps. That ended up soft bricking my phone so I had to re-flash the stock ROM I originally flashed which ended up making the camera working again. I'm not sure if it was the camera mod that set something straight or just re-flashing the stock ROM that fixed it. Either way, I hope that helps someone.
My lg v10 was having same problem i installed evry camera app from playstore and wipe cache of gallery any camera app also .. But nothing helping .my problem is actually flashlight says camera app is running .. And camera app unfortunately stoping..... So here us what i have done to solve this
1.in power menu. Long press shutdown /poweroff to prompt safe mode menu .
2. It will ask .. Press ok
First off, this may be a dupe from another thread (http://forum.xda-developers.com/verizon-lg-g3/general/vs985-ota-updated-to-49a-11-11-t3498269), but I wanted it as main topic so that what was discovered does not go unnoticed by people who may not read the entire thread. Maybe someone can sticky this as well since this is a major issue with the 49A OTA?
Last week, I took the 49A OTA for the G3. I have an older model (non-K model) and immediately, upon rebooting, I started getting multiple SD card ejection notifications. It would unmount and remount my SD Card several times throughout the day. This would happen at random times, although my feeling was that it occurred whenever an app attempted to read and/or write to the SD card. Sometimes, after it unmounted, it would take anywhere from a few minutes to maybe an hour or more to remount it without rebooting.
This continued on throughout the week as I waited to see if it would clear up. It didn't. A factory data reset didn't help and one time, I saw a SIM card failure. Posting in the forums, it was a few days later that @nulloverride posted this very important tid bit of information:
http://forum.xda-developers.com/showpost.php?p=69676134&postcount=17
nulloverride said:
I actually just spoke with Verizon's support people. It turns out the device is not compatible with the latest Android updates. Maybe going back to square one with it will fix the problem, but they said they would give me a new device with the updates disabled until the problem is fixed. I don't know if that means I'll have to give them the new phone back when the updates are working or what. I'm kind of partial to this one, now. But I do know that possibly bricking my phone with this KDZ or TOT stuff is a less appealing option than getting a free replacement and/or upgrade. I'll find out more tomorrow.
Click to expand...
Click to collapse
I have since flashed back to 48A via a 10B TOT flash. The reason I did this is to see if the error would show up in any of the other OTAs. They didn't. I have been on 48A since November 17th, and not ONE, I repeat, not ONE single SD card error has appeared. I have gone to 49A twice and both times, as soon as I get to 49A, SD card errors start popping up. And the SD card is fine (reformatted, did a full disk check on it). Any SD card I put in resulted in the error, and now with @nulloverride stating what he learned from the VZW rep pretty much confirms that the 49A OTA is the culprit.
So, I would state for anyone considering taking the 49A OTA to refrain from it. I've added a poll to see what the demographic is across K and non-K models of the VS985.
Again, this might be a dupe, but I feel it should be a main topic so that more people see it.
UPDATE #1 (11/21/2016):
Well guess what. No sooner do I post this and I get the dreaded "SD Card has been unmounted", but it remounted it right up. However, it occurred when I attempt to launch two apps that had just updated over the weekend that I hadn't launched since they were updated:
1. Google Opinion Rewards
2. Google Play Music
Both times, when I launched each app, I saw the SD card was unmounted but then it was remounted immediately without any issues. I'm wondering if these apps have been updated with new permissions and needed to remount the SD card? Maybe this is part of some new functionality? It does appear under 49A that maybe that is what is going on, however for me it causes the phone to have a "seizure" (as I like to say) and may not remount successfully for some reason. Strange. But, this time, under 48A, it mounted the card both times pretty quickly without any issue. So maybe this is normal when it works but under 49A, something is broken where it can't remount for some reason? Other than that, I have NOT seen this at all, so I wonder if in this case, it's an app issue (since both apps were recently updated). Not sure if the Rewards app needs access to the SD card, but I do have my music on the SD card, so Google Play Music would need to access the music from there.
UPDATE #2 (11/22/2016):
Switched SD cards and it happened again. Switched to a 2gb card. OUCH! So far, no issues. Wondering if it was the SD card all along? Upgraded to 49A since then and so far (fingers crossed) no issues. But, that's how it was before. This 2gb card is old, but hasn't been used much so hopefully, there aren't any bad areas. Surprised doing a chkdsk on the other SD cards didn't bring up anything. Will continue to monitor and update as I find more info.
Tekcafe rom VS98549A
https://www.youtube.com/watch?v=3FxIk7x-CaE
I've talked about this in another thread, forgetting I had this thread.
I have determined that in Safe Mode, I experience no issues with my SD card being unmounted unexpectedly. Once I boot back into Normal (Unsafe?) Mode, boom. SD Card becomes unmounted.
Something with the 49A OTA has broken something within the phone. This does NOT appear to be a hardware problem. But, the issue persists across ALL versions of the software (10b through 49A).
I called into Verizon today and they searched and saw that, as I already knew, I'm not the only one with this issue with this phone after the 49A OTA. She stated they are looking into the issue to resolve it. She's getting ready to patch me directly in with LG so we can discuss if they know what is going on. Seems like a firmware update issue that even a 10B TOT flash won't fix because it might be in a protected area of the phone that only the OTAs can update.
Also, I notice that 2 others have voted in the poll and are experiencing this issue and they are like me in that they have the older non-K model of the phone.
Okay. LG was of NO help. They said I could send my phone in and they would do a diagnostic and they have a way to flash it back to the way it was before the 49A OTA. Yeah, so do I which is 10B, etc. None of those work. Oh, and I would have to pay for any repairs as it's out of warranty.
I told her this was due to an official OTA. So basically, they can send out updates to out-of-warranty phones that break them, yet I would have to pay for any repairs? Sorry. That doesn't fly in my book.
Verizon said that they know of the issue and are looking into it, so I'll wait and see because if that is true, and they do come up with a fix, then I'm definitely going to wait because this phone has been great, and still is for me.
Now, if they want to send me a completely new phone free-of-charge and I turn this one in after I get the new one, yeah. I'll do that. And by new, I mean a replacement G3, preferably not refurbed. Heck, I'll take the K model because I won't root or flash back to 10b. I haven't for almost a year, except to try and debug this SD card issue I've been having since the 49A OTA.
In any case, anybody else that is having this issue, if you haven't already done so, reboot into safe mode. This is how you do it:
Power off the phone
Press and hold power + volume down until you see the menu
Choose Safe Mode and boot into it.
Once in Safe Mode, do things that would require writing and/or reading to/from your SD card (such as storing pictures from your camera on it). Copy files to your SD card, delete them, etc. Stay in that mode for as long as you can (you can still receive phone calls and text messages as well as make calls and send messages). You won't have access to any downloaded apps until you boot out of safe mode.
I want to know if this works for everyone, and then when they boot back into normal mode, if their SD card issues come back.
I've inspected the SD card slot. It is NOT damaged in any way. All pins are there and are in good condition. I think safe mode proves that. If this were a hardware failure, it should occur in safe mode and it doesn't. Something the 49A OTA updated (probably in a protected area of the firmware) is causing this and even flashing back to older versions doesn't overwrite that protected area. But for some reason, when in Safe Mode, it's either ignoring that area, or it's something else in the firmware that was updated that Safe Mode bypasses.
Okay, another update on my plight on figuring this out. I decided to uninstall two apps. Not sure why I chose them, but I did:
Greenify (mine I donated but I'm not rooted)
Nova Launcher (paid for)
I removed Nova because in Safe Mode, I'm running the default LG Home launcher. Greenify (even though it's not in root mode) I decided to remove since it's supposed to hibernate background processes.
Once I removed both, it appears so far that the problems have gone away. I haven't installed either one yet, but I will and I'll update what I find. If it's Greenify, then it must be something it's doing, which I find a little strange, but maybe the 49A update "broke" something in Greenify? If it's Nova, then again, something is going on with that.
I'm going to run without either app for the next day or so to see what happens. The thing I cannot understand is, I had ran without using either app I believe after factory resetting and still the problem persisted. So this might be a false positive for me. Definitely, safe mode the problem does not persist as I left my phone in safe mode for about 2 hours.
UPDATE: Okay. Apparently it wasn't Nova or Greenify as it started happening again after awhile. Safe Mode still cures it for some reason. It never umounts in Safe Mode, but once I reboot out of Safe Mode, it unmounts. So I guess we wait and see what Verizon/LG have to say about this, if anything. Not holding out too much hope though.
iBolski said:
Also, I notice that 2 others have voted in the poll and are experiencing this issue and they are like me in that they have the older non-K model of the phone.
Click to expand...
Click to collapse
I'm one of the ones who voted. I'm sorry, I misread the poll. I am NOT having any issues with my SD Card slot after the 49A update. Sorry for the confusion.
dmoney98 said:
I'm one of the ones who voted. I'm sorry, I misread the poll. I am NOT having any issues with my SD Card slot after the 49A update. Sorry for the confusion.
Click to expand...
Click to collapse
No biggie. Are you on a k model or non k model of the vs985?
Sent from my VS985 4G using Tapatalk
iBolski said:
No biggie. Are you on a k model or non k model of the vs985?
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
I am on the non-k model of vs985.
Dammit. Wish i would have read this before giving away my 128gb sd card. I thought it was just another failing piece of hardware.
First it was the internal mic.
Next the aux port.
Now the sd card slot.
So much for an upgrade from my unbreakable G2.
Time to revert to 12b and get my card back. Thanks OP!
(Non k)
afextwin said:
Dammit. Wish i would have read this before giving away my 128gb sd card. I thought it was just another failing piece of hardware.
First it was the internal mic.
Next the aux port.
Now the sd card slot.
So much for an upgrade from my unbreakable G2.
Time to revert to 12b and get my card back. Thanks OP!
(Non k)
Click to expand...
Click to collapse
I have no idea if it truly is an issue with the update or people's phones just started to miraculously start to fail after taking the OTA. I'm hoping it's the former and that there is a fix for this. In cany case, sorry to hear you gave away your SD card, but it sounds like you have more than just the SD card issue. I'm only having an SD card issue. No other failures. Your's definitely sounds like hardware failures with the list you gave and I doubt it's due to the upgrade.
I'm about ready to flash to a non-stock ROM to see if that might cure the issue.
iBolski said:
I have no idea if it truly is an issue with the update or people's phones just started to miraculously start to fail after taking the OTA. I'm hoping it's the former and that there is a fix for this. In cany case, sorry to hear you gave away your SD card, but it sounds like you have more than just the SD card issue. I'm only having an SD card issue. No other failures. Your's definitely sounds like hardware failures with the list you gave and I doubt it's due to the upgrade.
I'm about ready to flash to a non-stock ROM to see if that might cure the issue.
Click to expand...
Click to collapse
This might be unnecessary for me to remind you but I definitely recommend flashing the 10B TOT before testing to see if a custom ROM solves it, and if you decide to go back to fully stock I'd flash the 10B TOT once again beforehand.
Edit: Of course I forgot you're running completely stock, in which case flashing the TOT before will be necessary in order to root, etc, anyway.
roirraW "edor" ehT said:
This might be unnecessary for me to remind you but I definitely recommend flashing the 10B TOT before testing to see if a custom ROM solves it, and if you decide to go back to fully stock I'd flash the 10B TOT once again beforehand.
Edit: Of course I forgot you're running completely stock, in which case flashing the TOT before will be necessary in order to root, etc, anyway.
Click to expand...
Click to collapse
LOL. No biggie. I'm thinking of trying it just to see if the issue goes away, but if the 49A did touch a protected area that I cannot flash over, and that is the main reason why I see this issue across all version of the stock image, going to AOSP-based probably won't help, but it's still worth a look.
I guess what I need to do is backup my apps with LG backup, flash back to 10B, root, restore from LG Backup, then use TiBu to back up. Ugh! I know there is an LG Backup tool in the Google Play store, but I don't know if it will work from non-stock based ROMs.
iBolski said:
LOL. No biggie. I'm thinking of trying it just to see if the issue goes away, but if the 49A did touch a protected area that I cannot flash over, and that is the main reason why I see this issue across all version of the stock image, going to AOSP-based probably won't help, but it's still worth a look.
I guess what I need to do is backup my apps with LG backup, flash back to 10B, root, restore from LG Backup, then use TiBu to back up. Ugh! I know there is an LG Backup tool in the Google Play store, but I don't know if it will work from non-stock based ROMs.
Click to expand...
Click to collapse
As far as I know, the only LG Backup we can use is the one built into the stock ROMs. The one in the Play Store, unless there's another I'm unaware of, is for using on a non-LG device to move some of your data to an LG device, and according to the picture in the Play Store, looks like it has to happen between two different devices because they connect either directly via USB or wirelessly to do the transfer.
roirraW "edor" ehT said:
As far as I know, the only LG Backup we can use is the one built into the stock ROMs. The one in the Play Store, unless there's another I'm unaware of, is for using on a non-LG device to move some of your data to an LG device, and according to the picture in the Play Store, looks like it has to happen between two different devices because they connect either directly via USB or wirelessly to do the transfer.
Click to expand...
Click to collapse
Looks like Backup in 49A, revert to 10b, restore in 10b, root, TiBu it, flash AOSP ROM.
10b through 48A all show the same symptom. Might definitely be a hardware issue for me, but I find it really odd that as SOON as I upgraded to 49A, that's when my problems started. Never, I mean, never had one single issue with my SD card up until that point.
Still waiting to hear back from "possible solutions" to my issue from VZW. I have a feeling is "We can get you a discounted upgrade". Nope, nada, no way. If you broke it, you fix it for free, VZW.
iBolski said:
Looks like Backup in 49A, revert to 10b, restore in 10b, root, TiBu it, flash AOSP ROM.
10b through 48A all show the same symptom. Might definitely be a hardware issue for me, but I find it really odd that as SOON as I upgraded to 49A, that's when my problems started. Never, I mean, never had one single issue with my SD card up until that point.
Still waiting to hear back from "possible solutions" to my issue from VZW. I have a feeling is "We can get you a discounted upgrade". Nope, nada, no way. If you broke it, you fix it for free, VZW.
Click to expand...
Click to collapse
It was the same deal for myself (and for others) with my wife's SIM slot, except 49A wasn't even out yet, and she was on @xdabbeb 's VS985 v3.1.1 ROM. It's just ironic since although I haven't taken my SIM out a lot on my own G3, hers might've only been taken out once or twice since she got her phone. Never any hint of trouble and all of the sudden it no worky.
Since I've heard that the SIM slot is a common problem on the G3, and that the SIM and Micro SD card slot are both together, it could be that they're both just flaky. I certainly feel more secure with the SIM and Micro SD card trays, rather than slots.
By the way, I personally always had a lot of trouble using Titanium Backup on the G3 (and my my previous Galaxy S3). Especially for restores, always took a bunch of restarting to get everything restored. I'm guessing it has to do with such a custom framework because (not to be OT) on my HTC 10, which is very close to stock Android, and even a custom ROM based on the stock HTC Android, Titanium Backup was back to being completely dependable.
As many may know, I no longer have the G3. It died last week, so I'm now on the Samsung S7. It would still be interesting to see if Verizon does issue a fix IF the OTA is indeed what caused the SD card issue. But now I'm beginning to think my issue was hardware failure. I guess it was just blind luck/coincidence that right after the 49A OTA, that's when my SD card slot started to fail.