Motorola just released a software download for people using 4.1.51 and 4.1.52. According to them, this will bring any phone on one of those versions back to the official Motorola Software.
Download HERE
Motorola's Announcement HERE
I currently don't have access to my phone, but I would be interested in knowing what this does with bricked phones.
thehacker010 said:
Motorola just released a software download for people using 4.1.51 and 4.1.52. According to them, this will bring any phone on one of those versions back to the official Motorola Software.
Download HERE
Motorola's Announcement HERE
I currently don't have access to my phone, but I would be interested in knowing what this does with bricked phones.
Click to expand...
Click to collapse
Well........that's slightly promising. Seems like a small reach of the olive branch. Still not a bootloader solution though.
Work on Bell Atrix ?
Thanks.
I can't use it, but that might be because it can't get out through the proxy (I'm at work). It just says "Cannot determine something or other blah blah network settings." Then when I exit the program it reboots my phone. Then my phone stays in a reboot loop until I unplug the USB.
Crappy software, there.
Edit: remove all contents
I don't know how strict people are about "searching" things before posting on the forums, but I rather get yelled at by some nerd on the internet, than to have my $350 device screwed over because I followed the wrong tutorial. Anyways here are my questions:
1) I bought this device from someone brand new, and it came out of the box configured to work with Windmobile, but I was able to get my FIDO SIM card to work by simply inputting it into the device. So does this mean that my device is already unlocked?
2) I still have the old 2.2 version on my phone, and I want the new version (2.3), but since I cannot update the OS from the device itself, I don't know what method I should follow from my computer, also I am afraid that I might lose my unlock (if it is) with the update.
Please link me to the proper tutorial, or give me some insight on my problem, Thank you.
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.
I have looked and looked to no avail, is it no longer possible to flash Lumia firmware through the Nokia Care Suite anymore? I can not seem to find the RM-820 in the open product. Everything tutorial I have seen says to find it in there I did see a comment in a thread where someone said that they didn't think Nokia is allowing that anymore. Is this true? I have the spinning cogs so I wanted to flash the firmware...
So I'm stuck and all help on the internet seems outdated. Is there something I'm missing?
just read forum... there is few ways to download firmware....
http://forum.xda-developers.com/showthread.php?t=2515453
there is a new tool released by nokia that is supposed to help recover / flash phones if they become stuck during boot or flash.
From memory it is called nokia software recovery tool. maybe you could try that if you can find it. I read about it on a site lastnight but can not remember where i saw the info about.
Google may help or it may have even been on here..
Chris
CBDSonline said:
there is a new tool released by nokia that is supposed to help recover / flash phones if they become stuck during boot or flash.
From memory it is called nokia software recovery tool. maybe you could try that if you can find it. I read about it on a site lastnight but can not remember where i saw the info about.
Google may help or it may have even been on here..
Chris
Click to expand...
Click to collapse
I downloaded and installed Nokia Care Suite on a Windows 8.1 PC just last night (EST in New York). I then used to install the Amber update onto a RM-878 that I just bought from Amazon - worked flawlessly.
Instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2515453
I have installed pc suite for Lumia 520 ...but i am not getting usb connect option...
can anyone have idea?
docfreed said:
I downloaded and installed Nokia Care Suite on a Windows 8.1 PC just last night (EST in New York). I then used to install the Amber update onto a RM-878 that I just bought from Amazon - worked flawlessly.
Instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2515453
Click to expand...
Click to collapse
That is exactly what I am talking about. I have read the thread, followed the thread up until it say under product type. Under the sim tray it says RM-820 and there isn't a RM-820 in there, thus this question got asked. I'm not asking for someone to hold my hand through this, I just wanted to know if the RM-820 is or isn't supported with Nokia Care Suite. I know that the software works, flawlessly even, not saying it didn't. I have the firmware downloaded don't need the firmware. Just wanted to know if the Lumia was still supported by Nokia Care Suite, if I was missing something obvious.
chasingeuphoria said:
That is exactly what I am talking about. I have read the thread, followed the thread up until it say under product type. Under the sim tray it says RM-820 and there isn't a RM-820 in there, thus this question got asked. I'm not asking for someone to hold my hand through this, I just wanted to know if the RM-820 is or isn't supported with Nokia Care Suite. I know that the software works, flawlessly even, not saying it didn't. I have the firmware downloaded don't need the firmware. Just wanted to know if the Lumia was still supported by Nokia Care Suite, if I was missing something obvious.
Click to expand...
Click to collapse
What Phone do you have - reason I ask is that the original thread is a little confusing - there is of course a Lumia 820 but its actual Product Type is RM-824 and if you use the 824 Product Type from this thread:Nokia Lumia 820 Product Code (Product Type RM-824)
at http://forum.xda-developers.com/showpost.php?p=49364933&postcount=10 it shows dozens of codes to use for the Nokia Care Suite depending on country and carrier.
docfreed said:
What Phone do you have - reason I ask is that the original thread is a little confusing - there is of course a Lumia 820 but its actual Product Type is RM-824 and if you use the 824 Product Type from this thread:Nokia Lumia 820 Product Code (Product Type RM-824)
at http://forum.xda-developers.com/showpost.php?p=49364933&postcount=10 it shows dozens of codes to use for the Nokia Care Suite depending on country and carrier.
Click to expand...
Click to collapse
It is a Lumia 920 product code RM-820 I saw the product code on that little pull out thing under the Sim tray
http://forum.gsmhosting.com/vbb/f60...ting-care-suite-download-1660094/#post9434336
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