"Debranding" Hack to get pre-NoDo update - Quantum General

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.

Related

Update available!!!!

My phone currently updating to version 7008 - needs update to Zune too which is downloading first.
Was on 7004.
Will let you know what happens!
I can't see any changes...
Also no saving of the changes you make in Camera or so on...
Is this the update before March Update!?
Yeah, this is just an update to pave the way for future updates. You'll find nothing new here.
skycamefalling said:
Yeah, this is just an update to pave the way for future updates. You'll find nothing new here.
Click to expand...
Click to collapse
Is the Camera any better...? could be into the realms of imagination here but took a photo and it seemed clearer than previous efforts on standard settings. Phone also 'seems' a little zippier.
Not totally sure so guess things aren't that different.
Backup worked nicely though.
Mine is in the process of updating. The backup process takes a while.
I wonder if we can use someone elses backup to restore a phone? I only ask because I flashed my UK T-Mobile device with the unbranded Samsung one because it was said that it fixed Bluetooth problems. However, it has had no effect, and now I can't take my phone back to T-Mo because it's not running the original firmware. If I can get it back to UK spec, then I can take it back to a shop and swap it for a (hopefully) working one...
Done. It is only a preparatory update for the actual update containing copy and paste, improvements to Windows Phone Marketplace et.al. Ergo, it doesn't contain any new functionality and won't remove or hinder any installed jailbreak functionality.
Yup, more playing, definitely no changes I can find...camera taking a better photo just happened to be a picture in better light.
This update has bricked my Omnia 7.
When I connected my Omnia 7 to Zune today, I was notified of an update. Zune updated itself and quit. I restarted Zune and it informed me there was an update for my phone. I clicked update now and it got to step 6/10 rebooting phone. The phone evenually rebooted and Zune reported the following:
RESTORATION ERROR
An error prevented the restoration of your phone to its previous version. Your phone cant be used in its present condition and there are no restore points for it on this computer. Thephone might restart and return to normal if you disconnect it. For further assistance, contact your mobile operator.
ERROR CODE C101002E
Thanks Microsoft, that's a really helpful message. NOT.
I have manually updated to the latest Zune, rebooted my PC, rebooted my phone, and I get the same thing every time.
THIS IS NOT GOOD ENOUGH MICROSOFT. My Omnia 7 is now a brick.
Loconinja said:
This update has bricked my Omnia 7.
When I connected my Omnia 7 to Zune today, I was notified of an update. Zune updated itself and quit. I restarted Zune and it informed me there was an update for my phone. I clicked update now and it got to step 6/10 rebooting phone. The phone evenually rebooted and Zune reported the following:
RESTORATION ERROR
An error prevented the restoration of your phone to its previous version. Your phone cant be used in its present condition and there are no restore points for it on this computer. Thephone might restart and return to normal if you disconnect it. For further assistance, contact your mobile operator.
ERROR CODE C101002E
Sorry for that. I was afraid of this happening to me when the update stalled at the 7th step
Thanks Microsoft, that's a really helpful message. NOT.
I have manually updated to the latest Zune, rebooted my PC, rebooted my phone, and I get the same thing every time.
THIS IS NOT GOOD ENOUGH MICROSOFT. My Omnia 7 is now a brick.
Click to expand...
Click to collapse
Sorry about that. I was afraid of this happening to me, after the update stalled for an hour at the 7th step, so I disconnected. Luckily nothing happened to my device. But apparently several Omnia 7 are experiencing this.
Sort it out, MS.
First things first. I was updated Zune to the recent version, because I was curious it will resolve a problem with login user on one of my computers. One (Windows Vista) works fine, but another one, Windows 7 (both 32-bits versions) works fine with Zune + Market.
Silent Shark said:
I wonder if we can use someone elses backup to restore a phone? I only ask because I flashed my UK T-Mobile device with the unbranded Samsung one because it was said that it fixed Bluetooth problems. However, it has had no effect, and now I can't take my phone back to T-Mo because it's not running the original firmware. If I can get it back to UK spec, then I can take it back to a shop and swap it for a (hopefully) working one...
Click to expand...
Click to collapse
I've done the same. I have (branded) T-Mobile UK phone and decided update to unbranded one. I choose version I8700XENJK1 (but I tried another one before) - for me, one difference is language Dutch / Belgium if I remember correctly.
I've read this thread and I was wondering if my phone will find update... I had no information about this.
I return home, connect Omnia to computer and update process start immediately. I had no problem with update at all. Phone during update reboots twice (or more) and it looks stable. I haven't noticed any changes or improvements... maybe it's working a little bit faster, but maybe it's a auto-suggestion.
Loconinja said:
This update has bricked my Omnia 7.
When I connected my Omnia 7 to Zune today, I was notified of an update. Zune updated itself and quit. I restarted Zune and it informed me there was an update for my phone. I clicked update now and it got to step 6/10 rebooting phone. (...)
THIS IS NOT GOOD ENOUGH MICROSOFT. My Omnia 7 is now a brick.
Click to expand...
Click to collapse
Sorry for that mate. I really had not problem with update.
Loconinja said:
This update has bricked my Omnia 7.
When I connected my Omnia 7 to Zune today, I was notified of an update. Zune updated itself and quit. I restarted Zune and it informed me there was an update for my phone. I clicked update now and it got to step 6/10 rebooting phone. The phone evenually rebooted and Zune reported the following:
RESTORATION ERROR
An error prevented the restoration of your phone to its previous version. Your phone cant be used in its present condition and there are no restore points for it on this computer. Thephone might restart and return to normal if you disconnect it. For further assistance, contact your mobile operator.
ERROR CODE C101002E
Thanks Microsoft, that's a really helpful message. NOT.
I have manually updated to the latest Zune, rebooted my PC, rebooted my phone, and I get the same thing every time.
THIS IS NOT GOOD ENOUGH MICROSOFT. My Omnia 7 is now a brick.
Click to expand...
Click to collapse
have you tried taking back battery and then reboot again?
http://twitter.com/#!/WinPhoneSupport
hard-reset Focus, should be similar to omnia 7
http://www.technipages.com/samsung-focus-hard-reset-using-hardware-keys.html
Update error
801012DD Error code - we couldnt create a backup of your phone
Help !!!!!
Have you got samsung tools installed?
I have tried twice to install the update. Both times I got stuck at 7 or of 100 with 100%.
The only thing I have done my phone is to unlock it with chevron.
Altough I did have it in flight mode at the time to prevent relocking.
Do you think that would have affected anything?
Still nothing showing up for me yet. Those who got the mini update does your 3 button combo into download mode now work if you had a phone that didnt let it happen before?
Lordao
lordao said:
Still nothing showing up for me yet. Those who got the mini update does your 3 button combo into download mode now work if you had a phone that didnt let it happen before?
Lordao
Click to expand...
Click to collapse
Three button combo now gives me the rather scary option to Format or Cancel. I thought Cancel would be the way to go....
Successful Updaters: Please post your Firmware revisions
For those who have managed to get the update installed without error, can you please post here your firmware revisions. We may be able to work out which models are affected by the issue.
There are rumours that this update only affects firmware versions JI9 and JJ4 while the JK1 firmware is unaffected.
http://www.zdnet.com/blog/hardware/windows-phone-7-update-bricking-some-samsung-omnia-handsets/11501
gc48067 said:
Three button combo now gives me the rather scary option to Format or Cancel. I thought Cancel would be the way to go....
Click to expand...
Click to collapse
Are you saying the Download Mode is no longer accessible after updating?
scoob101 said:
For those who have managed to get the update installed without error, can you please post here your firmware revisions. We may be able to work out which models are affected by the issue.
There are rumours that this update only affects firmware versions JI9 and JJ4 while the JK1 firmware is unaffected.
http://www.zdnet.com/blog/hardware/windows-phone-7-update-bricking-some-samsung-omnia-handsets/11501
Click to expand...
Click to collapse
How can I check which firmware revision I am using?

[Q] Samsung Update (post Nodo)

After updating my Omnia 7 to Nodo I got another update notification about a "Samsung Update".
When I try to install it it hangs at step 6 of 10: rebooting your phone (the phone shows the omnia logo but doesn't boot).
Was anybody able to install this update? What does it do?
You say you updated to NoDo...how? Did you receive a notification or use one of the tricks to get the update? Not had anything myself. Also how long after the NoDo update did you get the other update, was it via Zune or a phone notification.
Sounds interesting given the odd display I've now got, wondering if we have some updated drivers on the way.
gc48067 said:
You say you updated to NoDo...how? Did you receive a notification or use one of the tricks to get the update? Not had anything myself. Also how long after the NoDo update did you get the other update, was it via Zune or a phone notification.
Sounds interesting given the odd display I've now got, wondering if we have some updated drivers on the way.
Click to expand...
Click to collapse
I forced the update (via Hungary) but got the new notification as soon as I connected the phone to Zune (it also shows up on the phone).
There is a 'more information' link on the first page but sadly it does not give more information.
Getting the same update after NoDo. Doesn't update though, stuck at rebooting just like you. Weird..
Didn't get my update via Hungary BTW, just the regular way (A1 branded).
Hmmm this is worrying. I assume there were no problems after this update failed?
Freypal said:
Hmmm this is worrying. I assume there were no problems after this update failed?
Click to expand...
Click to collapse
No, I don't think anything happened yet. The PC is waiting for the phone to reboot, and the phone is stuck on boot..
How long did you leave it?
Not sure, 30-45 mins maybe the first time. The second time I tried just a couple of minutes. It said the update would take 32 mins, but since it just said rebooting and not updating I reckoned the process hadn't even started yet.
Cheekbone said:
Not sure, 30-45 mins maybe the first time. The second time I tried just a couple of minutes. It said the update would take 32 mins, but since it just said rebooting and not updating I reckoned the process hadn't even started yet.
Click to expand...
Click to collapse
You just unplugged it then and it carried on workig OK?
That sounds about right, when i did pre-nodo the reboot took about a minute or so of displaying the Omnia logo then went to the pc plug screen whilst it updated.
I did read about device specific updates, seems odd though as some people are saying that they updated to NoDo and it works fine and had no future updates.
Freypal said:
You just unplugged it then and it carried on workig OK?
That sounds about right, when i did pre-nodo the reboot took about a minute or so of displaying the Omnia logo then went to the pc plug screen whilst it updated.
I did read about device specific updates, seems odd though as some people are saying that they updated to NoDo and it works fine and had no future updates.
Click to expand...
Click to collapse
Unplugged it and had to take the battery out to reboot. Notice how it says 'Samsung update for Windows Phone' though. I'll try one more time. My phone bugged me a couple of times about the update as well ('An Update is available').
I wonder if this is a firmware update?
Edit - Looks like it is http://forum.xda-developers.com/showpost.php?p=12516155&postcount=56
Yeah, guessed so. Still not working for me though. Waited for about an hour for it to reboot.
My mistake - Edited
Can i know which firmware version do you have on your Omnia 7? I got a JK1 and i haven't recieved this kind of update
PS
To view firmware version go in phone then open the numeric pad and call ##634# to enter diagnosis then type these combination: *#1234#
For me:
PDA: ends with JID
Phone: ends with JIC
CSC: ends with JID
Curious to see what Cheekbone has as its trying to update it
All end with JJ6
Well I guess the majority is already on JK1, so the samsung update only pops up for some.
It would be great if there would be further samsung firmware updates before major MSFT ones.
It does seem that JK1 is the norm. I guess it means I will be offered the further update...
Worrying!
Hey mine says
JID
JIC
JID
is this old? Is there any point to updating the firmware? Zune gives me no update. but i have been wondering about my FW Version for some time.
Any help is appreciated.
ProficienTWP7 said:
Hey mine says
JID
JIC
JID
is this old? Is there any point to updating the firmware? Zune gives me no update. but i have been wondering about my FW Version for some time.
Any help is appreciated.
Click to expand...
Click to collapse
Have you updated to Pre-NoDo (.7008) or NoDo (.7390) ?

[Q] Can't update from pre-nodo to nodo

I have 3 Samsung Focus in my family. I got two to update from stock to nodo. On the third, I've updated to pre-nodo (7008) but I can't get the nodo update to take after multiple tries.
I thought that I had it the first time, but one of my kids disconnected their phone without checking to see if it was finished updating. So I do not know where it was in the update process. The phone works and it says 7008 version (pre-nodo).
When we connect to Zune and try updating, it says that the phone is up to date.
Any help would be greatly appreciated. I tried the requisite searching but can't come up with a similar issue.
check this out:
http://answers.microsoft.com/en-us/...e/734b0f47-516b-e011-8dfc-68b599b31bf5?page=2
http://wmpoweruser.com/samsung-focus-rev-1-4-last-in-line-for-nodo-update
you probably have REV 1.4 on the back of your phone, behind battery...
I'll check on my daughter's phone. We bought all three of them at the same time. Odd that one might be different. I'll let folks know.
It was surprising that it took the pre-nodo and then when we went back in to update again, it found the 2nd update. It just didn't take and now it thinks that it is fully updated.
I'll post back the version of her phone.

I cannot force mango no matter how hard I try!

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!

I need your help..i still cant get mango!! EDIT SUCCESS!!

I went from v2 - 7004-7392cab -devicepro.cab- zune to 7403 - 80004005 error trying to install isv 7720.
Looked all over the internet for this code and somebody found a solution on this website(half way down the page)...it relates to a samsung device but if somebody can explain how do i apply this to hd2??
http://answers.microsoft.com/en-us/...o/60e728c6-2cfe-47fc-a996-344a9d1c2c0d?page=2
Ps i try cab 7403 to 7661 but fails with error code straight away..WHY?? Do i need devicepro.cab again?? What would be your advice /route if i wanted to try the cab install to mango? Detailed guide would be awesome
Im running out of patience now i think
Why dont you try to flash your device over Zune?
Just install V2 ROM and then follow the instructions and update via Zune.
Rosetti you couldnt have said better. I Updated All Through Zune. DeviceProvisioning.cab is needed for going from NODO to MANGO.
Yeah dude do it over Zune the last stages are way easier over zune
i can't believe i tried everything else but not this method...thanks all ..i will report back later 2nite..
I dont believe it!
all week i have been messing around with cabs files as people were constantly reporting errors with zune thats why i decided to avoid it but il be damned!
process took around 2hours from start to finish..still got cleanup to go but i rather get some sleep..
i just went from 7403 rom .turned phone off
format sd card
enter magldr - clear and enable stuff
usb mode
flash v2 rom
set up date and time
zune found february update
zune found 7392
Send devicepro.cab via cabsender
zune found 7720 took fooking ages
zune finds cleanup - gta wait till 2mro thou..
not one trick applied ie hard resets/change time zone/reserved space/virus off
it was as simple as that..good nite!
i followed yuki v2, then force update with zune i got 7xxx (forgot) then again force update i got 7392 but then i cant force it anymore to get 7403 (before final force to 7220). i tried 1 sec then pull the internet cable. no success. tried 3,4,5 secs, also no luck. comments?
Once I succeeded in installing Mango on HD2, but then I realised that it's not unlocked. So I flashed my phone again... and now I'm stuck on 7008 and Zune's not giving me any update.
Can you please help me? My hair is all grey
Matt.Murdock said:
Once I succeeded in installing Mango on HD2, but then I realised that it's not unlocked. So I flashed my phone again... and now I'm stuck on 7008 and Zune's not giving me any update.
Can you please help me? My hair is all grey
Click to expand...
Click to collapse
Have you tried forcing it??
I did and it worked now... (not before, didn't get the right timing)
Matt.Murdock said:
Once I succeeded in installing Mango on HD2, but then I realised that it's not unlocked.
Click to expand...
Click to collapse
How did you realise this, Venerable sir? Did it say it in toms xap(number of reasons)? Did you try to send dev-unlock-remove.cab then dev-unlock.cab?
You might have saved yourself some trouble and hair dye
Matt.Murdock said:
I did and it worked now... (not before, didn't get the right timing)
Click to expand...
Click to collapse
I have to say, I tried every possible timings (all between 0 and forever). Don't work for me. Worked with the NODO update on second try. Mango - no chance.
*edit: Don't know why. Yesterday cab sending did not work. Gave me an error. Went to bed. Just thought I'd give it a nother shot - worked. Sent the .cab and Zune found the update for my Phone instantly!
Now all I am lacking is the activation key - waiting for the replay by MS.
Thanks to all, that made this possible!
**EDIT²: Now after finding the update, and installing the first step to Mango, I get stuck at the CLEAN UP update. Can't get it solved. Any suggestions?

Categories

Resources