Related
Greetings.
Very recently, there was an official/OTA update for P7-L10. And I subsequently downloaded and tried to update it as soon as it finishes downloading.
But, when it tried to update, it keeps failing. Is the update wrong? or is there something missing that I am not clearly seeing it?
My current version, out of the box - P7-L10V100R001C00B133SP01
and the update (online update) is (as mentioned) : P7-L10_SouthPacific_C00B620.
Please advise me on what might have went wrong?
Thank you.
piring said:
Greetings.
Very recently, there was an official/OTA update for P7-L10. And I subsequently downloaded and tried to update it as soon as it finishes downloading.
But, when it tried to update, it keeps failing. Is the update wrong? or is there something missing that I am not clearly seeing it?
My current version, out of the box - P7-L10V100R001C00B133SP01
and the update (online update) is (as mentioned) : P7-L10_SouthPacific_C00B620.
Please advise me on what might have went wrong?
Thank you.
Click to expand...
Click to collapse
Do you have custom recovery?
ibeqa said:
Do you have custom recovery?
Click to expand...
Click to collapse
Hey there, thank you for the reply.
I'm not sure, how to check. But I have never rooted this phone yet.
piring said:
Hey there, thank you for the reply.
I'm not sure, how to check. But I have never rooted this phone yet.
Click to expand...
Click to collapse
Do you have TWRP or CWM installed? Was your phone brand new or pre-owned? Do you have custom rom or stock rom?
ibeqa said:
Do you have TWRP or CWM installed? Was your phone brand new or pre-owned? Do you have custom rom or stock rom?
Click to expand...
Click to collapse
Nope, I do not have those installed. This is a brand new phone running stock rom.
Ok, I guess your phone is not branded (vodafone, orange, etc.), so get the b609 update and install it.
If you had firmware 133, how come you got SAE update? Where did you buy your phone?
ibeqa said:
Ok, I guess your phone is not branded (vodafone, orange, etc.), so get the b609 update and install it.
If you had firmware 133, how come you got SAE update? Where did you buy your phone?
Click to expand...
Click to collapse
Yep, it's not. Hmm. I am unsure as to how or where I can get the B609 update, because ever since I first laid my hands on this phone, it has been running B133 out of the box. And, since, in between then and now, I have been going to the system update to look for any update prior to this one that I am currently having a problem to update, and there was no new update (until, again, now )
Also, previously I did went online on my PC to find an update B609, and downloaded it and tried to do a local update. and unfortunately for me, it caused my phone to be soft-bricked, and back then, I have not turned on my USB debugging or did any major changes to my phone, thus, requiring me to send my phone to the service centre. So, I'm kinda weary about downloading an update online from my PC, as of now.
Well, I am not sure what SAE is, and to answer that question, again, I do not know how I may have gotten the update. I bought my phone from where I am currently living, Malaysia.
Can you make a print screen of your SAE update problem?
sorry, but um, can you please enlighten me as to what is SAE? I am truly sorry for not knowing this.
piring said:
sorry, but um, can you please enlighten me as to what is SAE? I am truly sorry for not knowing this.
Click to expand...
Click to collapse
SEA is the code Southeastern Asia
Ohhh. haha. Sorry, was wondering what SAE was. Will update as soon as possible.
ibeqa said:
Can you make a print screen of your SAE update problem?
Click to expand...
Click to collapse
Hey there, I couldn't really printscreen it, as it was in the updating process (the one with the Android bot and the black screen behind) anyway, it just it failed. That's all.
Here's however, a printscreen of the update.
piring said:
Hey there, I couldn't really printscreen it, as it was in the updating process (the one with the Android bot and the black screen behind) anyway, it just it failed. That's all.
Here's however, a printscreen of the update.
Click to expand...
Click to collapse
So OTA fails., what's the code of error (why it fails)?
Also, you can try manual update or the "3 button update" (it is described in the forum).
But the most important thing is to know why it fails.
P.S. You can take print screens from the Hisuite during update or when it fails
piring said:
Hey there, I couldn't really printscreen it, as it was in the updating process (the one with the Android bot and the black screen behind) anyway, it just it failed. That's all.
Here's however, a printscreen of the update.
Click to expand...
Click to collapse
Hi piring, I've encounter the same issue with updating from B133SP01 to B620, my set is a"SOUTH PACIFIC" model.
I even brough my set to the huawei service centre to see if the technician over there can solve the issue but unfortunately, they are just as clueless as I am..... They did a factory reset of my set and tried to install the update again but the update still fail to install. There is no error code but only "fail" word appearing. They claim it's because my set was rooted but when I have unroot my phone, it still.can't update.
So if you managed to successfully updated your set, can you share with me how to go about it? Thanks.
[email protected] said:
Hi piring, I've encounter the same issue with updating from B133SP01 to B620, my set is a"SOUTH PACIFIC" model.
I even brough my set to the huawei service centre to see if the technician over there can solve the issue but unfortunately, they are just as clueless as I am..... They did a factory reset of my set and tried to install the update again but the update still fail to install. There is no error code but only "fail" word appearing. They claim it's because my set was rooted but when I have unroot my phone, it still.can't update.
So if you managed to successfully updated your set, can you share with me how to go about it? Thanks.
Click to expand...
Click to collapse
Oh. well, to be honest, I kinda given up hopes on how to update it. And with that, I am still clueless as to how to update it. I have tried using HiSuite, but to my surprise, HiSuite mentioned that my phone is already up to date. So, I am honestly puzzled as to how my phone is pushing for an OTA, but HiSuite insists that my phone model is of current and latest update.
Sorry I am unable to help you.
piring said:
Oh. well, to be honest, I kinda given up hopes on how to update it. And with that, I am still clueless as to how to update it. I have tried using HiSuite, but to my surprise, HiSuite mentioned that my phone is already up to date. So, I am honestly puzzled as to how my phone is pushing for an OTA, but HiSuite insists that my phone model is of current and latest update.
Sorry I am unable to help you.
Click to expand...
Click to collapse
Hi piring, same thing goes for my HiSuite as well. It's kinda of sucks that the update is available but can't update. It's even more worse that Huawei service centre cannot do anything about it and just tell me forget about the update and ignore the notification. Now i have a phone with a permanent notification mark that i cannot get rid of.
P7-L10 is a good phone but the support i'm getting from Huawei service centre is really unprofessional and disappointing.
But anyway, thanks for your reply.
Hi, now before I start I apologize if this has been covered or if this has not yet been explained very well.
Recently my phone experienced some water damge to which the pkwer button now does not respond-or when it does, very sporadicly- now I read somewhere about remapping buttons, to say volume down being a wake button. But when I went about the task of doing so the methods I found did not work. First I found an sdk on an forum here which did little to solve. Then I moved onto Xposed and a module made for this. Although installj g the frameowrk with my phone somehow had some known issues, and wouldnt install... so lastely I tried editing the keyboard .kl file in /system and again had no success as tyere was no way to gain r/w privileges.
Would anyone be able to shed some lihht on this issue.
Phone is fully rooted and is running originalrom. Android ver 4.4.2 EMUI 2. 3 btw
Also I saw a custom rom for the p7 that had Xposed embed so wondering if this would work as a workaround??
Cheers and apologies if anything here doesnt make sense
Did you ask for replacement at your local repair? Alternatively you may DIY for a fiver, search Side Key Flex Cable for Huawei Ascend P7.
Cheers, good luck!
Printusrzero said:
Did you ask for replacement at your local repair? Alternatively you may DIY for a fiver, search Side Key Flex Cable for Huawei Ascend P7.
Cheers, good luck!
Click to expand...
Click to collapse
Thanks but I was more looking for a way to change buttons. And does anyone know if it is possible to flash a custom rom to the phone if the power button does not work. Eg boot recovery menu is unusable atm...?
You can reboot into recovery using ADB:
Code:
adb reboot recovery
Or using any reboot applications from Play Store.
Hi all,
First post so please be gentle . I am currently on 5.1 on my 2nd gen device. For some reason I haven't received the MM update over the air. I was wondering if I really need to install a custom ROM at all? I am in the UK and my model is lpe23.32-25.3. Added a a screenshot to be slightly more helpful.
I got the update some time ago. Can you confirm it is an xt1092, and the system version?
Moto X Update
Indeed. Noob problems but I cant seem to be able to attach an image to this reply.
I can't post the screenshot either since I am a new user but yes the model is XT1092 and system version 23.16.3.victara_retgb.retgball.en.GB retde
Ok, if the system version is as you say there's a slight mismatch between GB and de at the end. Did you buy it second hand? Check in the fastboot to see if it's been unlocked (there are guides in the general forum). Have you tried to factory reset and see if the update cones through that way?
I sent it off to repair the screen and there was a issue with the device. Long story short Motorola messed up when returning the device and rather then send me the correct one they provided me with someone else's phone. I shall try the factory reset but I suspect that the bootloader has been modified leaving me with no option but to install the OTA myself? Or do I have any other option?
Hey guys,
Any chance I would be able to do this over the air? Planning on flashing the phone tomorrow and just do the installation that way
I think you need to read all the flashing guides and have a good idea of using fastboot, if you don't already.
Guys, i need your help, i am having a problem with screen-lock on nexus 6 build number NBD91X, kernel version 3.10.40-ge50fdd2 running android 7
i can easily bypass screen lock by pressing on emergency and then the back button, that's it and the phone is unlocked!!!!
any body else having the same issue ? and how to fix it
appreciate your support
Thx
meakha said:
Guys, i need your help, i am having a problem with screen-lock on nexus 6 build number NBD91X, kernel version 3.10.40-ge50fdd2 running android 7
i can easily bypass screen lock by pressing on emergency and then the back button, that's it and the phone is unlocked!!!!
any body else having the same issue ? and how to fix it
appreciate your support
Thx
Click to expand...
Click to collapse
I just tried it out on my N6, 7.1.1 build N6F26Q. No issue, phone's still locked.
Same here on N6F26Q - no problem, phone remains locked.
meakha said:
Guys, i need your help, i am having a problem with screen-lock on nexus 6 build number NBD91X, kernel version 3.10.40-ge50fdd2 running android 7
i can easily bypass screen lock by pressing on emergency and then the back button, that's it and the phone is unlocked!!!!
any body else having the same issue ? and how to fix it
appreciate your support
Thx
Click to expand...
Click to collapse
I have the same exact build and kernel and do not have the same issue as you. Still stays locked.
Maybe a trusted bluetooth connection.
Can you give us exact steps to replicate?
Sounds like you might have a root-kit exploit on your phone...
Note10.1Dude said:
Sounds like you might have a root-kit exploit on your phone...
Click to expand...
Click to collapse
how can i fix that ?
I've solved the issue by flashing the Official OTA 7.1.1 Image, thx for the support guys
Hi, phone (EVA-L09) was previously Vodafone branded and freshly upgraded to nougat.
After that the touchscreen sometimes doesn't respond to user input.
It's like you scroll down and if you want to immediatly scroll up it's not responding.-
Wait 2 minutes and it works again.
It's not bound to a specific region on the screen.
I downgraded to Android 6 via the debranding method and the touchscreen worked again as expected.
I then upraded to Nougat (B183) via OTA update and the touchscreen showed the same weird behaviour.
Also did a factory reset incl. internal storage.
Still no chance.
Anybody an idea, why the touchscreen isn't working in Nougat but works flawlessly in MM?
kwasi76 said:
Hi, phone (EVA-L09) was previously Vodafone branded and freshly upgraded to nougat.
After that the touchscreen sometimes doesn't respond to user input.
It's like you scroll down and if you want to immediatly scroll up it's not responding.-
Wait 2 minutes and it works again.
It's not bound to a specific region on the screen.
I downgraded to Android 6 via the debranding method and the touchscreen worked again as expected.
I then upraded to Nougat (B183) via OTA update and the touchscreen showed the same weird behaviour.
Also did a factory reset incl. internal storage.
Still no chance.
Anybody an idea, why the touchscreen isn't working in Nougat but works flawlessly in MM?
Click to expand...
Click to collapse
Do a HARD RESET
Rafa Mistry said:
Do a HARD RESET
Click to expand...
Click to collapse
I already did that but still no luck
Same problem here. With c432b386 the touchscreen works bad. B182 works perfectly. I don't know how to repair this...
Anybody around here with a high Version. Is it probably fixed in later versions? - or anybody with the same problem?
PiX3LaDo said:
Same problem here. With c432b386 the touchscreen works bad. B182 works perfectly. I don't know how to repair this...
Click to expand...
Click to collapse
Just made an interesting discovery.
I you switch the phone to landscape the touchscreen is working fine.
So it's somehow related to the display mode.
Can you confirm this?
...and the next finding:
I enabled "Show visual touch feedback" which shows a marker wherever a touch is registered on screen.
All touches are registered correctly and shown by the marker there are just times where the OS doesn't react upon these touches.
It's like if the GUI thread gets stalled for some reason and then works again.
Definitly not a HW problem buzt also no idea how this can be fixed
-Go to settings>smart assistance and try disabling enabling gloves mode. (It changes the screen sensitivity)
-Do you have a tempered glass screen protector?
When yes try removing it.
- Try installing a Rom like BlueWei or Moonlight (With BlueWei v3.7 you get Nougat B390)
Same issue
I have the same exact issue i debranded ee uk p9 now im running nougat.
I have to slightly swipe and press the screen to use it properly did you find any fix for that?
Same problem for me. Any EMUI 4.x.x works fine, but any EMUI 5.x has scroll issue. Someone found fix for that?
Video
I guess I am not alone with this issue. I can run ANY version of Marshmallow just fine but as soon as I update it to Nougat (B361 or B389) my touchscreen will not allow me to scroll. I can tap an icon and launch any app but I cannot scroll anywhere on my screen. No fixes???
Same issue here. I had to switch to custom rom to solve this issue. Resurrection remix works good.
Do you have a refurbished or repaired P9?
Rucha said:
Do you have a refurbished or repaired P9?
Click to expand...
Click to collapse
Mine is refurbished.
---------- Post added at 09:59 PM ---------- Previous post was at 09:58 PM ----------
BussanyiG said:
Same issue here. I had to switch to custom rom to solve this issue. Resurrection remix works good.
Click to expand...
Click to collapse
Thanks for the info. I may give this a try.
On mine I did myself the repair of the screen, because it was cracked. But this error with the touchscreen started to appear only when I updated the phone to the EMUI 5.
It looks like all we have not original screens that is not supported in EMUI 5 anymore. Probably they changed driver in new version.
It can be possible. Custom rom is better for me, I just miss the EMUI camera app.
BussanyiG said:
I just miss the EMUI camera app.
Click to expand...
Click to collapse
It's a big deal!
The quality of the picture from the RROS rom is good by I think the black& white camera is not working. Just the RGB one.
Taking touch/display driver from RROS and using it by overriding existing one in original ROM would be good solution.