Database Develop

LG 4xHD not registered

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.

[Q] Online Update for SEA Region failed

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.

Stuck On Google Logo and didnt Check Unlock OEM

Hi All,
So I have been searching the interwebs for the last four hours with no luck.
I have a Nexus 6 and I was trying to update the OTA developer preview from google that I signed up to test.
Problem is that I ended up on a bootloop. I am able to get into Fastboot but I am unable to make any commands work since the device is locked. All commands end with a Failed (command write failed error).
I am able to go into recovery to access ADB but that is also not very useful because it seems i am unable to push anything to the phone. The only thing which seems to want to work is when I try and load an OTA image.
This loads until 100% and I get an error which says the image I have is to new and it requires a specic image.
I am currently on 6.0.1/MMB29V/2554798.
I have tried factory reset but no help there.
Also when I try select update from SD Card it says it Couldnt mount/sdcard.... Unknow volume for path
Any help?

qbzee007 said:
Hi All,
So I have been searching the interwebs for the last four hours with no luck.
I have a Nexus 6 and I was trying to update the OTA developer preview from google that I signed up to test.
Problem is that I ended up on a bootloop. I am able to get into Fastboot but I am unable to make any commands work since the device is locked. All commands end with a Failed (command write failed error).
I am able to go into recovery to access ADB but that is also not very useful because it seems i am unable to push anything to the phone. The only thing which seems to want to work is when I try and load an OTA image.
This loads until 100% and I get an error which says the image I have is to new and it requires a specic image.
I am currently on 6.0.1/MMB29V/2554798.
I have tried factory reset but no help there.
Also when I try select update from SD Card it says it Couldnt mount/sdcard.... Unknow volume for path
Any help?
Click to expand...
Click to collapse
Very difficult. Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=3053783

NLBeev said:
Very difficult. Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=3053783
Click to expand...
Click to collapse
Tried it and it seems I have no other option but to return.
Problem is that i am in South Africa and have no idea how to go about.
Bought off Amazon

http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/

qbzee007 said:
.....Problem is that i am in South Africa and have no idea how to go about.
Bought off Amazon
Click to expand...
Click to collapse
your n6 is bricked and you could try all the options from XDA.
There is a thread about the Nexus Root Toolkit of Wugfresh. This kit runs on a Windows PC and has a menu with option for bricked phones.
When you can start in recovery mode (long press start button + volume down) you could give it a try. http://forum.xda-developers.com/showthread.php?t=2947452
When there is no result, you could send it to Amazon for repair. But check the costs.
The total costs of mail, assurance and repair are probably more than $ 100,=.
I have seen some posts that the of a new N6 is every month lower.

TriguyRN said:
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Click to expand...
Click to collapse
I was going to suggest this too. The link posted leads to this link that has instructions on installing.

alryder said:
I was going to suggest this too. The link posted leads to this link that has instructions on installing.
Click to expand...
Click to collapse
Thank you very much.
This worked.
Booting as I type this. Best Easter Monday gift.
Thanks Again

Help reflashing stock Android

Hello.
My Nexus 6 is out of warranty, so I'm doing my best to get it working myself because I can't get it replaced for free.
So, several months ago, my Nexus 6 (running Android 6.0.1 MOB30O) restarted on its own and showed a "Device is corrupt" message before booting (information at g.co/ABH; red error). I was concerned about the security of my device, so I performed a factory reset. Upon trying to set the phone up again, I found that after connecting to Wi-Fi, the phone would loop indefinitely while periodically saying that Google Play Services has crashed. I once tried leaving it overnight while it was "Checking connection" or whatever, and it still did not move to the next phase of setup. I have tried this on several different networks, and when I intentionally use a wrong password, the phone doesn't connect. So, I have no reason to believe the Wi-Fi connection is the problem. I have tried performing a factory reset from Android Recovery dozens of times, and it still doesn't work. So, I'm effectively limited to the boot menu to interact with my phone (so, I can't access Developer Options because I can't set up my phone). Also, most of the times I boot up my phone, I still get that red error during boot.
So, I've been trying to reflash stock Android. I tried using Nexus Root Toolkit to do that several times, and it never works (I get to a part in the process where it says to set up the phone and enable Developer Options, but I still can't set up the phone). I then decided I would try to do it myself since that tool wasn't fixing the problem. I am able to get ADB connected using the "Apply update from ADB" option within Android Recovery, but whenever I try to sideload one of the Shamu factory images, I get a C++ (I think) error:
Code:
loading: 'C:\Users\dpowell\Downloads\shamu-mob30o.zip'...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I just updated all the ADB-related stuff from within Android Studio, so it all should be up-to-date.
So, I don't know what to try next. I've used Nexus Root Toolkit to root my Nexus 7 successfully, but I've never tried to modify my Nexus 6 before it stopped working. Regardless of what images I try to put onto the Nexus 6, it always shows MOB30O as the current image in the bootload menu.
Any thoughts or suggestions? I really would like to get this device working again, and Motorola would charge me $170 to replace it because it's not under warranty anymore.
Thank you for your help.

dpowell11 said:
Hello.
My Nexus 6 is out of warranty, so I'm doing my best to get it working myself because I can't get it replaced for free.
So, several months ago, my Nexus 6 (running Android 6.0.1 MOB30O) restarted on its own and showed a "Device is corrupt" message before booting (information at g.co/ABH; red error). I was concerned about the security of my device, so I performed a factory reset. Upon trying to set the phone up again, I found that after connecting to Wi-Fi, the phone would loop indefinitely while periodically saying that Google Play Services has crashed. I once tried leaving it overnight while it was "Checking connection" or whatever, and it still did not move to the next phase of setup. I have tried this on several different networks, and when I intentionally use a wrong password, the phone doesn't connect. So, I have no reason to believe the Wi-Fi connection is the problem. I have tried performing a factory reset from Android Recovery dozens of times, and it still doesn't work. So, I'm effectively limited to the boot menu to interact with my phone (so, I can't access Developer Options because I can't set up my phone). Also, most of the times I boot up my phone, I still get that red error during boot.
So, I've been trying to reflash stock Android. I tried using Nexus Root Toolkit to do that several times, and it never works (I get to a part in the process where it says to set up the phone and enable Developer Options, but I still can't set up the phone). I then decided I would try to do it myself since that tool wasn't fixing the problem. I am able to get ADB connected using the "Apply update from ADB" option within Android Recovery, but whenever I try to sideload one of the Shamu factory images, I get a C++ (I think) error:
I just updated all the ADB-related stuff from within Android Studio, so it all should be up-to-date.
So, I don't know what to try next. I've used Nexus Root Toolkit to root my Nexus 7 successfully, but I've never tried to modify my Nexus 6 before it stopped working. Regardless of what images I try to put onto the Nexus 6, it always shows MOB30O as the current image in the bootload menu.
Any thoughts or suggestions? I really would like to get this device working again, and Motorola would charge me $170 to replace it because it's not under warranty anymore.
Thank you for your help.
Click to expand...
Click to collapse
Hello,
The error you get from adb is coming from a problem with latest ADB Rev.25.0.4
Check this: https://issuetracker.google.com/issues/37139736
In Android studio are you able to revert to a previous version, no?
Rev.25.0.3 should work...
I assume your bootloader is locked?!
Good luck...

5.1 said:
Hello,
The error you get from adb is coming from a problem with latest ADB Rev.25.0.4
Check this: https://issuetracker.google.com/issues/37139736
In Android studio are you able to revert to a previous version, no?
Rev.25.0.3 should work...
I assume your bootloader is locked?!
Good luck...
Click to expand...
Click to collapse
Yes, my bootloader is locked.
Thank you, that fixed the ADB problem. I just saw that they actually have a Rev.25.0.5 now, so I am using that.
I tried sideloading first one of the Android 7 images, and that didn't work. So, I tried MOB30O again, and that also didn't work. Here's the error I'm getting:
Code:
E:footer is wrong
E:signature verification failed
Installation aborted.
The Shamu files I was trying to flash are the ones found at https://developers.google.com/android/images#shamu. Is this not what I'm supported to be using?
I don't know how relevant this is, but again, I'm using the "Apply update from ADB" option in Android Recovery, and all I did from my command line is "adb sideload [file]".
Thank you.

dpowell11 said:
Yes, my bootloader is locked.
Thank you, that fixed the ADB problem. I just saw that they actually have a Rev.25.0.5 now, so I am using that.
I tried sideloading first one of the Android 7 images, and that didn't work. So, I tried MOB30O again, and that also didn't work. Here's the error I'm getting:
The Shamu files I was trying to flash are the ones found at https://developers.google.com/android/images#shamu. Is this not what I'm supported to be using?
I don't know how relevant this is, but again, I'm using the "Apply update from ADB" option in Android Recovery, and all I did from my command line is "adb sideload [file]".
Thank you.
Click to expand...
Click to collapse
Hey,
WTF
You can't sideload a factory image
Download a proper OTA here: https://developers.google.com/android/ota#shamu
And try again.
Good luck...

5.1 said:
Hey,
WTF
You can't sideload a factory image
Download a proper OTA here: https://developers.google.com/android/ota#shamu
And try again.
Good luck...
Click to expand...
Click to collapse
Yeah, I understand about 40% of what I'm doing. Thanks for helping.
So, I sideloaded N6F26Y, which is 7.1.1. Here is the debug info I got:
Code:
Installing update...
Target: google/shamu/shamu:7.1.1/N6F26Y/3821691:user/release-keys
Patching system image unconditionally...
E:unknown command [log]
E:unknown command [log]
Writing bootloader...
Writing radio...
script succeeded: result was [1.000000]
Install from ADB complete.
So, it looks to me like that worked, but at the top of my screen, it still says 6.0.1/MOB30O. Also, it always makes me slightly nervous to see error messages. Do I need to reboot to bootloader in order for changes to take effect? Does it look like anything went wrong?
I know that manually messing with the operating system is potentially risky, so I didn't want to continue from here without knowing if there's anything else I needed to do.
Thank you so much for your help.

dpowell11 said:
Yeah, I understand about 40% of what I'm doing. Thanks for helping.
So, I sideloaded N6F26Y, which is 7.1.1. Here is the debug info I got:
So, it looks to me like that worked, but at the top of my screen, it still says 6.0.1/MOB30O. Also, it always makes me slightly nervous to see error messages. Do I need to reboot to bootloader in order for changes to take effect? Does it look like anything went wrong?
I know that manually messing with the operating system is potentially risky, so I didn't want to continue from here without knowing if there's anything else I needed to do.
Thank you so much for your help.
Click to expand...
Click to collapse
Hey,
You know everyone has to start somewhere. 40% is not that bad. :good:
Factory reset once again, just in case. And reboot.
Should be good now (hopefully). Let me know...
Cheers...

5.1 said:
Hey,
You know everyone has to start somewhere. 40% is not that bad. :good:
Factory reset once again, just in case. And reboot.
Should be good now (hopefully). Let me know...
Cheers...
Click to expand...
Click to collapse
Dude. It works.
Man, this phone had been out of commission for months. I am so happy to have it working again.
Thank you very much for your help. I really appreciate it a bunch.

dpowell11 said:
Dude. It works.
Man, this phone had been out of commission for months. I am so happy to have it working again.
Thank you very much for your help. I really appreciate it a bunch.
Click to expand...
Click to collapse
Hey,
Great! I'm glad for you...
Keep reading on this site. There's plenty of usefully threads, infos, etc...
Enjoy your phone...
Cheers...

Nexus 6 locked T-Mobile demo

I recently had to replace the motherboard on my Nexus 6. I could only find refurbished ones, and bought one on AliExpress, with item description clearly specifying as unlock. I installed it, and it appears it is actually locked status 2. Looks like demo version used in T-Mobile retail network. Some settings inaccessible u such as developer mode or Apps. Trying to get refund but both AliExpress and the vendor are in denial mode.
I have 7.0, NBD92G installed. Very hard to unlock as I cannot access developer mode to allow usb debug. Pressing build nr several times won't help. I get message "you're already a developer" but actually usb debug does not work.
Anybody can help?

Go download factory image from Google and flash it manually by using the command prompt.

@ShernDog: He can't as his bootloader is locked. He can however download an OTA and sideload it.

Strephon Alkhalikoi said:
@ShernDog: He can't as his bootloader is locked. He can however download an OTA and sideload it.
Click to expand...
Click to collapse
Thanks. You are right, bootloader is locked too. Would there be any instructions somewhere on your proposed solution (sorry I am rather inexperienced user).

FYBRU said:
Thanks. You are right, bootloader is locked too. Would there be any instructions somewhere on your proposed solution (sorry I am rather inexperienced user).
Click to expand...
Click to collapse
I think I figured out how to do this but the other question is whether I won't be stuck afterwards being requested to enter the only registered user's login which I do not have (I cannot register a second user, as this setting screen is locked too). Do I need to sideload the OTA corresponding to current version / build or can I sideload an older one?

Download the oldest OTA available, as long as it is a full system OTA (easily detectable by size). You're going to have to bypass Factory Reset Protection to be able to resolve this, and the older the OTA, the better.
If this doesn't work, you're going to have to fight with the place you got the motherboard from, and file a chargeback with your credit card company if need be.

Ultimately I can go for the refund, but there is no place where I can find 64 GB MBs outside China, which means I'll have to wait again for something like 3 weeks with poor backup device, and with no certainty I don't receive again a locked MB.
I tried with 6.0 OTAs (page with instructions I followed: https://developers.google.com/android/ota#shamu) and even with just older versions of 7.0, I got every time abortion after about 45% installation, with the msg that I cannot update with older versions.
I am a bit confused now, I just tried to install same build as what I had installed (https://dl.google.com/dl/android/aosp/shamu-ota-nbd92g-2b65257b.zip), it worked but it looks like absolutely nothing has changed on my phone. I thought it would have erased pretty much everything. Am I missing something?

OTA updates don't wipe system. That's why nothing changed.
Ultimately, I think you're going to have to go for the refund and take the risk that the next motherboard you get is going to be locked. Unless the version of Android you're on can have its FRP bypassed - and I don't think it can - you're stuck.

Thanks, bad news. Would it be worth trying wipe data / factory reset accessible from the recovery mode + power/volume up menu ?

You can try it, but it won't help. Doing a factory reset will cause Factory Reset Protection to kick in, meaning you'd need to know the original owner's account information.

Surprisingly it worked. I could log in with the google account I used before the reset. Everything works, but indeed I was expecting some more difficulties

@FYBRU: This is one of those times where I'm pleased to be wrong. LOL.
Glad you got it resolved.