Related
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.
hi to all!
I am writing to you because I have a problem, I followed the tutorial to the letter relocker the bootloader, once done, I have a message "security warning" that appears below "relocked ".
I reboot bootloader the message disappears, so I launch the RUU SFR and there it gets complicated, "error 140" problem with the bootloader! I cracked it's almost 2:00 I looking for a solution, but nothing works, I can not even unlock this one - 'over the phone does not even load connected to the PC and can not access the recovery...
this is to install the ROM Maximus JB
Please help me!!
(translated with google)
srtdesign said:
hi to all!
I am writing to you because I have a problem, I followed the tutorial to the letter relocker the bootloader, once done, I have a message "security warning" that appears below "relocked ".
I reboot bootloader the message disappears, so I launch the RUU SFR and there it gets complicated, "error 140" problem with the bootloader! I cracked it's almost 2:00 I looking for a solution, but nothing works, I can not even unlock this one - 'over the phone does not even load connected to the PC and can not access the recovery...
this is to install the ROM Maximus JB
Please help me!!
(translated with google)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1920546&page=2
Help.
I need help unlocking my bootloader, I can type adb devices while the device is powered on & my unique I.D number comes up in cmd, but whenever I boot into bootloader, the device doesn't come up in cmd what gives? All my drivers are up to date & installed correctly, though I get an MTP driver issue, could that be causing this? This is my second M8 (T-Mobile this time), first one was the dev edition s-off & converted to GPe.
You never said what command you used in the bootloader ?
It's :
Fastboot devices (not adb devices)
adb devices for adb wile phone is booted in OS
fastboot devices in fastboot/hboot mode
Oops never mind, another thing - I keep getting an error while trying to submit my code to HTC Dev after getting the identifier token.
EternalAndroid said:
Oops never mind, another thing - I keep getting an error while trying to submit my code to HTC Dev after getting the identifier token.
Click to expand...
Click to collapse
Please state the error if you would [emoji12]
After reading the opening post here, I get the impression that the code you get for the token is more an issue on your side(You messed up somewhere).
That being said, it doesn't help alot saying "I keep getting an error" but you don't tell us what the error is.
Taking a wild guess, it has to do with the actual token. Make sure you don't have any spaces in the selection of the code. Select it with the <<<<< >>>>> included. Do NOT include the <bootloader> parts next to it and again make sure there are NO spaces in the selection.
Comparison pictures of the code how it SHOULD and SHOULD NOT look.
If that is not your problem then give more information as to the error you're receiving. Doesn't help to phone an IT dept for help and you don't tell them what the problem is either, does it? Same here...
jball said:
Please state the error if you would [emoji12]
Click to expand...
Click to collapse
Sorry guys just frustrated & keep forgetting, "error reason token decryption fail (cannot generate result)."
But I think I figured out my issue, so my computer's internet is off right now & I'm trying to do all this from my N5. I'm typing the code on my phone, reading it letter for letter, number for number.
BerndM14 said:
After reading the opening post here, I get the impression that the code you get for the token is more an issue on your side(You messed up somewhere).
That being said, it doesn't help alot saying "I keep getting an error" but you don't tell us what the error is.
Taking a wild guess, it has to do with the actual token. Make sure you don't have any spaces in the selection of the code. Select it with the <<<<< >>>>> included. Do NOT include the <bootloader> parts next to it and again make sure there are NO spaces in the selection.
Comparison pictures of the code how it SHOULD and SHOULD NOT look.
If that is not your problem then give more information as to the error you're receiving. Doesn't help to phone an IT dept for help and you don't tell them what the problem is either, does it? Same here...
Click to expand...
Click to collapse
Oh wow I see
Copy the text to notepad. Copy it to your phone. Open it in your phone using any file manager. Copy and paste .
i am using htc desire 820s when i tried to unlock bootlader the htc dev website displaying error 152
i tried whole process several times but its not working
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 152.
Error Reason: Token Information not complete (CID)
please help me how can i fix this
HTC One M9
Android 6
Bootloader Locked
S=On
USB debugging disable
today I found my phone stock on decryption screen! I did not enable encryption mode. now my phone says: your phone is encrypted. to decrypt your phone, enter your Screen lock password.
it does not matter what number I enter! every number I enter, it says: Decryption unsuccessful. the password you entered is correct, but unfortunately, your data is corrupt. to resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
But nothing happened when I press the "reset phone" button. I waited 4 hours but it remains on a window named "Factory data reset, Rebooting..." but it can not proceed to reboot.
when I power off and go to bootloader, I can not go to recovery mode. on recovery mode, there is only a triangle with a red exclamation mark.
I download a stock ROM so I can flash it to my phone from download mode, but at the beginning of flashing process it comes with this error
12 RU_ZIP_ERROR
please help me
sjmahmoudi said:
HTC One M9
Android 6
Bootloader Locked
S=On
USB debugging disable
today I found my phone stock on decryption screen! I did not enable encryption mode. now my phone says: your phone is encrypted. to decrypt your phone, enter your Screen lock password.
it does not matter what number I enter! every number I enter, it says: Decryption unsuccessful. the password you entered is correct, but unfortunately, your data is corrupt. to resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
But nothing happened when I press the "reset phone" button. I waited 4 hours but it remains on a window named "Factory data reset, Rebooting..." but it can not proceed to reboot.
when I power off and go to bootloader, I can not go to recovery mode. on recovery mode, there is only a triangle with a red exclamation mark.
I download a stock ROM so I can flash it to my phone from download mode, but at the beginning of flashing process it comes with this error
12 RU_ZIP_ERROR
please help me
Click to expand...
Click to collapse
This problem has been posted from time to time by other users - it often indicates a corrupt chip in the motherboard.
Depending on your SKU and whether or not there really is a hardware issue or not, it may be possible to apply a RUU, which would effectively restore your phone to factory state (though it will wipe your internal memory).
Please post your OS version, which will help us determine your phone's SKU.
If you put the phone in download mode and plug it into a pc then run fastboot.exe with the cli command 'fastboot getvar all' you will get a lot of important information.
If you are absolutely sure your phone has never been modified and it shows on the fastboot output "status modified" then you can assume your phone has hardbricked from a faulty nand. Only HTC can fix it in the case.
Beamed in by telepathy.
computerslayer said:
this problem has been posted from time to time by other users - it often indicates a corrupt chip in the motherboard.
Depending on your sku and whether or not there really is a hardware issue or not, it may be possible to apply a ruu, which would effectively restore your phone to factory state (though it will wipe your internal memory).
Please post your os version, which will help us determine your phone's sku.
Click to expand...
Click to collapse
os: 3.35.401.32
shivadow said:
If you put the phone in download mode and plug it into a pc then run fastboot.exe with the cli command 'fastboot getvar all' you will get a lot of important information.
If you are absolutely sure your phone has never been modified and it shows on the fastboot output "status modified" then you can assume your phone has hardbricked from a faulty nand. Only HTC can fix it in the case.
Beamed in by telepathy.
Click to expand...
Click to collapse
I rooted this phone when I first bought it. but 4 months ago I unroot it so I could update it's android to marshmallow. after unrooting, i receive the android update and everything was as normal as a fresh unrooted phone.
I was able to go to download mode when first my phone faced this problem. but now the download mode is not available
it says: failed to boot to download mode
press volume up or down to back to menu
this build is for
development purposes only
do not distribute outside of HTC
without HTC's written permission.
Failure to comply may
lead to legal action.
computerslayer said:
This problem has been posted from time to time by other users - it often indicates a corrupt chip in the motherboard.
Depending on your SKU and whether or not there really is a hardware issue or not, it may be possible to apply an RUU, which would effectively restore your phone to factory state (though it will wipe your internal memory).
Please post your OS version, which will help us determine your phone's SKU.
Click to expand...
Click to collapse
I took my m9 to HTC service center. he said that main chip must be replaced. after replacing the chip, he said that I need a dump.bin file and I do not have it. now after 3 months, my dear m9 is still on the service center . I search all over the net for the dump.bin file but there is nothing at all.
I do not even know what the hell is the dump.bin file. he said that your phone can boot but it will not have antenna without relevant dump file. I'm confused please help me
my phone model ID: 0PJA100
Did you give your phone to an official HTC service center? HTC should have the needed file so the fact that you should provide it to the service center confuses me a bit.
It's impossible to get that file (from a working phone) without a JTAG device and I doubt that many M9 owners have one since they're quite expensive. Sorry for the bad news.