I tried to flash a rom in my phone but every time when I does this, just before the flashing begins, the update program ends with: No retail device and I cannot continue.
It goes fine into download mode. Any clues ?
I'm guessing the Samsung updater knows that the device shouldn't be available and so will not update it. I don't know if there is a way around this.
EDIT: Should just check, is your device retail? Or is it some other version of the Omnia you've got?
Casey
It isn't a retail device. It came in an unmarked box. I have had my share of devices that were not supposed to be flashed over the last years and still managed to flash them. But this is a tough one. Cannot find a way to do this.
On second thought: Is there another flash program available ? Looks like the retail flasher checks if it is retail. (It will be after I flashed it).
It outputs this error:
[Channel 0] Confirm Model Name
[Channel 0] FLASH LOCK
No other solutions available ?
Not that I've seen
I have exactly the same problem. My device comes from the batch of the early prototypes and I can't flash it to a new firmware. Neither it updates to 7008 through Zune as it always says the phone is up-to-date.
Big shame, I'm stuck to the 7004... Any idea for solution?
I suppose you could try contacting Samsung? Maybe visit one of their service centres to see if they can flash it for you?
Casey
@Ivoky
Mine is too but it is updated to 7008. Guess I can update it to NoDo too with the instructions on the Omnia general forum. But the receptance is much better with the latest firmware. That is why I would like to upgrade.
For the Samsung Taylor you have to use the ChevronWP7 NoDo Updater to update the phone to NoDo.
did you find any solution to update?
Related
Hi there,
I successfully upgraded my SGS to 2.2.1 (JPY) via the Kies Registry Patcher in January. All seems well however I just tried doing exactly the same trick with my sister-in-laws SGS and no luck. Successfully got her rooted and unlocked, but for some reason I cannot get the registry spoof working.
I know I have not done things in exactly the same order for her phone, but it is bugging me. I tried with Kies 1.5(?) but when the phone was plugged into Kies it flashed up the "You can update your firmware" but when the actual process kicked off no firmware was available. She's on JF3.
Her SGS is from the same company, locked to the same network. The only thing I can think of is that the original spoof I did is still in my system registry and that her values do not match up in the same way? I have no idea...
I have now updated to Kies 2.0 to see if I can just get a normal 2.2 update for the T-Mobile firmware, but if her experience is like mine, that firmware has to go! So 2.2.1 XEU is the goal.
Any ideas?
As a side issue, now that OTA is enabled for 2.2.1, does that mean I will never have to fight Kies for an update?
http://forum.xda-developers.com/showthread.php?t=959806, as well you could also use Odin/Heimdall (? spelling) to flash a 2.2.1 ROM. OTA is not currently activated.
OTA at Samsung end? As the option is there on my phone and when i run it is says "no updates available".
Anyway - yeh. I saw that link. Will check it out when I next get my mitts on her phone.
What I don't know is what has changed? Has ?Samsung wised up to the previous spoof in some way?
skinfreak said:
OTA at Samsung end? As the option is there on my phone and when i run it is says "no updates available".
Anyway - yeh. I saw that link. Will check it out when I next get my mitts on her phone.
What I don't know is what has changed? Has ?Samsung wised up to the previous spoof in some way?
Click to expand...
Click to collapse
You can spoof by patching a file to make Kies2.0 believe that another firmware is connected, but when the update starts, another check is made directly to the phone, which is new as of Kies2.0. This is where we get stuck in patching Kies2.0. The module that checks this is encrypted which makes is impossible to patch it.
This is why I went for another approach and spoofed the firmware that the device is reporting, to fool Kies2.0 in every moment
Allot of us forced the mango update on Zune, but did not get the new drivers from Samsung.
So here it is a quick and dirty way of getting you phone up to date
Download the package from Here.
Unrar it to you pc.
Plug in you Omnia ,make sure Zune is not open.
If you have windows x64 click on the update-driversx64.bat shortcut.
If you have windows x86 click on the update-driversx86.bat shortcut
Follow the promps...
Notes:
You doing this at you own risk.
update can take up to 30 minutes
Tested in windows xp with an unbranded Omnia7, in windows vista or seven you may need to run the shortcut as an administrator.
After the update your Firmware version should be 24.11.8.5 and Bootloader version should be 5.8.1.9
You doing this at you own risk.
Good Luck.
As I see from FW number and BL version, these should be drivers from KH5 FW.
What's the difference, if any at all, with KH2 FE, i. e
FW 2424.11.8.2
BL 5.8.0.8
Radio is the same in both - 2424.11.7.2
rgds
I updated to Mango and ended up with the 2424.11.8.2 firmware instead of 2424.11.8.5 as well. Very tempted to use this method to update my Omnia 7. Will using this method cause any problems updating via Zune in the future?
timolol said:
I updated to Mango and ended up with the 2424.11.8.2 firmware instead of 2424.11.8.5 as well. Very tempted to use this method to update my Omnia 7. Will using this method cause any problems updating via Zune in the future?
Click to expand...
Click to collapse
No,since this is an official update.
Sent from my OMNIA7 using XDA Windows Phone 7 App
cerato said:
As I see from FW number and BL version, these should be drivers from KH5 FW.
What's the difference, if any at all, with KH2 FE, i. e
FW 2424.11.8.2
BL 5.8.0.8
Radio is the same in both - 2424.11.7.2
rgds
Click to expand...
Click to collapse
As far as i know they are the same.
i have the unofficial RTM.will work anyway?
andw93 said:
i have the unofficial RTM.will work anyway?
Click to expand...
Click to collapse
Im not 100% sure but it should, the update only goes thrue if required by the device, if the devices does not need it or not compatible the update gets discarded.
I had the Mango flashed following threads from here from a month or so ago , a night or 2 ago i got 1 update (A Samsung update) i have had no others though i have the fw and bl mention in the first post . Am i up to date with only this one update ??
Others have mentioned "Beta clean ups" i haven't had these
Good. I got problems updating the drivers via zune. I guess those are official I'll be updating soon.
Thank you
worked like a charm, I needed this to get the wifi tethering to work, had the option there any everything but needed the sammy drivers.
I have an Omnia 7 that is "3" branded. I was running RTM 7220, plugged my phone into zune and it had 10 updates..
am I right in thinking I now have official Mango? so confused as everyone else seems to say the update hasn't come for us yet, but mines there now with hidden wifi and everything..
Installed the update and it works like a charm. Thank you.
Before :
FW : 24.11.2.3
Bootloader : 5.2.1.4
After:
FW : 24.11.8.5
Bootloader : 5.8.1.9
Hi guys,
I'm getting update error on Mango 7720.
This is my Mango upgrade path..
NoDo -> ISV Beta -> 7403 -> 7720
I've been unable to install the Samsung Firmware, all I get is:
Error:
Update device 9d76937d - e66da2ea - e6327312 - f45fcae9 Complete with error code
: 80180048, error message: IU (Image Update) installation failed due to an error
.
Click to expand...
Click to collapse
The only restore point that I have is NoDo+Prov.cab that brought my phone to the Beta path (takesonetomango tool). Meaning that if I connect my phone to Zune, it says that the 'ISV Beta' update is available.
Anyone have any idea on how I could get the latest firmware? or possibile unprovision my phone so I could get on the normal path..and hopefully get the firmwares through the official production server?
I'm hoping that I won't need to reflash my device as it contains many SMS messages that I'd like to keep.
Works perfectly.
But I dont see any changes, what does this update exactly do?
Qtek8020User said:
Works perfectly.
But I dont see any changes, what does this update exactly do?
Click to expand...
Click to collapse
For one it updates the sensor drivers, for instances, without this update the compass does not work.
Is this WP7_ENGINEER or WP7_PRODUCT???
vosathanh said:
Installed the update and it works like a charm. Thank you.
Before :
FW : 24.11.2.3
Bootloader : 5.2.1.4
After:
FW : 24.11.8.5
Bootloader : 5.8.1.9
Click to expand...
Click to collapse
Strange, I went from NoDo through the Mango RTM process and my boot loaders the same yours, but my FW: 2424.11.8.5..has my update screwed up? Lol
Spookidoodles said:
Strange, I went from NoDo through the Mango RTM process and my boot loaders the same yours, but my FW: 2424.11.8.5..has my update screwed up? Lol
Click to expand...
Click to collapse
I went from Mango beta 7712, but FW and BL version very old
all is good...forced mango
and this has update all my sammy drivers on my three handset
techdave said:
Hi guys,
I'm getting update error on Mango 7720.
This is my Mango upgrade path..
NoDo -> ISV Beta -> 7403 -> 7720
I've been unable to install the Samsung Firmware, all I get is:
The only restore point that I have is NoDo+Prov.cab that brought my phone to the Beta path (takesonetomango tool). Meaning that if I connect my phone to Zune, it says that the 'ISV Beta' update is available.
Anyone have any idea on how I could get the latest firmware? or possibile unprovision my phone so I could get on the normal path..and hopefully get the firmwares through the official production server?
I'm hoping that I won't need to reflash my device as it contains many SMS messages that I'd like to keep.
Click to expand...
Click to collapse
I'm getting the same error. This is really frustrating.
Hi,
Device is Ativ-S i8750 bought through Handtec. Operating on GiffGaff UK PAYG.
OS 8.10.14203.306
FW: 2424.13.10.1
CSC : XEF
I've searched around and found a little info about the problems with my camera since installing the 8.1 update through developer preview. Apparently it's fixed in firmware update 2424.14.9.3 which came out around October last year.
While my phone has picked up OS update, I don't seem to have picked up any firmware updates four months down the line.
I've have searched to find out what to do next but I am a bit stuck and unsure what to do next. So hope this community can help. Is there anything I should be doing to get this update other than just waiting?
Thanks!
Smoothound said:
Hi,
Device is Ativ-S i8750 bought through Handtec. Operating on GiffGaff UK PAYG.
OS 8.10.14203.306
FW: 2424.13.10.1
CSC : XEF
I've searched around and found a little info about the problems with my camera since installing the 8.1 update through developer preview. Apparently it's fixed in firmware update 2424.14.9.3 which came out around October last year.
While my phone has picked up OS update, I don't seem to have picked up any firmware updates four months down the line.
I've have searched to find out what to do next but I am a bit stuck and unsure what to do next. So hope this community can help. Is there anything I should be doing to get this update other than just waiting?
Thanks!
Click to expand...
Click to collapse
rather annoyingly the only way I got it was to flash back to GDR2 and work upwards. Royal pain in the arse if im honest but I got there in the end, I believe it was disabled in some of the CSC images that were flashed because upgrading to it also disables some of the ability to unlock the device. As much as I liked the idea of it being unlocked I didn't make any real use of it so decided to bite the bullet and flash it back an upgrade, several hours later, back on DP with a working camera and a more stable Bluetooth stack!
___
dazza9075 said:
rather annoyingly the only way I got it was to flash back to GDR2 and work upwards. Royal pain in the arse if im honest but I got there in the end, I believe it was disabled in some of the CSC images that were flashed because upgrading to it also disables some of the ability to unlock the device. As much as I liked the idea of it being unlocked I didn't make any real use of it so decided to bite the bullet and flash it back an upgrade, several hours later, back on DP with a working camera and a more stable Bluetooth stack!
Click to expand...
Click to collapse
Thanks for the reply, man. Sorry for my slow response.
I was hoping there was another way around this. Thanks anyway!
Is there a total n00bs guide to flashing an Ativ-S back to GDR2?
EDIT : I found this : http://forum.xda-developers.com/showthread.php?t=2391138&page=11 - but looks like the ROMs are no longer up
I have the same problem, but am still on firmware 2212.13.11.2 (and hardware 15.3.1.0, bootloader 13.08.14.16). Phone is a SGH-T899M by the way. Because of PfD my OS is 8.10.14203.306, which is recent. Disabling PfD doesn't make my phone upgrade the firmware, nor did it when my OS was a few months older.
It might be that in this thread (http://forum.xda-developers.com/win...aylors-super-rom-tool-dump-sgh-t899m-t3037789) the solution can be found to downgrade but there's a bit too little step-for-step instructions for me to do it. If someone can give them to me (or a different solution to force my phone to upgrade firmware), then I'd be thankful!
EDIT: in the ATIV SE (thanks to the author) thread there's a how-to 'hidden' in the download. It goes as follows:
1. If you have not done so already, extract the .zip file that this is contained in and ensure that you are working from the unzipped folder
2. Install SamsungUSBDriver.msi and restart
1b. If you have Windows 8.1 x64 you need to disable driver signature verification first:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
3. Extract the file SM-W750V_VRU0ANC2_R_signed_2.zip
4. Power off device (and leave it unplugged)
5. Open the file WP8_Binary_Downloader_Ver._3.54.exe
6. Click the yellow/orange folder and Open the file SM-W750V VRU0ANC2_R_signed.wp8
7. Click the green folder and Open the file SM-W750V_VRU0ANC2_R.csc
8. Boot into Download Mode (hold Vol. Up and Home buttons while device is powering on)
9. Plug in your phone
10. If it shows up in the Channel Information section and does not report an error, you are ready
11. Last chance to consider saving your data
12. Press start
13. Wait until it has completely finished and your phone has rebooted
14. Skip through initial setup, go to Settings > about, and reset your phone once before using it
15. Enjoy stock!
I guess this should be the same for other phones, but you have to exchange the file with the file for your phone as given in the taylors-super-rom-tool-dump thread. Ofcourse, no guarantees, this is what seems logical with my limited knowledge
Hi Guys,
Just to let you know - I managed to flashed with GDR2 - file GTi8750-OXABME1_R.
It wouldn't update to 8.1 until I changed CSC from XEF to ATO, then it picked up the new firmware and 8.1. It just finished installing a few moments ago.
So I am now on :
Software: Windows Phone 8.1 Update
OS version: 8.10.14157.200
Firmware: 2424.14.9.3
I have tried checking for more updates and now I am getting error 80072f8f, which apparently it time related, even though time is correct. Same after a reboot. So not sure if I'll get any futher updates till I can work around this.
How far am I off the most current OS version for ATIV?
EDIT : Took a punt that it was the CSC that was causing the time problem. So switched CSC to BTU (which apparently is UK. British Telecom maybe?) - and it's now saying it's downloading updates!! \o/
EDIT : The phone reinstalled, did the gears. But OS version is unchanged. I do however have a newer firmware still: Firmware revision number: 2424.15.3.2
Hello guys,
I have failed. And now I do not know how to continue.
My tragic storry: I wanted to update my HUAWEI P9 from Marshmallow to Nougat and got an error during update, because I am an idiot. I took an (wrong) update from some site, putted it in a dload folder on a sd card and started the update. The update started, the phone rebooted and continued. But at 5% comes "Software update failed! Incompatibulity with current version. Please download the correct update package."
After that I started to search for a solution.
Now I found this site and it seems that here are a lot of people, that are able to solve such problems between wakeup and teeth brushing. I hope someone here can help me with good advices, which avoid me of damaging my phone completely and bring me instead on the way that I can solve my problem.
Enough of the chatter, this is my current knowledge (correct me if I am wrong):
I have (had) a P9 with EVA-L19C636B190 Firmware. (I have noted this before update)
L19 stands for the dual sim P9.
C636 is the Asia/Pacific Hardware
B190 was the old version of stock Android (Marshmallow)
(I know now, that I have tooked the wrong Hardware-Package. I should have taken C636 and
everything would have become beautiful)
As I understand, the wrong Firmware is now on my phone and the bootloader try to continue the update each time I start an Update.
If I start the phone normaly, I get the EMUI logo with the options to "Download latest version and recovery" (No way, with the wifi connection, he can not find a server to download), "Reboot" and "Shutdown".
I suppose, that there is a partition on my phone, where the wrong update file was loaded to. Because if I try to "update" back to EVA-L19C636B190, there is no difference, the update ends at 5%, even without a sd card. So I think, that I need to clear this partition and need to start an update with the dload-folder-method again.
As I understand some artikles here, I need for that a special tool (SRK), with which I can clear the partition in the FASTBOOT&RESCUE MODE. But for that the phone must be unlocked.
In next step I need to unlock the boatloader with the huawei online tool where i get the unlock code based on my serial number and so on.
What would you say to my plan? Or is there an easier method?
What do I need for that?
Please be indulgent with me, I try to learn and to undestand to solve my problem
Thank you in advance.
I bought a LM-V450ebw Dual SIM with android 8x, probably HongKong distribution. I've beed trying to flash it to EU/Polish ROM (android 10) with no possitive effect (I want to have volte and wifi calling - that's the main reason to update).
I've beed trying LGUP 1.14-1.16 with different LGDLL but no way to overcome "error: 0x6004, crossdl open_hk_ds>open_eu_ds"
Finally I tried to update to android 10 Hong Hong version and I succeeded (v30b-lao-yt). But still no success in moving to EU/Polish ROM (android 10) via LGUP - "error: 0x6004, crossdl open_hk_ds>open_eu_ds"
It looks like, there is no problem to move between HK version but no way to move from HK -> UE/Polish.
Of course LG Bridge doesn't help much.
What's wrong? Is there any way to do it without rooting?
pjgadek said:
I bought a LM-V450ebw Dual SIM with android 8x, probably HongKong distribution. I've beed trying to flash it to EU/Polish ROM (android 10) with no possitive effect (I want to have volte and wifi calling - that's the main reason to update).
I've beed trying LGUP 1.14-1.16 with different LGDLL but no way to overcome "error: 0x6004, crossdl open_hk_ds>open_eu_ds"
Finally I tried to update to android 10 Hong Hong version and I succeeded (v30b-lao-yt). But still no success in moving to EU/Polish ROM (android 10) via LGUP - "error: 0x6004, crossdl open_hk_ds>open_eu_ds"
It looks like, there is no problem to move between HK version but no way to move from HK -> UE/Polish.
Of course LG Bridge doesn't help much.
What's wrong? Is there any way to do it without rooting?
Click to expand...
Click to collapse
For most of the variants all that's needed to crossflash is to use 1.14 and choose 'partition download'. But the HK dual sim variant is a pia. You can lose one or both sims if not done correctly.
I'd suggest, in rom forum see initial thread for lineage os and find invite to join v40 tele group. Ask there as those guys have much more international experience especially with dual sim variants.
cheers
Similar problem wit a new LM-V405EBW running Android 9 sec patch 1 June 2019
It is supposed to be an European version, came with a EU charger ...
Current software V20a-LAO-YT
Checked with a IMEI checker that said it is a DEC region phone.
It seems LG has removed V40 Thinq from the supported devices,
cannot get any OTA updates :-(
I want to install V405EBW30d_00_OPEN_EU_DS_OP_1223.kdz
latest DEC firmware I think.
When I try LGUP i get the same error mess as above
"error: 0x6004, crossdl open_hk_ds>open_eu_ds"
Tried both "refurbish" and "update" same error.
I don't mind to wipe the phone clean,
but when i select the "Partition DL" i get more than 10 options,
which one(s) should i select ?
Hope I can get some advice.
LG_User_42 said:
Si
I don't mind to wipe the phone clean,
but when i select the "Partition DL" i get more than 10 options,
which one(s) should i select ?
Hope I can get some advice.
Click to expand...
Click to collapse
all of them except ftm. Then, when it finishes and reboots, do the refurbish (twice) with the same kdz.
cheers
Evening! I bring you a solution, it seems a strange solution, but after weeks of trying anyway, the only one that did not occur to me, is to disconnect it while I was flashing the rom that I put wrong to downgrade it, i cause a provocated brick, what is my surprise when insert the IBR rom (before it had the TIM) it started flashing without problem.
Mobile to repair: Lg K41S (LMK410EMW)
Use this version of the LGUP flash tool: LGUP_Dev-1.14 (patch)