I thought I'd post here and make it easier for all LG QUANTUM users.
http://www.wpcentral.com/get-nodo-now-debranding-your-lg-phone
Just tried, worked smoothly.
When you get to the following step:
Input SUB_PATH: \System\Platform\DeviceTargetingInfo|
Input without the first "\"
Enjoy!
how's about the No-Do?
I heard it's out yesterday
just updated to 7008 after that it says that is the latest update
guess have to wait ...
Confirmed, works. Thank you very much!
-Gus
Twitter: @gguuss
In my country, there are someone selling a quantum with nodo update, he said that it's leaked from technician. So we can keep our hope
gacon1000 said:
In my country, there are someone selling a quantum with nodo update, he said that it's leaked from technician. So we can keep our hope
Click to expand...
Click to collapse
Interesting. I'll research this.
Thanks.
I did the registry change last night and got 7008.
Same thing today... still 7008.
I was ATT-US before.
The registry key value doesn't change post-7008 update FYI.
7008 does fix the Markeplace hanging bug that makes you reboot. So there's some value in doing the update.
So, I guess we wait for NoDo. Since the table of carriers released by Microsoft says that AT&T is "Testing" for both updates for all their devices, perhaps - and this is a theory - perhaps it means that Microsoft is rolling the update to IMEI number groupings or something.
If anything changes, post about it!
Got it working, thanks!
no need to wait
follow the http://forum.xda-developers.com/showthread.php?t=1012189 thread to get the NoDo update, it works great, but when u change over and debrand, change it from space to 000-88, then follow the instructions in the thread i posted. works like a charm. my magic number was 45 seconds and an onscreen timer is a big help.
I'm on LG Quantum - ATT, US, and now running 7.0.7390.0
jlott069 said:
follow the http://forum.xda-developers.com/showthread.php?t=1012189 thread to get the NoDo update, it works great, but when u change over and debrand, change it from space to 000-88, then follow the instructions in the thread i posted. works like a charm. my magic number was 45 seconds and an onscreen timer is a big help.
I'm on LG Quantum - ATT, US, and now running 7.0.7390.0
Click to expand...
Click to collapse
thank you very much,
finally I can taste the joy of NoDo on my Quantum
Has anyone updated their Quantum to NoDo, and then rolled back using the ROM in the development forum? I'm waiting to update until ATT pushes just in case there is ATT/LG fixes included, but if I can rollback to a clean ATT ROM of 7004, I'll try the Nodo update now.
Thanks, Carini
I can't seem to get it to work for my Quantum. Edited the registry to 000-88, disconnected data, checked for update/turned comp internet off... nothin'. Zune either hangs if I disconnect too early, or it says my phone is already updated. I barely have enough time to disconnect my comp's WLAN before it finishes checking
So I never saw a response to my post about rolling back to 7004, but I decided to update to Nodo anyways
All I did was change my phone to 000-80 to get the update(I think). I first tried it at work, turned off the data/wifi on the phone, looked for update in Zune, disabled my NIC after 3 seconds. It gave an error about not contacting the server. I then tried to look for an update again this time not disabling my NIC, and it gave the same error. Tired it a couple more times just in case.
I assumed the update server was blocked by the proxy at work. When I got home, I plugged my phone in Zune, it immediately came back and said 7008 was available, and then after that installed Nodo was available.
I'm not sure if what I did at work caused me to get the update a few hours later, but when I was at home, I didn't have to do any tricks at all. Still wondering about using the ROM to rollback to 7004, if anyone tries it, let me know how it goes.
Got NoDo today with 'unbranded' Quantum
Hi... just wanted to let people know that I received the NoDo update today via Zune, using the 'unbrand' registry hack described here.
Took about 15 mins, went very smoothly.
So the Chevron team released their tool to allow phones that have been forcefully updated to start receiving updates the regular way again. Is there any chance this would put the HD2 into a state that would allow us to update to NoDo?
http://blog.walshie.me/walshed-phone-support-tool-official-fix-to-get-you-back-on-track
Hamburg said:
So the Chevron team released their tool to allow phones that have been forcefully updated to start receiving updates the regular way again. Is there any chance this would put the HD2 into a state that would allow us to update to NoDo?
http://blog.walshie.me/walshed-phone-support-tool-official-fix-to-get-you-back-on-track
Click to expand...
Click to collapse
ive not tried it but i seriously doubt it, the updating still needs to be done the usual way, and that way restarts the device to updating mode where the device is then identified as a LEO, at which point updating fails.
whats needed is us to stop it being identified as a LEO in the update mode and i believe we'll then be able to do normal updates.
Ok, If you are thinking about flashing one of Ansars ROMs then consider this first.
You may never be able to update your phone via Zune again..
Many users are experiencing Error 80180048 when attempting to update via zune from version 7008.
One thing they seem to have in common is that they have flashed one of Ansars ROM's
Here are some examples...
http://forum.xda-developers.com/archive/index.php/t-1034962.html
http://answers.microsoft.com/en-us/...80180048/ceb86673-e65a-e011-8dfc-68b599b31bf5
http://simonwilkins.wordpress.com/2011/04/02/march-update-nodo-for-wp7-arrives/
http://www.pocketpc.ch/windows-phone-7-allgemein/128982-fehlercode-80180048-update-7-0-7392-0-a.html
Plus a number of others on this site...
I have asked for assistance from ansar, and he provided another ROM, which caused even more problems and caused my device to not be detected by Zune or windows.
I know ansar works hard on these ROM's, but I think its important they you all know the risk and don't get stuck in the situation I am in, where I will now have to purchase a new handset.
Ansar: If you can at least acknowledge this issue and confirm that you are working on a fix that would be great, otherwise I believe this Thread is important as a warning to others.
Thanks
WP
Agreed. Verizon Trophy users flashing 0.82.605.02_Radio_1.25.00 are left with unusable devices until an official ROM is able to be flashed.
Be warned.
I flashed my trophy a few times ..
1. RUU_Spark_HTC_Europe_1.10.401.04_Radio_5.52.09.16_22.33a.50.10U_by_ansar
2.to NoDo via zune
3. Zune (nodo) to mango
4. forgot to unlock it before
5. We are back at RUU_Spark_HTC_Europe_1.10.401.04_Radio_5.52.09.16_22.33a.50.10U_by_ansar
6. NoDo via Zune
7. Zune (nodo) to mango (unlocked this time)
So i guess everything fine here
Ok, So the solution for me here was to Unbrand my device with a "Y" Cable and flash
RUU_Spark_HTC_Europe_1.20.401.00_Spark_5.54.09_RELEASE.
Once I was on this rom, I was able to update no problem through Zune to 7392.
Basically the ROMS by Ansar seem to be problematic and he isn't willing to provide any support. So, I suggest avoiding flashing them, unless you want problems in the future.
I have a HD2 running wp7 7392. Really want to get mango. Have tried to force (phone airplan mode, laptop wifi off, plug and unplug ethernet cable). I have tried for 3 days and I have done this maybe 200 times. If I pull too quickly,
within a second, I get connection error. If too slow, 2 or 3 sec, I get "your phone is up to date" And I have tried every ms in between but never was able to get the upgrade! Does anyone else have this problem? Do I have to push deviceprovisioning.cab? I did not have to push this cab and was able to get 7008, then 7392 all through zune. But this time I just cant force. Also looking at the microsoft site, t-mobile phone are already in delivery phase! Drive me nuts! Any advise?
Let's see if I got it right you're on NODO with back to the future v2 and waiting for the official mango update?
Then the solution is quite simple: READ the rom thread! It's in the second or third post...
Anyway, here's the solution:
If you can wait for the official update (it's not out yet!), wait
If not (very likely!!), you've got to send deviceprovisioning.cab to get developer updates and then: just continue updating with zune and it should work just fine...
(or you can use the update cabs provide by xbmod...)
But however you're going to do this, read the rom thread. It's better for you, for your phone (much safer!!!)
upate: I can't wait any longer, so I pushed the deviceprovisioning.cab onto the phone. Right away, zune tells me that there is an update available (7403).
I am in the middle of the 7403. Looks hopeful. Just want to update so other who are stuck at the same place could benefit.
HD2 stuck at 7403, fix!
Hi All! Since august 15th 2012 my HD2 has been stuck at WP7 7403. Tried the force Mango trick very often, but didn't succeed. Very frustrating.
I found my solution in this topic, thank you chabun!
With WP7 Cab Sender I send Deviceprovisioning.cab wich I found here: http://forum.xda-developers.com/showpost.php?p=20696473&postcount=4498
After sending Deviceprovisioning.cab Zune showed an update (7720) wich I am installing right now. XDA did it again for me, tnx folks!
So, I was eagered to update my phone with the new SFR-FR update, got it all set.
It started all with the 8018001E error I got when trying to update to this update, so I thought I would just leave it, and I changed my carrier to 000-88.
Then I saw there was another method to update, with the WP7 Cab Sender and the update as a .cab file. Tried this one out when I was still being debranded (000-88), this time the installation failed with error 80180011.
Then (oh dear), I downloaded the Samsung Update Tool from the Omnia 7 support page, and installed a update (or something). Now I tried the official way again (changing carrier to SFR-FR, then Zune update), this time I got the 80180097 error! Yes its raining errors today.
After the Samsung Update Tool thingy, my phone couldn't connect to any network, or sometimes it's connecting to my KPN network for a few moments.
I am tired of this all, all I wanted was to install a few OEM updates, now I end up with this. Can anyone help me out? Really appreciated!