Hello everyone
I have a lenovo vibe p1a42
When i bought this phone i was initially able to update without any problem til build no. S147_151288_ROW. But after that when i received notification of new update available, i downloaded it bt I cannot update it. I tried it several time. Every time it jist takes me to recovery mode, starts updating then at 24% it fails. I tried updating manually. I also tried using Lenovo Smart Assistant. But all of them give same result.
I am unable to uodate any furture. Can u tell me what should i do? I hear that this phone has now MM update too, bt i'm stuck.
Also, my phone has stopped vibrating. No vibration on anything. The vibration does works sometimes, bt again stops working in few min. I dont know whether this is software related or h/w prob. I will take it to service center if the problem doesnt solve on updating the os.
niranjand147 said:
Hello everyone
I have a lenovo vibe p1a42
When i bought this phone i was initially able to update without any problem til build no. S147_151288_ROW. But after that when i received notification of new update available, i downloaded it bt I cannot update it. I tried it several time. Every time it jist takes me to recovery mode, starts updating then at 24% it fails. I tried updating manually. I also tried using Lenovo Smart Assistant. But all of them give same result.
I am unable to uodate any furture. Can u tell me what should i do? I hear that this phone has now MM update too, bt i'm stuck.
Also, my phone has stopped vibrating. No vibration on anything. The vibration does works sometimes, bt again stops working in few min. I dont know whether this is software related or h/w prob. I will take it to service center if the problem doesnt solve on updating the os.
Click to expand...
Click to collapse
Hello,
Try upgrading your phone via QPST and not OTA
Good luck
dreigosh said:
Hello,
Try upgrading your phone via QPST and not OTA
Good luck
Click to expand...
Click to collapse
I wanted to try tht but i cannot find a link for s152 version file. I tried contacting lenovo through their official forum, they said bring it to service center. I think i ll just do that only. Since i anyway had to go there for my vibration problem.
BTW Thank you for reply.
Sent from my Lenovo P1a42 using XDA-Developers mobile app
niranjand147 said:
Hello everyone
I have a lenovo vibe p1a42
When i bought this phone i was initially able to update without any problem til build no. S147_151288_ROW. But after that when i received notification of new update available, i downloaded it bt I cannot update it. I tried it several time. Every time it jist takes me to recovery mode, starts updating then at 24% it fails. I tried updating manually. I also tried using Lenovo Smart Assistant. But all of them give same result.
I am unable to uodate any furture. Can u tell me what should i do? I hear that this phone has now MM update too, bt i'm stuck.
Also, my phone has stopped vibrating. No vibration on anything. The vibration does works sometimes, bt again stops working in few min. I dont know whether this is software related or h/w prob. I will take it to service center if the problem doesnt solve on updating the os.
Click to expand...
Click to collapse
I understand your pain.... lenovo OTA updates are very finicky. If you want marshmallow you can straightaway flash that ROM (the latest one is S285).
But please make sure to backup your data since this will definitely wipe all your data (same as factory reset). There is thread in on this forum which gives a fairly easy steps on flashing ROMs folr Vibe P1.
If you want to root your android 6.0 though, thats a different story.
Still have a look here - http://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650
You can flash ROM fairly easily from flashing steps mentioned in above thread. If you feel rooting steps are complex, you can still stay on unrooted rom, at least it will be the latest one.
Related
Hey guys I've had this issue where regardless of what music app I use, a few seconds after I turn my screen off (i.e. lock the device) the music will stop playing until I turn it back on.
Anyone have any idea why? I'm on version 10e (latest according to PC Suite and OTA Checker), and I'm stock unrooted.
Other than that the phone's been amazing and blazing fast, even outspeeding my M8 GPE sometimes
Sent from my LG G3 Cat.6 using Tapatalk
Also, when charging, this problem doesn't occur. This further adds to the mystery...
Also, it happens if I have music local or streaming, so that rules out network issues.
Sent from my LG G3 Cat.6 using Tapatalk
UPDATE: OK so after messing with about every single setting on the phone, I tried switching it back to Dalvik. Fixed everything 100%. Whole phone is faster, from opening apps to web pages.
Very strange... Not sure why there would be so much ART incompatibility, but I guess it's 4.4.2 and not .3 or .4. If anyone else has has this problem (including an inability to wake the phone up without a few tries), check your RunTime. I'm hoping it'll be better next update, but for now this'll have to do.
Sent from my LG G3 Cat.6 using Tapatalk
SolarTrans said:
UPDATE: OK so after messing with about every single setting on the phone, I tried switching it back to Dalvik. Fixed everything 100%. Whole phone is faster, from opening apps to web pages.
Very strange... Not sure why there would be so much ART incompatibility, but I guess it's 4.4.2 and not .3 or .4. If anyone else has has this problem (including an inability to wake the phone up without a few tries), check your RunTime. I'm hoping it'll be better next update, but for now this'll have to do.
Sent from my LG G3 Cat.6 using Tapatalk
Click to expand...
Click to collapse
Hi there!
I have exactly the same problem since I updated the phone to Lollipop (D85520A) but before that I didn't have that problem. Firstly I found this when I updated to D85519H and then I performed another update to the current version (D85520A) and it didn't help. The smartphone is way better, but this problem is really ennoying me.
ART is not available on Lollipop and my phone went only for one day to ART mode and it was a pain in the ass (when I still had 4.4.2) and then I switched back to normal.
I am thinking about to a factory reset and reinstall Android 5.0 on CSE mode AGAIN and see what happens, but I think it won't help at all.
Do you have any idea of what could I do in order to solve this problem?
Thank you in advance.
Fixed
Hi there!
Just a short update.
Like I mentioned before, I got this problem when I updated my phone with the new Lollipop FW (D85519H) and then I tried to perform another update using the D85520A but the problem was still there. So I believe that the update didn't fix the issue from the previous update so I performed another clean update using the same last one and the problem disappeared.
Thank you anyway.
juansavage said:
Hi there!
Just a short update.
Like I mentioned before, I got this problem when I updated my phone with the new Lollipop FW (D85519H) and then I tried to perform another update using the D85520A but the problem was still there. So I believe that the update didn't fix the issue from the previous update so I performed another clean update using the same last one and the problem disappeared.
Thank you anyway.
Click to expand...
Click to collapse
I have the same problem. What do you mean by "clean update"?
ZHENURIK said:
I have the same problem. What do you mean by "clean update"?
Click to expand...
Click to collapse
Probably CSE flash with this method: http://forum.xda-developers.com/showthread.php?t=2785089
Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.
nelson2006 said:
Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.
Click to expand...
Click to collapse
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.
snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
I haved tried the first two steps and no luck at all. Maybe this weekend I'll try the third one. Thank you for the reply.
snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
RoyaLKurTx3 said:
On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.
Click to expand...
Click to collapse
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.
nelson2006 said:
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.
Click to expand...
Click to collapse
The problem, in fact is a fault in the hardware problem. If it's still under warranty, request a new phone.
I have, apparently, one of those sw3's that will not accept the MM OTA so that the watch will work after is successfully installs. I am having to reinstall the LCA43 ROM in order to get the watch to work. While I would like to have MM, I can't seem to find the right ROM to install and XC is no help in either the software repair or update. The issue is when MM is on the watch, it continually stops at the 4 dots or symbols and never goes any further. I am using Ubuntu to connect to the watch for repair.
Is there a way to stop the OTA updates while still being connected to the phone via BT? I was happy to get this watch going again, but was disappointed this morning when it tried to boot in MM without me installing it.
Edit: This may be resolved. I installed a different ROM yesterday, 5.1.1.2, and it did not automatically try to upgrade last night so I may be good to go.
Hello guys,
I managed again to brick my phone.
I flashed Fulmics as I wanted to swap from those not fully stable nougat roms. Well, I have no idea what caused my problem - Fulmics run without prolbems for a 2 or 3 days including xposed etc.
Then today I changed my ChromePie options and that's when the reboots began. I don't know if this the real cause was though.
So I tried to flash another rom but always got random reboot even in recovery after few minutes/seconds. So I went all the way back to stock rom (4.4.2) with LG Flash tool - which worked after a few tries. Then I installed MM rom via .kdz file and flash tool 2014, which also worked after a few more tries. But then the reboots started again. Can't say if the 4.4.2 rom was without boots because I updated to 6.0 quite quickly.
The strange thing is that after some reboots phone won't boot again and I have to take and leave out the battery for some time to boot the phone again.
Any solutions for my problems?
Best regards
..bumped into the same 1/2 year ago. Didn't want to put to much effort so,..went to stock and back, worked for me.
Good luck.
Gerhard.M said:
..bumped into the same 1/2 year ago. Didn't want to put to much effort so,..went to stock and back, worked for me.
Good luck.
Click to expand...
Click to collapse
Which stock and how did you go back?
As mentioned I already went back to stock but the issue kept occuring.
Hi, got the same problem with my G3
wi fi and bluetooth didn't work and phone loop rebooted
Here below the steps I followed to solve
1) First attempt (didn't solve): had cloudy rom, got back to stock official but still rebooting, tried fulmics and other rom but problem persisted.
2) second attempt (didn't solve): went back to stock and changed battery (found somewhere in internet), now I have a brand new battery but a phone still loop rebooting
3) third attempt (SOLVED): found that the wi-fi / bluetooth chip (one for both) copuld have unwelded and solved so (it appears I can't post outside link, delete spaces to have the correct link):
youtube .com / watch?v=1zWpzYh2DPI&t=15s"
youtube .com/ watch?v=6_0jzp65eLY&t=256s
Now i'm on fulmics and no more loop reboot
Hope you can solve
[sorry for my english]
frosty234 said:
Which stock and how did you go back?
As mentioned I already went back to stock but the issue kept occuring.
Click to expand...
Click to collapse
http://stockroms.net/file/LGG3/D855/European/BIN_LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G-0.zip
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/D855/
used flashtool
have to say restoring and/or flashing isn't always that stable. I've experienced it sometimes needs a 2nd try.
Hopefully it isn't a hardware issue in your case.
So I tried all of oyur suggestions but nothing seems to work.
On the contrary I ended up in a status where I can't even flash a new firmware.
In LG Flash Tool 1.8.1 I get the error
"Donwload Fail!!!"
PID: NULL
IMEI: NULL
MODEL:
DLL: D855
BIN: LGD855AT.....
SWV:
SWOV:
Model Information Check Fail!
000000000
Click to expand...
Click to collapse
In LG Flash Tool 2014 (flashing MM with kdz file) phone shuts down in middle of process.
But I can still access Download Mode.
No more ideas?
I really think I finally broke my phone... But the fact that I can still access download mode keeps my hopes up.
So, after 2 months I just tried to reawaken my phone. Still the exact same problem. It just keeps shutting down aber some while, but just when I start flashing something. If it stays connected to computer whitout doing anything it can stay on for like ever.
Can anyone confirm that this could be a hardware defect?
Hi,
Since I got the latest Oxygen OS update (I'm on Oxygen OS 9.0.4) . My Phone App has started crashing if I make a outgoing call or get one. First the Phone App crashes and then the system UI Crashes. The Phone was working fine till this update.
Thinking this is an issue with the Oneplus Oxygen OS update, i tried to move to Pixel Experience OS. The version I installed worked well but again when i did a OTA upgrade the same issues started recurring. There I also faced crashes if I used the camera app.
Frustrated I moved back to the Stock Rom.. But the Problem of the Calling app still exists. I"ve tried installing alternate diallers but its the same effect. I'm attaching my log file here : https://drive.google.com/file/d/1nLldKekVd_ZLWRghbPeJP94cdimQpsf6/view?usp=sharing
Can you guys help figure out whats happening ?
coolparth said:
Hi,
Since I got the latest Oxygen OS update (I'm on Oxygen OS 9.0.4) . My Phone App has started crashing if I make a outgoing call or get one. First the Phone App crashes and then the system UI Crashes. The Phone was working fine till this update.
Thinking this is an issue with the Oneplus Oxygen OS update, i tried to move to Pixel Experience OS. The version I installed worked well but again when i did a OTA upgrade the same issues started recurring. There I also faced crashes if I used the camera app.
Frustrated I moved back to the Stock Rom.. But the Problem of the Calling app still exists. I"ve tried installing alternate diallers but its the same effect. I'm attaching my log file here : https://drive.google.com/file/d/1nLldKekVd_ZLWRghbPeJP94cdimQpsf6/view?usp=sharing
Can you guys help figure out whats happening ?
Click to expand...
Click to collapse
try clean flash any beta version of oos , or use unbrick tool to restore all firmware to factory setting.
Hi
Would this be the unbrick tool ? https://www.google.com/amp/s/forum....5t-unbricking-tool-confirmation-t3733012/amp/
Seems like a very old version ?
Hello
I tried doing the clean flash to the latest Beta.. But still getting the crashes. Will try un bricking now.. However is there a chance its related to the hardware ?
coolparth said:
Hello
I tried doing the clean flash to the latest Beta.. But still getting the crashes. Will try un bricking now.. However is there a chance its related to the hardware ?
Click to expand...
Click to collapse
no, perhaps its related to software. are u using any mod or theming?
Hi,
Currently none. The phone was on Stock Oxygen till 3 odd months ago and was working fine. After one of the OTA Updates, this problem started happening. Since I could not find any consistent users reporting the same issue on Oxygen, I decided at that point to try using a different ROM and switched to Pixel experience. The phone worked ok for 2 weeks or so post that. Again after a new OTA came and I upgraded it started crashing again.
In the team time i saw another update to Oxygen had come so it thought i'd try going back to stock.. But not avail. Its still crashing.. Its only the Phone App that acts up. Everything else works fine. However the first time this issue came video playback was also freezing.
The logs that i have posted show these crashes but I dont have enough knowledge as yet to understand the reason.
After the above response to try clean flashing the latest Beta. But the issue persists..
Try see if the phone app is set as standard app for handling phone calls.
Hi
Tried that ..it is set as default.. The latest trial I did is cleanflashed an older version official ROM v5x of Oxygen OS... Problem is still the same..
Infact worse.. now I've got the settings app crashing and random reboots in addition to the phone app crashing !
I'd thought if this issue is due to post 9.02 upgrades this would solve it . But it's made it worse..
Parth