I upgraded my 85' with the "official" wm6 rom and now I cannot go to other roms. The process was solid, meaning I was fully charged, no power loss, and it was synced. I've tried every version of rom available and get the same results. I went through the "brick" thread and I'm affraid I don't quite fit into any category. I can get phone calls and everything works, I just happen to like all of the great ROM's everybody is cooking and want to try them to see which one I favor. I tried using the Hard-SPL and all of the other bootloaders out there and I always get that ERROR [206]. I've tried to restart the machine, and hard reset the 85'. Any good idea's.... Maybe I need to search more? I'll try that.
==============================================================================
UPDATE:
What I should really do is rent a gun, and buy a bullet...
I'm not saying I'm some sort of season veteran of flashing... but I've never had to touch anything after I accept all terms. For some reason, when it came down to the last "Next" form, my phone flashes "Accept" super fast. So what to do?... I push "Yes" soft key fast as I can and it runs like grease lightening... I had to choose SS for the boot loader because it couldn't figure it out... Maybe next time around.
Have you tried to flash a coocked ROM using the microSD card?
Hi,
did you try get your phone in the tri color bootloader screen and then running the Hard SPL program again?
I did not try to do flash it woth the MicroSD card... I just found out that I could flash it with the MicroSD card about 2 seconds ago. And I wanted to Hard-SPL at the tri-color as a last result in fear of bricking but everything is okay now. As I said before, I've never had to touch my 85' while flashing the rom, it just did it on it's own, but that "official" rom was not about being neglected. And then when I saw it flash something and say "yes", I pushed it and never looked back. It's alllllllllllllllllll good.
I do have one question, is the SSPL preferred over the other choices? Or is there one that is recommended?
Hi joshkrajnak,
How did you solve this problem exactly cos I dont understand what your saying:
http://forum.xda-developers.com/showthread.php?t=298640
boz said:
I extracted these error codes from a Hermes rom upgrade 'read me' document, these should be of help if you get an error message during a rom upgrade. They should be common to all roms, please correct me if I am wrong.
ERROR [202, 204] : CONNECTION
This error message will appear when the device is not connected to ActiveSync correctly. Make sure you properly connect the device to the PC through ActiveSync before running RUU.
ERROR [260] : CONNECTION
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
ERROR [206] : MEMORY ALLOCATION
ERROR [280] : UPDATE ERROR
When you see any of these error messages, close other running programs on the computer and run RUU again.
ERROR [208] : FILE OPEN
ERROR [210] : FILE READ
These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.
ERROR [212] : FILE CREATE
ERROR [214] : FILE WRITE
ERROR [222, 224] : DEVICE NOT RESPONDING
These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.
ERROR [220] : MAIN BATTERY POWER
This error message will appear when the device’s battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery when it is upgrading the radio).
ERROR [238] : FILE READ
This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again.
ERROR [240] : FILE OPEN
When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.
ERROR [242] : INVALID LANGUAGE
ERROR [244] : INVALID MODEL ID
ERROR [294] : INVALID VENDER ID
ERROR [296] : UPGRADE ONLY
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
ERROR [246] : DEVICE NOT RESPONDING
This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.
ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
ERROR [300] : INVALID UPDATE TOOL
This error message will appear when you use the incorrect RUU version to upgrade.
ERROR [330] : ROM IMAGE ERROR
This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.
Click to expand...
Click to collapse
To Clarify: Whenever I went to upgrade my 85' to a different ROM, it wouldn't recognize my bootloader, and then after selecting any of the options, it would give the "ERROR [206]" message and fail miserably with any rom.
What I did to correct it was this: On the "official release" whenever I went to upgrade the ROM, the 85' would show a message at the bottom, the same as any "Notification" would giving me the option to either "confirm" or "dismiss". I did not notice the messages up until it caught my attention out of the corner of my eye on the very last attempt. The messages would quickly appear and disappear, so when the time came and it stated:
Current Rom: 3.25.###.###
Upgrade: 1.##.###
I had to press a confirm notification to continue on or I would get the "206" error message. The quote posted by Binyo is correct, but it does not apply in my situation.
ERROR [206] : MEMORY ALLOCATION
ERROR [280] : UPDATE ERROR
When you see any of these error messages, close other running programs on the computer and run RUU again.
Although that may be true that some applications may interfere with the upgrade process, I had turned off all applications and killed any services during this process.
Hello everybody,
I just got a Samsung Nexus 9250 phone. I came to this forum to look for tutorials, tips, etc. I'm sure I will find a lot of interesting information around here.
After a few minutes using the device, I noticed that it had never detected my SIM card . My card works perfectly in my older phone. I tried with other people's cards and it happens the same. I have not been asked to input my pin code in any case. There is no message where I am asked to insert a SIM card.
This phone has never been manipulated (no jailbreak, unlock, etc). Then I tried with a hard reset, no. The "plane mode" is not activated.
If I search for available mobile networks / network operators, the phone finds the common ones. But if I try to choose one I get the message : "Unable to connect to this network at this time. Please try again later".
Other features (wifi, etc) seem to work OK. Except that I can't find any icon to use some kind of Android Market / Google Play.
Anyway my priority right now is to make the SIM card work.
So the question is : any ideas about how to make it work? Except, of course, some kind of hardware malfunction in the card reader.
Android version is 4.0.1.
Model number : GT-I9250_EUR_XX
Thanks in advance.
It is hard to believe, but it got fixed when I updated the firmware.
At the begining I tried with the tutorial in this thread :
(4.0.4 Unofficial Changelog *Update2 02/05*)
http://forum.xda-developers.com/showthread.php?t=1481044
But somehow my terminal did not like that version. I got some errors like :
-------------------------------
1.-
assert failed: file_getprop(”......
-------------------------------
2.-
- Install / sdcard …
Finding update package …
Opening update package …
Verifyng update package …
E: signature failed to verify wholefile
E: signature verification failed
Installation aborted.
-------------------------------
Which some people seem to have too.
Never mind, I could upgrade "only" to 4.0.2 and it worked like a charm. I suppose I will wait for 4.0.4 to be available globally.
Thank you very much to the community. You did not answer my question, but there is a lot of useful information out there.
I succesfully rooted MM but I cannot get rid of the "Your device has failed verification and may not work propperly" warning screen when booting, is there a .img file I missed flashing?
Another reason not to install MM !
As it said in the rooting guide you used, it will do that. And just ignore. Its the price we pay to be early adopters.
When you modify some system files in stock MM like rooting or unlocking, that warning message will appear each time you boot your phone. It's normal, just ignore it
Its nothing to worry about, it's the new bootloader's security warning feature. didn't you vist http://g.co/abh its self explanatory if you changed the system software yourself, then you have nothing to worry about.
is there any way to remove this advertising ?
It seems this is the only message I found across google search for my device Asus Zoom ZX551ML.
Just installed a modified ROM and getting the same message.
Device verification failed on boot.. Everything is stable and working fine.
I know i should put more info here but im out of town for work so hopefully someone can help. My 10 rebooted today and gave this error message: Reboot Reason: 0x776655aa, Reboot message: RPM:APPS NS-WD! ... Any ideas? No, i don't have a log, yet. I'll get one this weekend when I'm home. Thanks.
So i`ve been running back and forth with the issue of not having signal to use for calls and that stuff in my Samsung a225m.And now i ran into a problem with a message popping up everytime i start my phone that states as follow "simcard mode has changed, it changed from single sim to dual sim.To apply this setting restart your phone..." and i restart several times but the message doesnt dissapear and i cant use the cellphone.
I bought this cellphone used and rooted with magisk to a android 11 custom rom, and around the time i bought it, cellphone`s signal lasted a few days before not working.
Now the main issue is the fact that i cant use the phone, but further into it i dont have internet signal.
Note: the last thing i applied to my phone before this error message started to appear, was flashing via Odin (only method used by me) a file to fix efs corrupted taken from @regalstreak.