Develop Bugs

Error 262 when attempting Coke 2.31

So here's the situation. I've had a Touch before, and unfortunately after I broke my ribs I was spaced out on painkillers (which is why I don't take them) and forgot to pull it out of my pants before they did the good ol' wash cycle.
I finally got one back, and now I can't get anything going for me. I know for a fact I can flash the device since the new one came with the original stock WM6 ROM. Not even the 6.1 ROM, just plain old WM6. After several failed attempts to get Coke 2.31 on there I finally just said to hell with it and tried the MR1 update from VZW just to make sure it wasn't my PC.
Sure enough that one worked perfectly every step of the way.
Everytime I attempt to unlock the phone though it just fails with Error 262. I've tried every way I can think of.
I tried it with the 'Enable advanced network functionality' both on and off. I've reinstalled WMDC multiple times. I've tried it while in Windows Mobile, and while on the bootloader which just gives me the stock Vogue VZW info...nothing showing it is even getting anywhere in the unlock process.
I even tried the last resort of flashing from the MicroSD which of course just said loading for about half an hour and went nowhere.
I've read threads here and on PPC backwards and forwards on how to do this.
I've done it multiple times before on the old one before I sent it to an early grave.
I'm going nuts here trying to figure out what in the world it could be that I'm doing wrong.
Help?!?

Morpheus Phreak said:
So here's the situation. I've had a Touch before, and unfortunately after I broke my ribs I was spaced out on painkillers (which is why I don't take them) and forgot to pull it out of my pants before they did the good ol' wash cycle.
I finally got one back, and now I can't get anything going for me. I know for a fact I can flash the device since the new one came with the original stock WM6 ROM. Not even the 6.1 ROM, just plain old WM6. After several failed attempts to get Coke 2.31 on there I finally just said to hell with it and tried the MR1 update from VZW just to make sure it wasn't my PC.
Sure enough that one worked perfectly every step of the way.
Everytime I attempt to unlock the phone though it just fails with Error 262. I've tried every way I can think of.
I tried it with the 'Enable advanced network functionality' both on and off. I've reinstalled WMDC multiple times. I've tried it while in Windows Mobile, and while on the bootloader which just gives me the stock Vogue VZW info...nothing showing it is even getting anywhere in the unlock process.
I even tried the last resort of flashing from the MicroSD which of course just said loading for about half an hour and went nowhere.
I've read threads here and on PPC backwards and forwards on how to do this.
I've done it multiple times before on the old one before I sent it to an early grave.
I'm going nuts here trying to figure out what in the world it could be that I'm doing wrong.
Help?!?
Click to expand...
Click to collapse
Did you read my tutorial? It is the one stickied on this sub forum. If I were you, I would try an XP computer. This usually seem to give more issues than not. Also, the 262 error is a connection error, so a simple check would be to change the USB port that you are using to connect. Finally, you could try mtty (if you feel adventurous enough).... but I would rather go to the XP option first.
Good luck and let me know how it turns out!

This is what I had to do on my Dell Pentium 4 running Windows 7 32 bit to get mine to flash. I went into Control Panel/ Hardware and sound and Changed connection settings for WM Device Center. I unchecked everything. Then I right clicked on the ROMUpdateUtility.exe for coke 2.31 and clicked on troubleshoot compatibility and for the system to run it in XP service pack 2 mode. Then I ran the ROMUpdateUtility.exe as administrator and it worked!

egzthunder1
Your guide is actually the main one I was trying to use to get this all to work out
My big problem is that I don't have any machines with XP on them around here anywhere
Even my 5-year old laptop is running Windows 7 at this point, and I don't have the old factory restore discs for it to toss XP back on there.
neuteboomt
I just gave that a try and for some reason when I uncheck all of those settings nothing sees the phone at that point, not even the updater.
I am trying to find a way to make Virtual XP Mode see the phone since over on Modaco a ton of people have managed to unlock their omnia's in XP Mode with 0 issues...I just have to get the files all downloaded to try it out.
Edit:
Well got all the files needed to try in XP Mode, and it still gives me a 262. I think I found an old image backup of my laptops XP disc though so I'm going to try to reformat my laptop and go back to XP on it to see if all this works.
I'm hoping it does, otherwise I'm going to be spending a crapload of time playing around with operating system installs
Well that image wasn't the right one for the laptop...so it was a no go...found the right image for my laptop though so it'll take a few hours to get everything all set back up on the laptop and ready to go.
I'm hoping to report back by 3PM or so today on whether or not it all worked out.

you should read through this http://forum.xda-developers.com/showthread.php?t=569922 he was having the same issue and what i suggested worked for him

Barogi44 you are the man. I have the phone unlocked now
I can't figure out why that made a difference, but it sure did and now the phone is updating with the Bell Rom on its way to having the NFSFAN ROM on it

Morpheus Phreak said:
Barogi44 you are the man. I have the phone unlocked now
I can't figure out why that made a difference, but it sure did and now the phone is updating with the Bell Rom on its way to having the NFSFAN ROM on it
Click to expand...
Click to collapse
Im glad i could help

2.1 update 1 fail, plz help

Well i just got the, as Carlsberg says, probably the best phone out there , i love it, but i have a small little problem. I don't know what happened but when i made the 2.1 update 1 it didn't applied it . u can see the picture where it says 2.1 update 1 BUT the other numbers are like before, and i checked and the changes and they where NOT applied, no HQ youtube, still the problem with the keyboard when long press menu in home screen. I alse checked bootloader, still the 0.75. Now when i check for updates OTA it says : "No new updates available". My phone is not rooted, just got it. And yes, i rebooted phone, several times. No hard reset yet.

First of all, the line with "2.1-update1" is not changed by the update, so that is no indication
With that out of the way, maybe this can help:
http://blog.gamermatrix.co.uk/?p=194
I have not tried it, as my phone updated fine by itself.
Be sure you have the version that it mentions ("unbranded EU"), and even then it is all at your own risk...
You might want to try it first from step 3: if the update is already somewhere on your sd-card, maybe hidden or disguised, then it would be best to use that of course.
For my phone the update lasted about 7 minutes and took about 3 reboots to finish.
Good luck with it!

tx
Oh, tx about the info, i thought it tried to update and failed, i am not eager to do it, i'll just wait for froyo update. I have one more question: i will receive an unlock key to remove my vodafone only limitation, then will i have an unbranded phone or it will still be branded but unlocked?

Rollback NoDo update only once

Hi,
It seems that the rollback works only once.
So, i installed the NoDo update and the rollback option was in Zune, at Settings->Phone->Update.
I rollback it and after a while put it again, because i got the "an update is available" every time i connected Zune.
This time there is no rollback option on Zune, Settings->Phone->Update page, it only display:
Your Phone is up to date.
Current phone software version: 7.0 (7390).
So i think the only way to roll back now is hard reset(i didn't tried that yet).
It is a feature or a bug?

Not sure. I accidentally did not remember to apply the relock prevention registry edit on my Samsung Focus before I updated to Nodo. As a result my phone became locked again and I lost my ability to sideload.
I restored my phone to the Feb update through Zune, made sure to unlock the phone and apply those registry edits, and reupdated to Nodo. I successfully got my phone back to a dev unlocked state =)

Check to be sure your phone isn't connected as a guest partnership and that its the exact same device name. Just a thought.

holimon82 said:
Hi,
It seems that the rollback works only once.
So, i installed the NoDo update and the rollback option was in Zune, at Settings->Phone->Update.
I rollback it and after a while put it again, because i got the "an update is available" every time i connected Zune.
This time there is no rollback option on Zune, Settings->Phone->Update page, it only display:
Your Phone is up to date.
Current phone software version: 7.0 (7390).
Click to expand...
Click to collapse
How long did yours take to roll back? I am attempting to roll mine back and take the phone back to AT&T because of a constant boot-reboot issue.
And doing a hard reset will just erase your data... it will not roll back your device.

I think my rollback took about 20-25 minutes... sorry I didn't time it.

OTD Razor said:
Not sure. I accidentally did not remember to apply the relock prevention registry edit on my Samsung Focus before I updated to Nodo. As a result my phone became locked again and I lost my ability to sideload.
I restored my phone to the Feb update through Zune, made sure to unlock the phone and apply those registry edits, and reupdated to Nodo. I successfully got my phone back to a dev unlocked state =)
Click to expand...
Click to collapse
OTD Razor, now, if you go in Zune at Settings->Update you still have the option to rollback?
Thanks.

I rolled back at least twice and I still have the option in the Zune software.
Sent from my SGH-i917 using XDA Windows Phone 7 App

OTD Razor said:
I think my rollback took about 20-25 minutes... sorry I didn't time it.
Click to expand...
Click to collapse
My rollback never got past step 2... and I left it running overnight... oh well... back to AT&T I go for a 3rd Focus.

holimon82 said:
Hi,
It seems that the rollback works only once.
So, i installed the NoDo update and the rollback option was in Zune, at Settings->Phone->Update.
I rollback it and after a while put it again, because i got the "an update is available" every time i connected Zune.
This time there is no rollback option on Zune, Settings->Phone->Update page, it only display:
Your Phone is up to date.
Current phone software version: 7.0 (7390).
So i think the only way to roll back now is hard reset(i didn't tried that yet).
It is a feature or a bug?
Click to expand...
Click to collapse
I think this is a bug in the Zune software. When I upgraded from 7.0.7004 to 7.0.7008 I had the same problem. There was no backup. No possibility to restore. When I upgraded to 7.0.7390 (NoDo) a proper backup was created and I do have to possibility to restore. I don't know the exact conditions for failing or succeeding to make a backup.

Plug it in, open zune ->Settings ->Phone ->Update ->Restore/Rollback.

Xerax said:
Plug it in, open zune ->Settings ->Phone ->Update ->Restore/Rollback.
Click to expand...
Click to collapse
The problem is that "Restore/Rollback" is not there
Anyway, i was only curios if i'm the only one with this kind of problem.

Like I said above... I couldn't get mine past step 2.. the reboot phase. Phone had the Samsung boot screen on it all night. Doesn't matter. I took the phone in this morning to AT&T because of the stupid hard reset/reboot issue I was having. New phone is unlocked and loaded with what I need on it. NoDo is a damn snore.

This is Probably A Long Shot...(AT&T SGH-I467)

I've tried searching around here for an answer, but I haven't really been able to find anything solid regarding the issue that I'm experiencing. The other day I popped my sim card into my sgh-i467, as I do from time to time, to check for any OTA updates. This device is usually mounted in my vehicle, so I don't regularly check for updates. Sure enough, an OTA update was available. Tablet was at maximum charge, so I went ahead and chose to do the update. Unfortunately, the update failed at around 93% and went into a boot loop. There was nothing crucial on the device, so I figured it'd be no big deal to just re-flash the firmware if need be. However, I can only seem to find a KIES image for 4.1.2, and while I didn't think to verify exactly what version I was on before the bootloop/brick, I'm fairly certain I was on 4.2.xx.
From what I understand, the bootloader updates with 4.4, correct? With the bootloader getting updated, downgrading to 4.1.2 isn't possible or feasible, right? I didn't think to confirm this before I attempted to flash the KIES image for 4.1.2 via odin (kies never seems to actually see my device), which fails every attempt. I was originally able to get into recovery, but I kept seeing that /system wasn't found. I'm assuming that the OTA update partially installed, before failing, and either corrupted the partition scheme or updated the bootloader but not the system?
I'm dead in the water at this point, and AT&T is obviously no help. Plus, I don't the device on contract with them anyway, so I'm starting to think that my only option is to contact Samsung. However, I really don't want to have to send the unit in, and given it's age, I don't think it's worth investing anything in it if the repair isn't covered somehow. Plus I enjoy tinkering, I'm not new to the scene, and I'd really like to come up with a solution that doesn't require Samsung.
I don't suppose any kind people out there have any suggestions, similar experiences, etc. do they? I'd really like to hear from anyone who's got something to offer! Thanks in advance for your help!

pbrady5 said:
I've tried searching around here for an answer, but I haven't really been able to find anything solid regarding the issue that I'm experiencing. The other day I popped my sim card into my sgh-i467, as I do from time to time, to check for any OTA updates. This device is usually mounted in my vehicle, so I don't regularly check for updates. Sure enough, an OTA update was available. Tablet was at maximum charge, so I went ahead and chose to do the update. Unfortunately, the update failed at around 93% and went into a boot loop. There was nothing crucial on the device, so I figured it'd be no big deal to just re-flash the firmware if need be. However, I can only seem to find a KIES image for 4.1.2, and while I didn't think to verify exactly what version I was on before the bootloop/brick, I'm fairly certain I was on 4.2.xx.
From what I understand, the bootloader updates with 4.4, correct? With the bootloader getting updated, downgrading to 4.1.2 isn't possible or feasible, right? I didn't think to confirm this before I attempted to flash the KIES image for 4.1.2 via odin (kies never seems to actually see my device), which fails every attempt. I was originally able to get into recovery, but I kept seeing that /system wasn't found. I'm assuming that the OTA update partially installed, before failing, and either corrupted the partition scheme or updated the bootloader but not the system?
I'm dead in the water at this point, and AT&T is obviously no help. Plus, I don't the device on contract with them anyway, so I'm starting to think that my only option is to contact Samsung. However, I really don't want to have to send the unit in, and given it's age, I don't think it's worth investing anything in it if the repair isn't covered somehow. Plus I enjoy tinkering, I'm not new to the scene, and I'd really like to come up with a solution that doesn't require Samsung.
I don't suppose any kind people out there have any suggestions, similar experiences, etc. do they? I'd really like to hear from anyone who's got something to offer! Thanks in advance for your help!
Click to expand...
Click to collapse
You need to upgrade to keis 3.0 and reboot, then start kies, then boot note into download mode and have kies detect and reload the update.
Too bad you let the Note update to Kit Kat, Jellybean is better, on the LTE Note.

gooberdude said:
You need to upgrade to keis 3.0 and reboot, then start kies, then boot note into download mode and have kies detect and reload the update.
Too bad you let the Note update to Kit Kat, Jellybean is better, on the LTE Note.
Click to expand...
Click to collapse
Thank you very much for the information! Unfortunately, I've tried Kies 3.0. It notifies me that my device isn't compatible with Kies 3.0. With the other version of Kies, 2.6 maybe(?), it never ends up being able to connect. I've tried manual initialization, but when after I enter my model number, it won't accept my serial.

Take it to a BEST BUY with a Samsung Experience Center (Kiosk (Most all of them in larger cities have them) and they will fix your SGH-i467 for free. I did almost the same exact thing as you (trying to solve a EFS problem) and was stuck. I have posted about it on here before. They will not charge you BUT you may run into a clueless rep now and then. If you do, ask them to call for help and they will get you fixed up in a hurry. Hope this helps.

Samsung note 10+ 5g not booting after firmware update

Hi,
I have applied firware update for years without problems but today I am stumped.
I tried to update todate from 6ETLL firmware to the newer 6FUBD both Android 11.
Set up Odin using 3.14.4 and started ok.
Then I had the install stopping and disconnecing to the phone.
Eventually I disconnected the phone lead and it now wont boot passed the error message -
An error has occurred while updating the device software.
Use the Emmergency recovery function in the Smart Switch PC software.
So I installed this on my pc it it fails to recognise the phone even in Emmergency recovery mode.
I have tried all methods of trying to reboot the phone but it always comes back to the above arror message and wont go into recover mode or download mode.
I did not but this from O2 but directly from Samsund and its just out of warrantee.
I dont know wheer the service center is in the Uk and thats a lst resort anyway.
Any suggestions please.

Repaste from my other reply on the UI3 update :
"
Odin hates thunderbolt - If you plan on using a USB-C port make sure it's not thunderbolt. It will fail half way in and freeze. Get a well rated cable and do it via USB concentrator directly
If you get stuck and you cannot access recovery via key combo or smartswitch emergency recovery use Odin
Open options and select get device info - It will reboot directly to the recovery if it was previously written (check the log). After that disable the get device info option and reconnect the cable (select files for flashing again - should go smoothly.
If after the reboot and setup you get a moisture warning on the USB port - this does not make nay sense but it works - Turn off the Note, plug in a usb cable on the PC and reboot the phone connected to the cable - It will reset the sensor warning and should work flawlessly.
Hope to have helped - Had a bit of a jarring adventure setting this one up this time.
The lag in the animation is there, however, I think it's the animation timer that is set higher (slower) it's not slow "per se" but it shows. "

Bomm,
I must say.... I dont know how to thank you. Your post saved my Note 10.
I emailed Samsung repair and after 2 days they said phone xxxxx if you need it repaired under warrantee.
I waited a week for the phone to lose its battery and when booted back on charge cane up with the same error.
So I went back on xda and you had kindly posted the exact fix I needed. I didn't expect that. I know now if I have the same issue again. It was my pc I think using usb-c to usb-c like you said. Thank you so much.

I didn't get any warnings at all. booted up fine.

Johny1fin said:
I didn't get any warnings at all. booted up fine.
Click to expand...
Click to collapse
had the same issue. I was stumped at first too

I've tried all the posts but when I say start in odin, the phone restarts and gives an error

As you say you are super, my friend, I applied it step by step, the phone entered the download mode.

Not sure why you want Q or above on the 10+.
I'm still running on Pie/One UI. Fast, very stable and zero issues. Last reload was back in June.
If the OS is running well and fulfilling its mission let sleeping dogs lie.

One issue is if we don't keep up to date then at some point Samsung will stop support on a particular phone and the phone can be years out if date.
They may then be on a version unsupported by the apps suppliers and will be more difficult to sell if you want to buy a new phone.

Johny1fin said:
One issue is if we don't keep up to date then at some point Samsung will stop support on a particular phone and the phone can be years out if date.
They may then be on a version unsupported by the apps suppliers and will be more difficult to sell if you want to buy a new phone.
Click to expand...
Click to collapse
No problem here. All my PCs, their XPx64/W7 OSs as well as my Androids Kitkat/Pie OSs are now unsupported.
No issues and all continue to fulfill their missions.
Forced learning curves waste my time and offer little in return. My last learning curves were from Kitkat to Pie and XPx64 to W7.
I stopped updating with the best versions of both MS and Android. I don't rat's arse if it stays like that for the next 10 years... or if my Windows machines mutate into Pie or Linux machines
Whatever works best for me.

It's not just the bugs that won't get fixed it's the vulnerabilities as well, then the apps stop working. I actually enjoy upgrading my kit and amon Windows 10 21h1. Anti virus packages mat stop working as well.

Johny1fin said:
It's not just the bugs that won't get fixed it's the vulnerabilities as well, then the apps stop working. I actually enjoy upgrading my kit and amon Windows 10 21h1. Anti virus packages mat stop working as well.
Click to expand...
Click to collapse
I've never had a malware or virus issue that required a factory reset in over 7 years of using Android. More than half of the time was using out of date OS's. My current Pie OS is over a year out of date.
99% of rootkits, viruses etc are uploaded by the user. There's no protecting the stupid.
I have redundant complete backups so a factory reset will cost me normally 2 hours and at worst case 6-8 hours if I need to restore the SD card.
You waste far more time then this fighting with the bugs, the learning curve and the forced factory reset that a major firmware update requires.
I get to use the OS of my choice... you get whatever they throw at you and the ride that comes with it.