Hi,
I have a ATT 920 and I'm trying to flash to the Euro dev rom so that I can have AWS.
I'm trying to flash the Rogers RM-820 ROM but I keep getting this error message:
0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
Any solutions?
I'm getting the same error. For some reason I can't see to flash it to a non att rom.
oddleif said:
I'm getting the same error. For some reason I can't see to flash it to a non att rom.
Click to expand...
Click to collapse
you have to flash to non-portico Rogers rom like RM820_1232.5962.1314.0000_RETAIL in order to flash your AT&T nokia.
I've made it a month ago.
boril said:
you have to flash to non-portico Rogers rom like RM820_1232.5962.1314.0000_RETAIL in order to flash your AT&T nokia.
I've made it a month ago.
Click to expand...
Click to collapse
I tried the specified ROM, several times. But only got this error "DTL Connection: Could not connect to media. DTL Back-End error code = 0x8400A403. DTL Back-End: Driver initialization failed. DCM status code = 0x84004416, Common USB DCM: The initialization parameters are wrong." I got the same error when trying other Rogers ROM. There should be nothing wrong with the ROM, I downloaded it from NCS. Along with all the other ROM I've tied. And as stated before, I am for some reason only able to flash to another att ROM (black, white, yellow, red, cyan).
oddleif said:
I tried the specified ROM, several times. But only got this error "DTL Connection: Could not connect to media. DTL Back-End error code = 0x8400A403. DTL Back-End: Driver initialization failed. DCM status code = 0x84004416, Common USB DCM: The initialization parameters are wrong." I got the same error when trying other Rogers ROM. There should be nothing wrong with the ROM, I downloaded it from NCS. Along with all the other ROM I've tied. And as stated before, I am for some reason only able to flash to another att ROM (black, white, yellow, red, cyan).
Click to expand...
Click to collapse
sorry I mislead you the pre-portico is RM820_1232.2109.1242.1002
boril said:
sorry I mislead you the pre-portico is RM820_1232.2109.1242.1002
Click to expand...
Click to collapse
Still getting the same error. I've gone through the process several times. I'm not able to flash that ROM to my phone. I have deducted that there is nothing wrong with the files, but most likely the error refers to the firmware I currently have on the phone (RM820_1232.5962.1314.0001). This is based on the fact that when I press start before the phone is conected, I get all green lights. I'm considering a firmware rollback, but so far I'm not seeing it happen anytime soon. Any advice will be considerde.
oddleif said:
Still getting the same error. I've gone through the process several times. I'm not able to flash that ROM to my phone. I have deducted that there is nothing wrong with the files, but most likely the error refers to the firmware I currently have on the phone (RM820_1232.5962.1314.0001). This is based on the fact that when I press start before the phone is conected, I get all green lights. I'm considering a firmware rollback, but so far I'm not seeing it happen anytime soon. Any advice will be considerde.
Click to expand...
Click to collapse
i had similar issues yesterday but i followed this thread "http://forum.xda-developers.com/showpost.php?p=38325527"
hope it helps... im now running successfully the Rogers ROM
TopoX84 said:
i had similar issues yesterday but i followed this thread "http://forum.xda-developers.com/showpost.php?p=38325527"
hope it helps... im now running successfully the Rogers ROM
Click to expand...
Click to collapse
Thanks, but I've tried it before and no luck.
TopoX84 said:
i had similar issues yesterday but i followed this thread "http://forum.xda-developers.com/showpost.php?p=38325527"
hope it helps... im now running successfully the Rogers ROM
Click to expand...
Click to collapse
I follow the same guide and manage to flash to various ROMs
boril said:
I follow the same guide and manage to flash to various ROMs
Click to expand...
Click to collapse
curious thing i just tried to roll back to the AT&T ROMs but seems not to be working... it gives me the
0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
any suggestions as well ?
TopoX84 said:
curious thing i just tried to roll back to the AT&T ROMs but seems not to be working... it gives me the
0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
any suggestions as well ?
Click to expand...
Click to collapse
Check this
http://forum.xda-developers.com/showpost.php?p=42874438&postcount=77
Roll back Att Lumia 920
I'm trying to roll back to the original ROM from my nokia lumia 920 at&t but I can't even with other ROM Product from At&t anyone have a solution?
Related
As you may have seen from my previous post I FUBAR'd my 920 by trying to flash a RM-821 ROM to my RM-820 Lumia 920.
Since there are no RM-820 ROMs on Navifirm yet, I was wondering if it is possible to somehow copy or backup the ROM from a working 920 and flash it to my phone?
I wonder if someone with a Rogers Lumia 920 can test something for me?
http://www.symbiantweet.com/how-to-force-update-nokia-lumia-800-to-latest-firmware-12070
Can you download the tools listed on the above site and see if you can do a backup of your 920 with them?
As I recall one of the options is to backup the current ROM with this. However, I don't know if it will even recognize a 920.
If you are able to do a backup, I would REALLY appreciate it if you could send me it so I could get my 920 working again
tomcahill said:
As you may have seen from my previous post I FUBAR'd my 920 by trying to flash a RM-821 ROM to my RM-820 Lumia 920.
Since there are no RM-820 ROMs on Navifirm yet, I was wondering if it is possible to somehow copy or backup the ROM from a working 920 and flash it to my phone?
Click to expand...
Click to collapse
Hello OP, so are you still able to flash an image to your phone? Did you try the Middle East version or Saudi Arabia version? Those phones are supposed to support ALL radios, and even though Nokia's international site has removed some bands, the nokia sites for those regions still list those bands. Why don't you try to flash with one of those and report back. Thanks
hkalltheway said:
Hello OP, so are you still able to flash an image to your phone? Did you try the Middle East version or Saudi Arabia version? Those phones are supposed to support ALL radios, and even though Nokia's international site has removed some bands, the nokia sites for those regions still list those bands. Why don't you try to flash with one of those and report back. Thanks
Click to expand...
Click to collapse
Man I had my hopes up!
I can still try to flash the phone but every time I get this error message:
0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
Same result when using the ME_Open ROM.
I doubt any RM821 has AWS support. Its the RM820 that's pentaband.
tai4de2 said:
I doubt any RM821 has AWS support. Its the RM820 that's pentaband.
Click to expand...
Click to collapse
As per this site, it is: http://www.nokia.com/ae-en/products/phone/lumia920/specifications/
Edit. Just re read the post.
RM-820 - Is that the US model number?
AndyD777 said:
Edit. Just re read the post.
RM-820 - Is that the US model number?
Click to expand...
Click to collapse
Yup US and Canada.
Im trying to update my rom from 821 to a more recent 821 - but cant work out how to do it. I have download the ROM and files it comes with from Navifirm... got the latest Product Support Tool and it sees my 920. But how do I point it to the ROM file? I tried the data package option and pointed it to where the files are (in a folder) but it doesnt give show any new packages when I choose "Refurbish".
I think it is either not seeing the location of the files or the files need to be in a container like a zip file or something? Can anyone confirm how to do this?
Thanks
paulthomas881 said:
Im trying to update my rom from 821 to a more recent 821 - but cant work out how to do it. I have download the ROM and files it comes with from Navifirm... got the latest Product Support Tool and it sees my 920. But how do I point it to the ROM file? I tried the data package option and pointed it to where the files are (in a folder) but it doesnt give show any new packages when I choose "Refurbish".
I think it is either not seeing the location of the files or the files need to be in a container like a zip file or something? Can anyone confirm how to do this?
Thanks
Click to expand...
Click to collapse
If you download the ROM from navifirm you need to move it to the Nokia product directory. In Windows 7/8 it is C:\ProgramData\Nokia\Packages\Products\rm-821
tomcahill said:
If you download the ROM from navifirm you need to move it to the Nokia product directory. In Windows 7/8 it is C:\ProgramData\Nokia\Packages\Products\rm-821
Click to expand...
Click to collapse
Ok - thanks for that - tried it but its not done anything.... first of all the Product directory and rm-821 directory wasnt there so had to create them. Then copied the files over to there and relaunched the nokia care suite.
I go to refurbish and it says "New software version - Not available"
Is there something i'm missing?
paulthomas881 said:
Ok - thanks for that - tried it but its not done anything.... first of all the Product directory and rm-821 directory wasnt there so had to create them. Then copied the files over to there and relaunched the nokia care suite.
I go to refurbish and it says "New software version - Not available"
Is there something i'm missing?
Click to expand...
Click to collapse
try changing it from refurbish to recovery.
did you move all the files into the rm-821 directory? They all need to be moved. You may want to try downloading the Data Package Manager, it may not be part of your NCS. It's similar to Navifirm but it works with NCS and puts the files in the right location so the other tools can see it.
tomcahill said:
try changing it from refurbish to recovery.
did you move all the files into the rm-821 directory? They all need to be moved. You may want to try downloading the Data Package Manager, it may not be part of your NCS. It's similar to Navifirm but it works with NCS and puts the files in the right location so the other tools can see it.
Click to expand...
Click to collapse
I have installed the Data Package Manager... all good apart from it wont download the files for the phone. I think it is failing on DC_template_development_v4.bin file as Navifirm also fails on this and gives a exception error. Do you think this is why it is not seeing the package in the software updater? I think it might be.... but how do I download that file? Does anyone have one they can send me for rm-821 - I am trying the EE Black rom....
Thanks
its been posted in another thread
http://forum.xda-developers.com/showpost.php?p=33934389&postcount=10
I have a working phone locked to EE, Im trying to flash it to a generic GB version, but just keep getting error messages along the lines of
Invalid response from device, incorrect message id
Will be interested to hear how you get on
rti r
edgedemon said:
its been posted in another thread
http://forum.xda-developers.com/showpost.php?p=33934389&postcount=10
I have a working phone locked to EE, Im trying to flash it to a generic GB version, but just keep getting error messages along the lines of
Invalid response from device, incorrect message id
Will be interested to hear how you get on
Click to expand...
Click to collapse
Well I have good news.... I succesfully relashed my phone! I got the DC template bin file for the yellow UK rom - downloaded that same ROM and flashed it (turned my phone off then started the flash process). My phone is the black one and was on the oldest 821 ROM (unlocked) so was worried about putting a yellow ROM on it... btw - it gave me a msg at the start of the flash saying that it was not the right access IS or something for the phone - I chose ok and bit the bullet.
But it all went through ok with no errors and now I have a newer ROM and my bluetooth in the car is working a lot better. I hope my battery life will be better too... we will see....
If you want a step by step of what I did then let me know.....
which specific firmware download?
- 1232.2110.1244.3 (059R072)
or
- 1232.2110.1244.3011 (059R1W6)
or?
thx
paulthomas881 said:
Well I have good news.... I succesfully relashed my phone! I got the DC template bin file for the yellow UK rom - downloaded that same ROM and flashed it (turned my phone off then started the flash process). My phone is the black one and was on the oldest 821 ROM (unlocked) so was worried about putting a yellow ROM on it... btw - it gave me a msg at the start of the flash saying that it was not the right access IS or something for the phone - I chose ok and bit the bullet.
But it all went through ok with no errors and now I have a newer ROM and my bluetooth in the car is working a lot better. I hope my battery life will be better too... we will see....
If you want a step by step of what I did then let me know.....
Click to expand...
Click to collapse
Awesome. I am very happy for you. But at the same time I hate you just a little bit
kesu2 said:
which specific firmware download?
- 1232.2110.1244.3 (059R072)
or
- 1232.2110.1244.3011 (059R1W6)
or?
thx
Click to expand...
Click to collapse
The one I used is 1232.2110.1244.3003 - the GB yellow rom. I used the latest version of the nokia care suite.
Bluetooth is now working sweetly in my car.... reconnects every time which it wasn't doing before.
---------- Post added at 11:30 AM ---------- Previous post was at 11:20 AM ----------
this is the link where I got the dc template file but I cant post links as Im new to the forum..... put a www on the start of this - dropbox.com/s/owwrhc339ex5wfm/DC_template_development_v4.bin
Thank you for your answer.
In NaviFirm Plus unfortunately I do not see 1232.2110.1244.3003 only 1232.2110.1244.3. That's it?
paulthomas881 said:
Well I have good news.... I succesfully relashed my phone! I got the DC template bin file for the yellow UK rom - downloaded that same ROM and flashed it (turned my phone off then started the flash process). My phone is the black one and was on the oldest 821 ROM (unlocked) so was worried about putting a yellow ROM on it... btw - it gave me a msg at the start of the flash saying that it was not the right access IS or something for the phone - I chose ok and bit the bullet.
But it all went through ok with no errors and now I have a newer ROM and my bluetooth in the car is working a lot better. I hope my battery life will be better too... we will see....
If you want a step by step of what I did then let me know.....
Click to expand...
Click to collapse
were you using lumia 920 rom, if so can you upload the rom somewhere to download it with detailed instructions and how to re-flash to the phone.
thank you and I really appreciate it.
Hi, this rom is no longer on navifirm can someone upload it somewhere I've been searching it everywhere.
Rom's name
RM-820_Rogers_Canada_VAR240202_v2_Black
RM-820 Rogers Rom
Yes please , if someone has this rom could they give us a link to download it. As it no longer shows up on navifirm and I rather not flash the ATT version.
it doesnt work anyway...
What doesn't work?
You can't install it on your rogers
I bricked my Developer Lumia 920 , since developer firmware is not available. I was hoping to flash it with Rogers rom.
yeah mine too is a dev
Looks like the links on navifirm are still active, even though they don't show up in the program anymore.
I tried posting the direct links, but it wouldn't let me. I've instead attached a txt file with the links.
To be able to flash them/use them after downloading you might need to rename each file removing the checksum from the file name.
985F2CE8_RM820_1232.2109.1242.1002_RETAIL_nam_canada_200_02_100347_prd_signed.ffu
would be renamed to
RM820_1232.2109.1242.1002_RETAIL_nam_canada_200_02_100347_prd_signed.ffu
etc
If anyone can find links to the RM-820 dev firmware, or even evn just a dump(or produce a dump), it would be much appreciated.
Chilly2112 said:
Looks like the links on navifirm are still active, even though they don't show up in the program anymore.
I tried posting the direct links, but it wouldn't let me. I've instead attached a txt file with the links.
To be able to flash them/use them after downloading you might need to rename each file removing the checksum from the file name.
985F2CE8_RM820_1232.2109.1242.1002_RETAIL_nam_canada_200_02_100347_prd_signed.ffu
would be renamed to
RM820_1232.2109.1242.1002_RETAIL_nam_canada_200_02_100347_prd_signed.ffu
etc
If anyone can find links to the RM-820 dev firmware, or even evn just a dump(or produce a dump), it would be much appreciated.
Click to expand...
Click to collapse
Thanks for the links , I'll keep a lookout for the RM-820 dev firmware. Thanks once again !
I have a problem when I try to flash it it says recovery failed because it says that the FUU is not meant for that product... (and I changed the name of the files)
Error:
0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.MurzimProgrammingException: 0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__8(Object state)
and it's not the first time I flash it with the rogers rom
lolo2007 said:
I have a problem when I try to flash it it says recovery failed because it says that the FUU is not meant for that product... (and I changed the name of the files)
Error:
0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.MurzimProgrammingException: 0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__8(Object state)
and it's not the first time I flash it with the rogers rom
Click to expand...
Click to collapse
This is a known issue with the Rogers Portico ROM, and I assume the reason it was removed. I was the first person to bring this to light on this forum, and fixed it on my phone by installing the pre-Portico ROM and doing an on device upgrade. I do not have the original ROM files anymore, but just be aware you will need the old ROM to make this work.
Does anyone have the Apollo version of the rogers Nokia 920 then ?
Update: I think this guy uploaded it I am gonna try it I'll keep you all updated
update2: it works
http://forum.xda-developers.com/showthread.php?t=2098562
lolo2007 said:
yeah mine too is a dev
Click to expand...
Click to collapse
mine, too. been looking around for the dev fw
I did succesfully flashed my phone with a rom but i dont have it anymore
i ll try to find it again
. Is it in there or the nokia suite. Maybe I can help.
Sent from my GT-N7100 using xda premium
Chilly2112 said:
Looks like the links on navifirm are still active, even though they don't show up in the program anymore.
I tried posting the direct links, but it wouldn't let me. I've instead attached a txt file with the links.
To be able to flash them/use them after downloading you might need to rename each file removing the checksum from the file name.
985F2CE8_RM820_1232.2109.1242.1002_RETAIL_nam_canada_200_02_100347_prd_signed.ffu
would be renamed to
RM820_1232.2109.1242.1002_RETAIL_nam_canada_200_02_100347_prd_signed.ffu
etc
If anyone can find links to the RM-820 dev firmware, or even evn just a dump(or produce a dump), it would be much appreciated.
Click to expand...
Click to collapse
i downloaded the firmware but everytime i try to flash it i get an error regarding the signature; invalid signature any help??
ka24 said:
I bricked my Developer Lumia 920 , since developer firmware is not available. I was hoping to flash it with Rogers rom.
Click to expand...
Click to collapse
I recommend you don't flash the rogers firmware unless you plan on using the phone on Rogers/Fido/Chatr
It has a lot of issues with other carriers (despite being unlocked).
I bought a lumia from rogers without knowledge of these issues and now im stuck with a brand new, opened lumia that I cant use on Telus, and cant sell because WP8 isnt popular.
It would be nice if someone could get a hold of the dev ROM for the Lumia 920.
guys what do you mean by this
0xFA001106: Signature check of FFU file fails. Reason(s): The FFU file is not correctly signed
or not signed for this device.
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.MurzimProgrammingException: 0xFA001106:
Signature check of FFU file fails. Reason(s): The FFU file is not correctly signed or not signed
for this device.
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariant
PackageCompleted>b__8(Object state)
I have successfully installed the AT&T Amber Developer rom to a brand new Locked Black AT&T branded phone just delivered this morning from AT&T. I had to go with AT&T to make sure that I got model rm-820 to ensure complete compatibility with 4G/Edge. The phone is locked, but I'm waiting for an email from AT&T to unlock it.
Here's how I got it done, just took some time and a lot of patience. As a bonus, I also got internet sharing working, without calling 611 and having tethering turned on, here in the NE USA, on AT&T's network.
Please remember that this is for a BLACK phone. Adjust for different colors if possible.
Download and install the latest version of NCS.
Download Navifirm+ v2.3 here: http://www.symbian-toys.com/navifirm.aspx. No need to install, just run it when you need it to download the rom.
I only downloaded two roms:
Rom 1
The first one was the pre-portico Rogers rom. I downloaded the needed files from here: http://wp.it168.com/thread-217624-1-1.html
Download the files under this heading "059Q6W4: RM-820_Rogers_Canada_VAR240202_v2_Black" by right clicking each one and saving to C:\Program Data\Nokia\Packages\Products\rm-820. Remove the check-sum numbers from the front of each file name when the downloads are complete.
Rom 2
Use Navifirm, or any of the other means, to download rom 059R2L5 RM-820 AT&T DEVELOPER DEVICE BLK. Copy the downloaded files to C:\Program Data\Nokia\Packages\Products\rm-821.
Flashing the roms
Start NCS and open product rm-820. Select Rom code 059Q6W4 RM-820_Rogers_Cana... Version 1232.2109.1242.1002. That should be the only one there. Click the start button to flash the rom to the phone. Ignore the warning about it not being the correct rom.
When flashing is complete, setup the phone just enough to get to the settings. Connect to your WIFI. In settings, go to Phone Update and click on Check for Updates. Keep tapping on the phone to keep it awake though out this procedure. The phone will take forever to find, download and install the first update. When completed and the phone is reset and on, set WIFI and check for updates again. Follow the same procedure until you are told that there are no more updates. I believe that it was 3 updates, maybe 4. Be sure that your WIFI is enabled each time to prevent failure of an update.
Go to NCS and open product rm-821. Select Rom code 059R2L5 RM-820 AT&T DEVELOPER DEV... Version 3047.0000.1326.20... That should be the only one there. Click the start button to flash the rom to the phone. Ignore the warning about it not being the correct rom.
Enable internet sharing
When the installation is complete, setup the basics of the phone. Enable WIFI. Go to Setting/Access Point and select AT&T - LTE 2 - Lumia.
Go to Settings/Keyboard. I kept the English keyboard and removed the French keyboard. Click on add keyboards and select Spanish (Spain).
Turn off your phone. Turn on your phone and go to Settings/Phone Updates and check for updates. Once the Spanish keyboard is installed, turn off the phone and then turn it back on. No need to do a reset.
When the phone is back on and up fully, go to Settings/Internet Sharing and turn it on. You'll see a screen stating "Sharing your cellular data connection over WIFI... a Broadcast name and password lines. Already had two tablets going thru it as a test. Worked great. Also, go to Settings/Speech and select the language you want spoken to you.
Hope this helps everyone out. I didn't include how to use NCS, feel free to add that if someone wants to.
PS The AT&T rom failure mismatch platform message, which has kept everyone from installing AT&T dev rom, or even own AT&T's rom, onto AT&T branded phones is misleading. What is being checked is the first section of the VERSION NUMBER. AT&T update needs to see at least version 3047.0000... (Amber) of the Rogers_Canada rom on the phone you're flashing the rom to in order to be successful. AT&T also checks a kernal version, which is the same for AT&T and Rogers roms.
By installing 059Q6W4 RM-820_Rogers_Cana... Version 1232.2109.1242.1002, which is the only rom that will flash onto an AT&T branded phone, and updating, you're bring the phone version up to 3047.0000.... and now 059R2L5 RM-820 AT&T DEVELOPER DEV... Version 3047.0000.1326.20... will install successfully.
The phone is now working fully, without any issues that I've been able to uncover yet.
I welcome any and all comments.
Added observations:
To avoid connectivity issues flashing, be sure to use a 2.0 USB port, directly to your computer, NOT thru a USB hub. If you plug into some 3.0 USB ports or a USB hub (powered or not), NCS will see and read the phone, but will fail at flashing.
All files for a rom need to be kept in their separate directories for clean flashing! Best practice is to download the files to a directory named after the rom you're downloading. Rename the directory of the rom you want to burn to your model (rm-820 or rm-821) before starting NCS. I believe Navifirm+ v2.3 already handles downloads this way. Failure to do this can result in a goofy acting phone, missing/not working right features and other possible issues.
But can you go back to the stock at&t retail rom ?
Sent from my Xperia Tablet Z
Why would you want to???
Spectre51 said:
But can you go back to the stock at&t retail rom ?
Sent from my Xperia Tablet Z
Click to expand...
Click to collapse
Sure! After flashing rom 059Q6W4 RM-820_Rogers_Cana... Version 1232.2109.1242.1002, do NOT perform any updates.
Download rom 059L848 RM-820 NDT AMERICA ATT Black and flash to the phone. This will install the current AT&T stock rom, Version 1232.5692.1314.0001, loaded with AT&T branded pay-for bloatware.
Now I have to ask, WHY would you want to run the branded, outdated firmware that is loaded with AT&T's pay-for bloatware, AND removes useful utilities that can help you potentially save money on AT&T's network? (Unless you're returning the phone to AT&T and you don't want them to know that you screwed with it.).
My wife has had her AT&T branded red 920 for about a week now, with the stock Version 1232... AT&T rom. I gave her my phone (AT&T branded black 920) that I've flashed to the Amber (Version 3042...) update, using the AT&T developers rom, to compare it to her phone. She played with the phone for about 1/2 an hour.
She said that she felt that the phone seemed to responded snapper under certain conditions, music in background, facebook running, and a game paused. She also liked having access to Data Sense. We have a shared 4 Gig plan and who ever goes over will have to come up with the extra cash, so she liked being able to view her usage in real time. She also really liked the Setting/Display and touch, which lets you double tap the screen to wakeup and displays the time while off. Also, having Setting/Internet sharing enabled (With Spanish (Spain) keyboard installed.), was a big hit with her. She'll be able to connect and use her WIFI table while on the road.
Needless to say, now she wants the Developers rom on her phone.
Nice. Thank you but I do have another question for the At&T Dev Rom. Do you know the code for Cyan AT&T color or should I use the black Dev Rom?
Thanks
randy_c said:
Nice. Thank you but I do have another question for the At&T Dev Rom. Do you know the code for Cyan AT&T color or should I use the black Dev Rom?
Thanks
Click to expand...
Click to collapse
I have only seen the AT&T developers rom for Black. I believe the only difference is what default color the tiles are (matches phone color) and what color the phone reports when plugged in.
I always want the ability yo go back to stock no matter what. Just a safety net for me I guess. Have you tested that method to go back to stock successfully? Just ask because it doesn't seem anyone else had found a successful method.
Sent from my Sony Xperia Z
Spectre51 said:
I always want the ability yo go back to stock no matter what. Just a safety net for me I guess. Have you tested that method to go back to stock successfully? Just ask because it doesn't seem anyone else had found a successful method.
Sent from my Sony Xperia Z
Click to expand...
Click to collapse
Yes, you can, using the procedure explained in my last reply. And, yes, I was able to reload the stock (UGH) rom.
Sure! After flashing rom 059Q6W4 RM-820_Rogers_Cana... Version 1232.2109.1242.1002, do NOT perform any updates.
Download rom 059L848 RM-820 NDT AMERICA ATT Black and flash to the phone. This will install the current AT&T stock rom, Version 1232.5692.1314.0001, loaded with AT&T branded pay-for bloatware.
I wonder why so many having problem going back to AT&T stock ROM
randy_c said:
Sure! After flashing rom 059Q6W4 RM-820_Rogers_Cana... Version 1232.2109.1242.1002, do NOT perform any updates.
Download rom 059L848 RM-820 NDT AMERICA ATT Black and flash to the phone. This will install the current AT&T stock rom, Version 1232.5692.1314.0001, loaded with AT&T branded pay-for bloatware.
I wonder why so many having problem going back to AT&T stock ROM
Click to expand...
Click to collapse
After installing Rogers Version 1232, even one update will prevent reloading stock AT&T rom. If you don't flash the stock rom immediately, you risk having the phone being updated automatically.
I think this thread would get more input in the 920 windows phone development section..
Yes the OP says its possible to go back to the ATT stock rom. They say not to let the phone update once on the Rogers preportico rom. From there, flash back to the ATT rom. It's supposed to work every time.
da1stprince said:
I think this thread would get more input in the 920 windows phone development section..
Click to expand...
Click to collapse
I believe that would be up to a moderator to make that decision and implement the change.
Returning to Stock
Once you have flashed the AT&T Developer ROM, is it possible to flash back to the Rogers Pre-Portico ROM to return to AT&T Stock?
Has anyone tested this?
JobuJones said:
Once you have flashed the AT&T Developer ROM, is it possible to flash back to the Rogers Pre-Portico ROM to return to AT&T Stock?
Has anyone tested this?
Click to expand...
Click to collapse
as explained in the posts above the answer is yes. You can go back to pre-portico Rogers and without running any OTA updates on the pre-portico Rogers (any updates will prevent you to flash to stock ATT) you can go back to stock ATT rom.
derausgewanderte said:
as explained in the posts above the answer is yes. You can go back to pre-portico Rogers and without running any OTA updates on the pre-portico Rogers (any updates will prevent you to flash to stock ATT) you can go back to stock ATT rom.
Click to expand...
Click to collapse
Thanks! I just wanted to verify that this works! :good:
When attempting to use NCS, I get the error, "Data package selection failed. Access is denied. Verify credentials."
I'm using 5.0.0 (2013.1.3) and I've moved the .cfg file to the appropriate location. Any ideas?
UPDATE - My problem was resolved by following the flashing procedure in this thread
I'm now running the AT&T GDR2 & Amber update - Thanks!
derausgewanderte said:
as explained in the posts above the answer is yes. You can go back to pre-portico Rogers and without running any OTA updates on the pre-portico Rogers (any updates will prevent you to flash to stock ATT) you can go back to stock ATT rom.
Click to expand...
Click to collapse
I don't think this is accurate info, please correct me if I'm wrong but don't you need to do OTA updates while in the pre portico rom in order to flash up to amber rom? I just successfully flashed a Rogers pre portico rom onto my att L920 and flashed back to my original stock rom because for some reason I couldn't flash the att amber dev rom (ID invalid errors) and the only reason I could think of as to why it wouldn't flash for me is because of a lack of OTA updates while in the rogers pre portico rom..
da1stprince said:
I don't think this is accurate info, please correct me if I'm wrong but don't you need to do OTA updates while in the pre portico rom in order to flash up to amber rom? I just successfully flashed a Rogers pre portico rom onto my att L920 and flashed back to my original stock rom because for some reason I couldn't flash the att amber dev rom (ID invalid errors) and the only reason I could think of as to why it wouldn't flash for me is because of a lack of OTA updates while in the rogers pre portico rom..
Click to expand...
Click to collapse
My post was referring to go back to ATT stock rom once you have been to some Amber rom. You can only go back to stock ATT if you reflash with pre-portico Rogers and not have it do OTA. Once you get an OTA you cannot go back to stock ATT. You basically confirmed this. To go to Amber you have to do OTA on the pre portico Rogers.
derausgewanderte said:
My post was referring to go back to ATT stock rom once you have been to some Amber rom. You can only go back to stock ATT if you reflash with pre-portico Rogers and not have it do OTA. Once you get an OTA you cannot go back to stock ATT. You basically confirmed this. To go to Amber you have to do OTA on the pre portico Rogers.
Click to expand...
Click to collapse
thanks for the confirmation, guess if I had to send this unit in for repair/replacement, I can flash the at&t dev rom and not have to worry about voiding any warranty
I tried going back to the pre portico rom and all I get is an error 0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device. I can flash to a french rom I found on wpc and the att dev rom but the not the pro portico rom. Can anyone help me out?
Does anybody have any insider information about its release? I do regret flashing that Rogers rom just for that damn amber. Naturally AT&T knocked out those updates rather quickly after I flashed.
Sent from my Nokia Lumia 920 using Tapatalk
Same boat here. While I did manage to get hold of what looks like an official AT&T Black update (from mrcrabs site), all three Nokia flashing tools fail to flash over. The version number is higher than the Rogers ROM or the AT&T Dev ROM. NCS gives the dreaded FFU error while Nokia for retail and Nokia recovery tools give some obscure 0x series error. Seems nobody has been able to 'force' the AT&T update, ignoring what's currently on the phone. Def sucks!
lilmagnus said:
Same boat here. While I did manage to get hold of what looks like an official AT&T Black update (from mrcrabs site), all three Nokia flashing tools fail to flash over. The version number is higher than the Rogers ROM or the AT&T Dev ROM. NCS gives the dreaded FFU error while Nokia for retail and Nokia recovery tools give some obscure 0x series error. Seems nobody has been able to 'force' the AT&T update, ignoring what's currently on the phone. Def sucks!
Click to expand...
Click to collapse
You tried to download the ROM with Data Package Manager?
Because, mrcrab.net renames all files of the ROM.
So, its been a rough time with this phone. I received it rooted and im really a noob to any of this, its a verizon phone, its labeled outside, and when you remove the battery it says model VS985. But in the settings it says otherwise. I placed an att sim card in it, and it worked fine, i just had some errors on the rom that i have no idea how to fix, it all just seems like a hassle to me, so i decided to unroot it to the best of my ability. I managed to download everything and when i ran the lg flash tool, i selected the firmware i downloaded, the verizon one, but when i tried to run it, it would say "Device Model is different" "factory model check error" or something like that, it would identify the phone has D850, which is at&t version.
So i went ahead and said **** it, i downloaded that version and went with that, something messed up and it ended with factory reset status 2 instead of 3.
So i had to select BOARD instead of UPGRADE in the flash tool. and it reset everything, booted with att logo and everything, now the only problem is i don't get any signal, at all. Any help?
cedric182 said:
So, its been a rough time with this phone. I received it rooted and im really a noob to any of this, its a verizon phone, its labeled outside, and when you remove the battery it says model VS985. But in the settings it says otherwise. I placed an att sim card in it, and it worked fine, i just had some errors on the rom that i have no idea how to fix, it all just seems like a hassle to me, so i decided to unroot it to the best of my ability. I managed to download everything and when i ran the lg flash tool, i selected the firmware i downloaded, the verizon one, but when i tried to run it, it would say "Device Model is different" "factory model check error" or something like that, it would identify the phone has D850, which is at&t version.
So i went ahead and said **** it, i downloaded that version and went with that, something messed up and it ended with factory reset status 2 instead of 3.
So i had to select BOARD instead of UPGRADE in the flash tool. and it reset everything, booted with att logo and everything, now the only problem is i don't get any signal, at all. Any help?
Click to expand...
Click to collapse
Somewhere in the g3 forums is an unbranded DLL file. It is my understanding from reading about it previously, you need to use that to allow you to flash the proper firmware. The DLL file was made to fix this exact issue from what I read before.
bweN diorD said:
Somewhere in the g3 forums is an unbranded DLL file. It is my understanding from reading about it previously, you need to use that to allow you to flash the proper firmware. The DLL file was made to fix this exact issue from what I read before.
Click to expand...
Click to collapse
Really? any more info on how to find it?
cedric182 said:
Really? any more info on how to find it?
Click to expand...
Click to collapse
I wish I could point you right to it, unfortunately you may have to browse similar help threads to yours until you find it.
I have the exact same problem but mine is seen as a d855 when it is a vs985 if you can find that .dll file please tell me as well! I am going to search for it now
cedric182 said:
So, its been a rough time with this phone. I received it rooted and im really a noob to any of this, its a verizon phone, its labeled outside, and when you remove the battery it says model VS985. But in the settings it says otherwise. I placed an att sim card in it, and it worked fine, i just had some errors on the rom that i have no idea how to fix, it all just seems like a hassle to me, so i decided to unroot it to the best of my ability. I managed to download everything and when i ran the lg flash tool, i selected the firmware i downloaded, the verizon one, but when i tried to run it, it would say "Device Model is different" "factory model check error" or something like that, it would identify the phone has D850, which is at&t version.
So i went ahead and said **** it, i downloaded that version and went with that, something messed up and it ended with factory reset status 2 instead of 3.
So i had to select BOARD instead of UPGRADE in the flash tool. and it reset everything, booted with att logo and everything, now the only problem is i don't get any signal, at all. Any help?
Click to expand...
Click to collapse
If you are 100% sure you do in fact have the Verizon LG G3 (VS985), replace the Verizon DLL file with the Generic LG G3 DLL below. This error is most common if you have changed the Product Name, Product Model, Display ID, and/or Build ID entries in the build.prop
The generic dll file is on autoprime's site. It's named LGUP_8974.dll and can be found here- http://downloads.codefi.re/autoprime/LG/LG_G3 Use that along with the Verizon firmware Instead of the Verizon dll
Hawkswind thank you so much!! that worked for me now i am going to flash back the verizon .dll file
Thank you.