Related
I have just managed to root my old LG P880/4xHD using advice from this forum. Thought I would try on an old phone first. One reason I tried is because I cannot update Android via the usual About phone, Software updates, Check now for updates. The Android version installed is 4.0.3. I am in Australia and it is possible the phone is an overseas model (got it from a friend in LG). Has "Not for Resale" stamped inside the back cover. When I try to update Android, I get an error message "Registered Error - Your device is not registered yet." I had hoped rooting would get around this but it hasn't. Have looked up old forum posts and there is talk of using .kdz files and all sorts of other things. Can anyone help me get around this registration issue but please be aware I am a novice and most of the older posts I read, I couldn't understand so simple explanations please. Thanks.
What you have is developer or test device and it is a bit different from normal ones. Try googling more but you will have hard time....
Sent from my microwave.
dimi89 said:
What you have is developer or test device and it is a bit different from normal ones. Try googling more but you will have hard time....
Sent from my microwave.
Click to expand...
Click to collapse
Could it be that it has overseas firmware, I read in a two or three year old post that this can happen but there was a way to get around this.
PD
pdonahue said:
Could it be that it has overseas firmware, I read in a two or three year old post that this can happen but there was a way to get around this.
PD
Click to expand...
Click to collapse
So...Did you try flashing kdz file and updating it that way or ... ?
pdonahue said:
I have just managed to root my old LG P880/4xHD using advice from this forum. Thought I would try on an old phone first. One reason I tried is because I cannot update Android via the usual About phone, Software updates, Check now for updates. The Android version installed is 4.0.3. I am in Australia and it is possible the phone is an overseas model (got it from a friend in LG). Has "Not for Resale" stamped inside the back cover. When I try to update Android, I get an error message "Registered Error - Your device is not registered yet." I had hoped rooting would get around this but it hasn't. Have looked up old forum posts and there is talk of using .kdz files and all sorts of other things. Can anyone help me get around this registration issue but please be aware I am a novice and most of the older posts I read, I couldn't understand so simple explanations please. Thanks.
Click to expand...
Click to collapse
Its a year old phone, its not like its the nexus one or samsng galaxy s2...
Try flashing 4.12 with kdz. Google is your friend, try kdz flash 4.1.2 Optimus 4x hd.
Funny thing, when I bought my phone, only google asked me to register the phone, the usual Google Play thing. SO what do you exactly mean with REGISTER?
i think the whole phone isn't registred by LG for consumers, like dimi89 said it has to be a dev device. they aren't registred and cannot be updated/used the normal way. the serial number of this phone isn't present in the LG databases i think. Just flash kdz and everything is fine. You know that you don't get any support or warranty on that phone but you should know that.
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.
Hey everyone,
So I got a P9 Plus and I tried to force the Android 7.0 EMUI 5.0 update on it, it didn't work..probably because I made a mistake which I'm unaware of.
Problem is, I'm away from home and I don't have the Box with me with the bootloader code, which means I can't really do it again right?
I tried using DC unlocker 2 and DC Pheonix but both failed, when I got to the eRecovery menu and tried to update from there (I used a B103 build, pasted in a dload folder on the SDcard) it says can't install update or something like that, my build before everything was VIE-L09C900B181, can't seem to find a stock ROM for that build (I gotta mention I'm really new to all of this when it comes to phone stuff, I'm used to work with CMD and Linux but this is territory unknown for me lol). Any advice? What can I do? When I try to restore it or force a factory reset it also says "Reset failed" right away...I'm lost you guy....PLEASE HELP ME
First of all if u have a P9 Plus and search for firmware in the p9 forum you are in the wrong place.
Did u ever made an OTA? I think dload tries the internal storage first so maybe this is why your dload attempt did not work - try formatting internal storage with fastboot (dont know if u can)
Basically you just have to find the right firmware. Maybe you need to downgrade first.
But again you are in the "P9" forum so you are probably wrong since you are talking about an "P9 Plus".
xtcislove said:
First of all if u have a P9 Plus and search for firmware in the p9 forum you are in the wrong place.
Did u ever made an OTA? I think dload tries the internal storage first so maybe this is why your dload attempt did not work - try formatting internal storage with fastboot (dont know if u can)
Basically you just have to find the right firmware. Maybe you need to downgrade first.
But again you are in the "P9" forum so you are probably wrong since you are talking about an "P9 Plus".
Click to expand...
Click to collapse
My bad, guess I didn't do enough research to see that there was a P9 Plus section, sorry about that.
An OTA? Sorry like I said I'm pretty new to this, I had the build that ends with 181 and I tried using the 103 build but I always get errors, can't seem to find a 181 build online to download.
Thanks for the reply by the way
CelticJ said:
My bad, guess I didn't do enough research to see that there was a P9 Plus section, sorry about that.
An OTA? Sorry like I said I'm pretty new to this, I had the build that ends with 181 and I tried using the 103 build but I always get errors, can't seem to find a 181 build online to download.
Thanks for the reply by the way
Click to expand...
Click to collapse
Where you from my friend? We probably get around this ****....
We need some way to communicate faster, u have Steam or Origin or something?
xtcislove said:
Where you from my friend? We probably get around this ****....
We need some way to communicate faster, u have Steam or Origin or something?
Click to expand...
Click to collapse
Try dc-phoenix but be careful with factory flash. avoid it if you don't have all partitions backed up.
I had to flash it with factory soft and now i stuck with unbricked phone but not being able to make phone calls
Good evening all.....
I have already search for this amongst the forums but unfortunately I could not find anything so I am hoping you are able to help.
I currently own a Huawei P9 EVA-L09C440B138 with EMUI 4.1 - Android 6.0 Installed, locked to EE-UK. My partner has the same mobile but with a different network and she received the update to EMUI 5.0, Android 7.0, MONTHS ago. You may or may not have heard, all EE customers with Huawei P9's seem to be suffering from the same problem, and whenever we approach EE we get the same bull**** response "when the update is ready you will be notified", no timescale, nothing.
So my question is, is there a way I can bypass the standard update procedure as I fear I will never get that update, or am I going to have to be patient and wait until further notice.
Any advice would be much appreciated.
Many thanks guys
See this link to get started:
https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
retsilred said:
See this link to get started:
https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
Click to expand...
Click to collapse
Thank you very much for this it looks relatively simple to do but would you be able to advise me if I need any preliminary software or if I need to do anything prior to installing this update. Is there a plan B in case there is potential for my phone to be bricked. If I were to in future self this device to a shop would they be able to tell that this was not a genuine update directly from Huawei?
Whighty383 said:
Thank you very much for this it looks relatively simple to do but would you be able to advise me if I need any preliminary software or if I need to do anything prior to installing this update. Is there a plan B in case there is potential for my phone to be bricked. If I were to in future self this device to a shop would they be able to tell that this was not a genuine update directly from Huawei?
Click to expand...
Click to collapse
Nothing extra needed.
There's always a plan B, there's several threads on her for recovering a bricked P9.
If you don't tell them, they'll probably never notice.
I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.
suain81 said:
I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.
Click to expand...
Click to collapse
I'm not sure, but worth a try,I warn the site is Russian, here's how to edit NT code https://4pda.ru/forum/index.php?showtopic=951883&view=findpost&p=100635159 here is a list of NT codes:View attachment NT_code.txtunfortunately needed root!working with QFIL do backup ftm.bin!
lexih said:
I'm not sure, but worth a try,I warn the site is Russian, here's how to edit NT code here is a list of NT codes:View attachment 5134107unfortunately needed root!
Click to expand...
Click to collapse
Thank you for your reply. Yes, I have read many instructions even on this page how to edit, cust_path_mapping.cfg, and that it's surely easy once the phone is rooted. But that's why I first wanted to see the possibilities to do this without that I have to root the phone.
suain81 said:
I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.
Click to expand...
Click to collapse
So, u have 2 problems right? u want to upgrade to v405ebw30c, but can't, and you also have the nt-code error right?
First, no, they aren't related. I think that's highly unlikely. That's not something lgup checks for. I'd bet you're using the 1.14 version dll and should be using the 1.16 dll and should be doing a refurbish.
As far as the nt-code error. It's a pain, lots and lots of info about fixing it, most of them need root. But here's what worked for me, no root needed: I switched from att pie to Korean open Q (first time had the nt-error and no editing anything would fix it), so went back to att and then did the korean 409N again, first with partition DL. Let that finish, it has to reboot the phone completely to finish. Then, don't change the phone in anyway, just shut it off. Back to LGUP and do a Refurbish with the same kdz.
No more nt-error code. It *seems* that nt-error code info gets propagated to various partitions as a part of refurbish. I verified that the ftm partition, where that information lives, was completely spaces (blank) after the refurbish... it's odd, I know. But for whatever reason, I no longer have the nt-error code problem.
cheers
AsItLies said:
So, u have 2 problems right? u want to upgrade to v405ebw30c, but can't, and you also have the nt-code error right?
First, no, they aren't related. I think that's highly unlikely. That's not something lgup checks for. I'd bet you're using the 1.14 version dll and should be using the 1.16 dll and should be doing a refurbish.
As far as the nt-code error. It's a pain, lots and lots of info about fixing it, most of them need root. But here's what worked for me, no root needed: I switched from att pie to Korean open Q (first time had the nt-error and no editing anything would fix it), so went back to att and then did the korean 409N again, first with partition DL. Let that finish, it has to reboot the phone completely to finish. Then, don't change the phone in anyway, just shut it off. Back to LGUP and do a Refurbish with the same kdz.
No more nt-error code. It *seems* that nt-error code info gets propagated to various partitions as a part of refurbish. I verified that the ftm partition, where that information lives, was completely spaces (blank) after the refurbish... it's odd, I know. But for whatever reason, I no longer have the nt-error code problem.
cheers
Click to expand...
Click to collapse
Thank you for your reply. No I don't know if they're related either, it was just a guess since the problems started at the same time. Well, I always had a kind of "problem" since I never have been able to upgrade from LG Bridge. And that I guess is from the NT-code. But the sign in the start appeared after the Android 10 upgrade. However, I'm using LGUP 1.16.0.3 and I have used it everytime, with DLL version 1.9.39.7.
And actually it wouldn't bother me too much having this sign in the start anyway, I only restart the phone like once per week. But of course it bothers me that I can't make the upgrade like before. And I can also mention that I have never tried to refurbish with LGUP, only upgrades, because I have some bank apps etc. that are a bit complicated to reinstall. Of course it's possible, but I have to be mentally prepared for it. So I'll only do that when I know there's no other option. And the phone work good today, so I'm not in a rush, but in a couple of months I should be doing an upgrade of course.
And thanks for telling me the other option too, I will surely try it one day but since it also requires refurbish I will try after I fail to make the normal refurbish.
I don't have any experience of rooting, if I root my phone, will I keep all the data or is it comparable to refurbish? Are the any other risks rooting the phone? I'll lose the warranty, but I don't really have the warranty anyway since it's not an official product in my country.
suain81 said:
I don't have any experience of rooting, if I root my phone, will I keep all the data or is it comparable to refurbish? Are the any other risks rooting the phone? I'll lose the warranty, but I don't really have the warranty anyway since it's not an official product in my country.
Click to expand...
Click to collapse
No, to root, you loose all data and have to start again. Part of rooting is to flash dm-verity which turns off encryption. But, that allows you to do a backup of the data partition once you've reinstalled everything. The positive side there is that in the future, you could back up that partition (data), make any other changes, then flash data back, and your apps would be back as they were.
Other risks? Well, maybe, if the phone was stolen I guess, it would be easier for someone to steal your data. Your situation, with serious banking apps, it **may be** you don't want that risk...
Maybe for just trying a refurb to lose nt-code, look at LG's 'restore' from previous device ability, use it to save off the apps somewhere, then restore after refurb? no root needed.
cheers