Database Users

[Q] MT3G 1.2 -the process android.process.acore has stopped unexpectedly at startup

Hi,
I have a tmobile mytouch 3g 1.2 (3.5mm jack phone). I tried to root my phone and it failed during the SYSTEM---UnZipping process. (it stuck there forever). I then looked at options of unrooting it. When I apply SAPPIMG.zip it says Main Version Older! Update Fail!
Then I reboot the phone in recovery mode (tried to reset to factory settings and then reboot). The phone gives me the below error upon startup. The only thing i can see is an notification bar.
the process android.process.acore has stopped unexpectedly. "FORCE CLOSE"
Please can someone help me how to get my phone working? Appreciate all your help!

If you go to tmobile.com then go to there forum under android development you will see a topic called how to unroot the mytouch. In that topic they have a link for the original sappimg .. download to your zip cars in the root of the card (no folders) then just boot into hboot and apply the sappimg. I have done it many times so I know it works. Then when you go to root your just us the universal androot method. Feel few to pm me i
ent from my HTC Magic using XDA App

Type this in fastboot:
Code:
fastboot getvar version-main
Then we can try to see if we can update it.
If not, you can always try to flash RUU.
The system starts, that's a good thing -> you have adb access!
Just don't go around and flash all kind of sapphire.nbh/zip...
Wait intil you have the right info :0)

I have had this problem and solved it. I would either get this acore stopped working error or just a loop in the boot screen. I think what caused this is there is not enough internal room for the ROM and gapps. Make sure you wipe everything. Do you have a nandroid backup? Can you get into recovery? Which recovery do you have installed? Do this, make a goldcard. Use fastboot to reroot the phone because you may have halfway unrooted it and made root useless. Boot into recovery and wipe. Install from sd any MyTouch ROM without Gapps. This should get you into the OS and now you can use other methods of getting your phone back. When I got here I used nandroid backup to get my phone back to a date it was when it worked and have had no problems since.

mumilover said:
Type this in fastboot:
Code:
fastboot getvar version-main
Then we can try to see if we can update it.
If not, you can always try to flash RUU.
The system starts, that's a good thing -> you have adb access!
Just don't go around and flash all kind of sapphire.nbh/zip...
Wait intil you have the right info :0)
Click to expand...
Click to collapse
I tried the command - fastboot getvar version-main
it just says < waiting for device > and then nothing happens...
also when i run the adb devices command, it does not display my devices. (But i have the number noted down when i tried to root the phone which failed...) can this number be used in any manner for anything

housry23 said:
I have had this problem and solved it. I would either get this acore stopped working error or just a loop in the boot screen. I think what caused this is there is not enough internal room for the ROM and gapps. Make sure you wipe everything. Do you have a nandroid backup? Can you get into recovery? Which recovery do you have installed? Do this, make a goldcard. Use fastboot to reroot the phone because you may have halfway unrooted it and made root useless. Boot into recovery and wipe. Install from sd any MyTouch ROM without Gapps. This should get you into the OS and now you can use other methods of getting your phone back. When I got here I used nandroid backup to get my phone back to a date it was when it worked and have had no problems since.
Click to expand...
Click to collapse
i did not take any nandroid backup ...i got into revovery boot...but whn i did the wipe clean option and reboot i get this error.
to make a gold card i would need to have the USB debugging enabled right? I am not able to go past the error screen (Home does not work, settings does not work )
and when i run the adb devices command, it does not display my devices. (But i have the number noted down when i tried to root the phone which failed...)
is there any other way to enable the USB Debugging as I am not able to open settings or even see anything on my phone...?
Would there be any option that's something like doing a System Restore to an earlier date on Windows OS on the computer?
please let me know the next steps...appreciate all of your help...

It's driver related.
Fix the drivers and try again to run the commands.

mumilover said:
It's driver related.
Fix the drivers and try again to run the commands.
Click to expand...
Click to collapse
You mean re-install the USB drivers for mytouch 3g? i tried that but still nothing happens...

Well you have to...
In fastboot mode this command shall give you the device nr .
Code:
fastboot devices
If not, the drivers are still bad!
You could also try to do a HARD RESET from hboot ( volume - together with power)...

mumilover said:
Well you have to...
In fastboot mode this command shall give you the device nr .
Code:
fastboot devices
If not, the drivers are still bad!
You could also try to do a HARD RESET from hboot ( volume - together with power)...
Click to expand...
Click to collapse
Thanks for the steps. I got the version details.
by executing the fastboot getvar version-main in fastboot mode.
version-main: 2.53.707.2
finished. total time: 0.001s
What will be the next steps...how to I update?

ganesh.raj.ms said:
Thanks for the steps. I got the version details.
by executing the fastboot getvar version-main in fastboot mode.
version-main: 2.53.707.2
finished. total time: 0.001s
What will be the next steps...how to I update?
Click to expand...
Click to collapse
Hey, i tried the below. can you please let me know if this is correct? and what do i do next?
userdebug-img-14721_1.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.0013
Baseband Version.....: 2.22.23.02
Serial Number........: HT03TPB01582
--------------------------------------------
checking product... FAILED
Device product is 'sapphire'.
Update requires 'trout'.
finished. total time: 0.042s
how do i try to rectify the checking product...FAILED???

OK....
Let's get the facts right.
You tried to root with wrong guide.
The sapphire.zip/nbh image you used if for the 32A.
How do i know that ?
Well the main version nr tells me that you have flashed this:
2.53.707.2 SEA WWE test-signed (from this page: http://forum.xda-developers.com/showthread.php?t=659403)
That's why you have troubles!
The solution....
I need all your fastboot info.. ALL.
Then i can figure out what to do. Or else i will work in the dark...

mumilover said:
OK....
Let's get the facts right.
You tried to root with wrong guide.
The sapphire.zip/nbh image you used if for the 32A.
How do i know that ?
Well the main version nr tells me that you have flashed this:
2.53.707.2 SEA WWE test-signed (from this page: http://forum.xda-developers.com/showthread.php?t=659403)
That's why you have troubles!
The solution....
I need all your fastboot info.. ALL.
Then i can figure out what to do. Or else i will work in the dark...
Click to expand...
Click to collapse
Is it the below that you want?
[FONT=&quot]SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009,22:33:27[/FONT]

Yes...
You have the right radio/spl combo. That's good.
The problem is that your main version is set to high.
If you try to flash any RUU for the 1.2 magic, you will get main-version older error...
Even if you use a goldcard.
Do you still have access to adb?
Even for a little... then we can flash a custom recovery and get the system back.
Even if your system don't start up... as long you can boot more then 20 sec and you don't get reboots.
If not, then we have to flash a 32A sappimg.zip using a goldcard.
From there we flash custom recovery. Then eng spl. Then flash system,boot, userdata. Then flash the 1.2 spl... Then we are done :0)
So it's a long one... but first test if we have adb access.
Code:
adb devices

mumilover said:
Yes...
You have the right radio/spl combo. That's good.
The problem is that your main version is set to high.
If you try to flash any RUU for the 1.2 magic, you will get main-version older error...
Even if you use a goldcard.
Do you still have access to adb?
Even for a little... then we can flash a custom recovery and get the system back.
Even if your system don't start up... as long you can boot more then 20 sec and you don't get reboots.
If not, then we have to flash a 32A sappimg.zip using a goldcard.
From there we flash custom recovery. Then eng spl. Then flash system,boot, userdata. Then flash the 1.2 spl... Then we are done :0)
So it's a long one... but first test if we have adb access.
Code:
adb devices
Click to expand...
Click to collapse
adb devices does not give me anything...its not working

Does the computer recognise the device?
Maybe it's driver related...
PS: check your pm

Accidentally flashed non WWE ROM

Hi Guys,
I'm a little stuck. By accident I flashed: RUU_Ace_HTCCN_CHS_1.75.1400.4_Radio_12.35a.60.140f_26.04.03.30_M_release_162585_signed.exe when I meant to get the WWE version.
When I try install the proper version: RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed I get an ERROR [140]: BOOTLOADER VERSION ERROR.
So I am stuck with a chinese version of android with all these weird looking apps on it. Can anyone put me in the right track here please?

higgo22 said:
Hi Guys,
I'm a little stuck. By accident I flashed: RUU_Ace_HTCCN_CHS_1.75.1400.4_Radio_12.35a.60.140f_26.04.03.30_M_release_162585_signed.exe when I meant to get the WWE version.
When I try install the proper version: RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed I get an ERROR [140]: BOOTLOADER VERSION ERROR.
So I am stuck with a chinese version of android with all these weird looking apps on it. Can anyone put me in the right track here please?
Click to expand...
Click to collapse
I have the same problem, who can help please ?

you guys did a clean flash? rename the rom.zip to PD98IMG.zip then flashed?
try checking if you have radio S-off on the bootloader.
top middle should display if u are SHIP S-ON or SHIP S-OFF
judging by the looks of it you guys are S-ON ;x
i dont know if fastboot or adb works tho... if u can get the 1.32.405.6 rom to flash over then u are safe.
maybe you can try booting to the bootloader and run fastboot flash system system.img ? or maybe flashing the recovery partition manually to clockwork mod?
to do fastboot or adb you need android SDK and java SDK "x86" the x64 giving problems.
please read at development section

i dont know if this would work but give it a try, get the 1.32.405.6 file and find
mainver: 1.32.405.6 on the android_info.txt and change it to 1.75.1400.5 ? ;p then flash? :O

randomdud said:
i dont know if this would work but give it a try, get the 1.32.405.6 file and find
mainver: 1.32.405.6 on the android_info.txt and change it to 1.75.1400.5 ? ;p then flash? :O
Click to expand...
Click to collapse
Unfortunately does not work

randomdud said:
you guys did a clean flash? rename the rom.zip to PD98IMG.zip then flashed?
try checking if you have radio S-off on the bootloader.
top middle should display if u are SHIP S-ON or SHIP S-OFF
judging by the looks of it you guys are S-ON ;x
i dont know if fastboot or adb works tho... if u can get the 1.32.405.6 rom to flash over then u are safe.
maybe you can try booting to the bootloader and run fastboot flash system system.img ? or maybe flashing the recovery partition manually to clockwork mod?
to do fastboot or adb you need android SDK and java SDK "x86" the x64 giving problems.
please read at development section
Click to expand...
Click to collapse
Hi Mate. Yeah I tried a clean flash and it stated the the main rom was older and didn't work. I also tried 1.32.405.6.
I'm trying to flash system.img but it is saying:
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.005s
I'm trying to S-OFF but Visionary doesn't seem to be working with this version. I attempt temproot and I get a black screen after a few moments. Is there any other way I can S-OFF so I can try and install cyanogen or something?

higgo22 said:
Hi Mate. Yeah I tried a clean flash and it stated the the main rom was older and didn't work. I also tried 1.32.405.6.
I'm trying to flash system.img but it is saying:
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.005s
I'm trying to S-OFF but Visionary doesn't seem to be working with this version. I attempt temproot and I get a black screen after a few moments. Is there any other way I can S-OFF so I can try and install cyanogen or something?
Click to expand...
Click to collapse
hmm, maybe try fastboot oem unlock ?

1.75 and 1.72 are unhackable YET!
Sent from my Desire HD

Then I'm stuck with a semi-bricked phone
On this 1.75 Chinese version - I cannot connect to my mobile network or use the google market.
I guess I am stuck waiting for WWE 1.75

You'r right
Sent from my Desire HD

kuceens007 said:
You'r right
Sent from my Desire HD
Click to expand...
Click to collapse
lol seems to be so. was hoping that someone around would know how to change the data on 1.32.405.6 to 1.99.999.9 so at least it would flash over replacing the 1.72 or 1.75 roms lol. then we can manually flash over the 1.72 system.img boot.img and clockwork the su and su.apk for root xD well someone here in xda might know how to do that ;p but that dude just aint me

try this i had to use it once when i flash the last chinese ver 1.60 and visionary was forcing close http://forum.xda-developers.com/showthread.php?t=843014.i have attached 2 files needed you will get the rest from the link.

How to create a update.zip???

Hi im interessted in. How can i flash a rom via the update.zip file??
I have a goldcard, so i can flash every update.zip i want.
Can i just rename the (for example) ''FroyoRider_FeeyoCM61_6.35_34_v2.1.zip'' to update.zip and flash via recovery?

Yes you can and if you've got a custom recovery you don't need the Goldcard to do it. Most recoveries though will recognize the .zip with any filename so you won't need to rename it.

.. yes i know the other method... but i have never found a method to restore the orginal recovery, so i want to keep it.
but the phone dont accept my goldcard or the file... the recovery said. the file isnt signed.

Ahh... good question :0)
You need to know a little about cryptography.
You sign things using cryptography. You can also encrypt things using cryptography. When encrypting, the content get changed to something only the intended receiver can read. When you sign things, the content can be read by everybody. You use the signing to verify that what you read has not been tampered with and actually is from you. So if someone "changes" anything in a signed file, cryptography will guaranty that you will discover that. If anybody else is imposing you, cryptography will show that he/she is fake. How does cryptography work then? This can be done using many methods, but here is what android uses (or a simplified version).
Cryptography is done using 2 distinct keys, public and private keys. Public key is what you "give" to everybody you want to communicate with. Private key is yours, and ONLY yours. If i sign an object with my private keys, then all can verify that this is object is from me by using my public key to check the signature. If you sign an object with the public key, then i can check using my private key, that the object is to me and only me.
So when HTC or who ever makes an update, they sign their software/updates with the private key. The device, here a magic, has the public key and can check the signature and verify that the update is from HTC and nobody else. It can also check if you have changed anything at all. If the update has been tampered with or is not from HTC, then the device will reject the software/update. Simple but effective.
Recovery:
The stock recovery will only accept signed updates by HTC. The custom recovery will accept signed updates, which are signed using google test key, which is freely available. (i'm not sure if it's google or somebody else, but you get the point). Clockwork recovery has an option to disable signature check to let you load any zip-file/update you want. The idea of signing the update.zip/rom.zip is to make sure that who ever made it, knows what he/she is doing. If you e.g. load a rom.zip which fails the signature check, then you know 1 of 2 things:
1) the person did not signed it
or
2) the file has been tampered with since it last was signed.
So if you want to load a file which fails the signature check, then you must re-sign it or disable signature check. But i will investigate WHY is the file failing before i re-sign it and load it.
The goldcard will not help here, since the only purpose it has is to allow you to flash an sapphire.zip which is NOT meant for your device id. It will not magically allow you to run code which is not signed.
Even in fastboot or ruu mode. The sapphire.zip is been checked for signature to make sure it's from HTC and has not been tampered with.
So, NO you cannot take FroyoRider_FeeyoCM61_6.35_34_v2.1.zip and rename it update.zip and try to load it using stock recovery. Unless you sign the files with HTC private keys, which make you a very powerful man and i would like you to contact me :0)
I hope i have shaded some light to your question!
ps: Some of the OLD guides will have you to rename the files like the "FroyoRider_FeeyoCM61_6.35_34_v2.1.zip" to "update.zip" and load it from custom recovery. That's because in the past custom recoveries did not have a "flash zip file" option which will let you choose any file ending with .zip!
That's is what DonJuan692006 is referring to.

Thanks a lot. This is an answer!

mumilover said:
The goldcard will not help here, since the only purpose it has is to allow you to flash an sapphire.zip which is NOT meant for your device id. It will not magically allow you to run code which is not signed.
Even in fastboot or ruu mode. The sapphire.zip is been checked for signature to make sure it's from HTC and has not been tampered with.
Click to expand...
Click to collapse
Let me ask you about the goldcard now: I have a HTC Magic here which currently has an incorrect SPL and radio combo due to a failed official update from HTC Brazil (SPL 1.76.0010 and Radio 3.22.20.17, SAPPHIRE PVT 32A SHIP S-ON H)
I've found in another thread in the xda-developers forums a SAPPIMG.ZIP built by Rogers Canada for their Magics. Looking inside the zip, the android-info.txt file says it's meant for a SAPP50000 model. But my Magic has the model ID SAPP60000... then, when I try to flash it to my phone (using Fastboot commander ), it rejects the file.
I've created a goldcard using another Magic (identical but working OK) that I have here. The messages I get when trying to flash the Rogers zip are these below:
###Calling fastboot with: flash zip C:\android\SAPPIMG_Sapphire_Rogers_WWE_3.54.631.3_R_Radio_63.18.55.06Q_6.35.16.19_release_144134_signed.zip###
sending 'zip' (110447 KB)... OKAY [ 19.522s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 52.576s
The signature error is due to the differences between the model ID of the file and my phone, or have my zip file been modified since signed by Rogers?
Thanks a lot!

yurifranzoni said:
(SPL 1.76.0010 and Radio 3.22.20.17, SAPPHIRE PVT 32A SHIP S-ON H)
###Calling fastboot with: flash zip C:\android\SAPPIMG_Sapphire_Rogers_WWE_3.54.631.3_R_Radio_63.18.55.06Q_6.35.16.19_release_144134_signed.zip###
sending 'zip' (110447 KB)... OKAY [ 19.522s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 52.576s
Click to expand...
Click to collapse
You need to rename it as sappimg.zip (not sappimg.zip.zip) and flash it from hboot mode. It's only there the goldcard will take effect...
But sadly, there is a BIG chance this will fail.
The spl has different partition layout which will make the flash of the radio fail!
What you have to do is to match the spl with the radio, then flash a new spl/radio combo.
In your situation, that's gona be hard... you have perfected spl! Plus any update will start with the radio which is likely to fail....
In other words, you kinda fu*ked.

mumilover said:
You need to rename it as sappimg.zip (not sappimg.zip.zip) and flash it from hboot mode. It's only there the goldcard will take effect...
But sadly, there is a BIG chance this will fail.
The spl has different partition layout which will make the flash of the radio fail!
What you have to do is to match the spl with the radio, then flash a new spl/radio combo.
In your situation, that's gona be hard... you have perfected spl! Plus any update will start with the radio which is likely to fail....
In other words, you kinda fu*ked.
Click to expand...
Click to collapse
mumilover, I've renamed it to sappimg.zip and this is the result:
###Calling fastboot with: flash zip C:\android\SAPPIMG.zip###
sending 'zip' (110447 KB)... OKAY [ 19.516s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 52.567s
I've tried flashing it through Fastboot commander (which is the same thing than typing the commands in the DOS prompt, right?). I expected that it would not work, because, well, I've tried nearly everything I found here in the forums
I'm still trying to find a RUU or HTC signed zip that contains the 1.33 SPL, so it would match the 3.22 radio. Does anyone know where to find something like this? Updating my radio do 6.35 is not an option...
I've reached this situation because of a ****ed brazilian official HTC update to Android 2.1. Before I tried to install it, my phone had CyanogenMod 6.1, with SPL 1.33 and radio 3.22. My mistake was to apply the update directly to the phone, without flashing the new SPL/Radio BEFORE.
During the update, it updated the SPL to the new 1.76 version, but when it starts to update the radio to version 6.35.xx, the phone screen becomes blank, then goes slowly white. I've tried that many and many times, still the same result.
I've tried applying the latest Rogers RUU (available for download in shipped-roms.com), which has similar SPL and Radio versions than the brazilian update, but no luck: even with the goldcard inserted, when it reaches the radio flash phase, the screen blanks again
Is there anything that could be done before sending my brick to service? They are replacing the logic board of every phone they receive in this situation - believe me, they have received many of them... I know a bunch of people that made the very same mistake as I did.
Thanks!!!

Again... as i wrote earlier, this has to done in hboot mode (volume - & power) with a goldcard.
You CANNOT do this with fastboot commands!
And yaa, i told you that you were screwed. Very bad combo which seriously messes with the your ability to fix it.

Right... my mistake, I forgot to mention that my brick does not boot in hboot mode anymore. It keeps stuck at the RUU USB screen, with the icon of the microchip and the red cross sign at the bottom.
Worse, it does not have the custom recovery anymore, so I'm not able to go there and do a "flash zip from sdcard".
Finally, if I try to do a "fastboot boot recovery.img", using any custom recovery image, what I get is a eternal "booting..." message, and the phone does not load the custom recovery image.
Any other ideas?
Thanks again!

GOOD NEWS!!
I've managed to FINALLY make it boot the system! I don't know why, but I tried the following and it restarted in CM 6.1 (the ROM installed before I tried to apply the official update):
- with the phone turned on, connected via USB and froze at the RUU USB screen, type the following in a command prompt:
fastboot oem boot
It will display a lot of data and then the PC screen will show FAILED (status read failed (Too many links))
- Then, I typed:
fastboot boot recovery-RA-sapphire-v1.7.0H.img
It told me "(waiting for device)". I left it there....
- Then, I fired up the Radio Switcher app and chose the "Shutdown device" option. My idea was to turn the brick off to try anything else...
BUT it took about 20 seconds and RESTARTED, then the CM logo shown up... and some seconds later it was RUNNING CM 6.1 again! Like it was before I tried to update!
I still can't reboot into recovery to flash the right SPL version, but that's a chance of success, isn't it? It still has the bad SPL/radio combo, but at least, it's starting!
How can I flash the right SPL into the phone WITHOUT restarting into fastboot or recovery? Is it possible?
Thanks!

HTC Magic - half bricked - RUU USB

Hello,
can anyone suggest how to recover HTC magic after flashing Rogers RUU official over custom rom.
ROM update was aborted on updating system partition.
Problem is that I can't upload any part of rom because phone is now S-ON. I'am getting signature error.
Flashed RUU: 42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP format]
ADB is no longer possible. Only FASTBOOT and RUU USB.
See attched photo for fastboot details.
Thanks in advance.

pero256 said:
Hello,
can anyone suggest how to recover HTC magic after flashing Rogers RUU official over custom rom.
ROM update was aborted on updating system partition.
Problem is that I can't upload any part of rom because phone is now S-ON. I'am getting signature error.
Flashed RUU: 42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP format]
ADB is no longer possible. Only FASTBOOT and RUU USB.
See attched photo for fastboot details.
Thanks in advance.
Click to expand...
Click to collapse
I went through a similar problem. My 32A was in the same state except for the radio; I had no system installed, S-ON, RUU mode, and a radio/spl mismatch. It looks like you at least have a proper radio/spl combo.
Before we do anything else, try flashing the RUU again. Were you using the ZIP file or the EXE? Use the ZIP, at least you won't have to load up that crappy HTC interface.
If the RUU fails again, see if you can find the log file from the installation. It'll be on your system's drive, probably in "C:\ruu_log" or something like that. It can tell us what error it found.
In my case, we (mumilover and I) had to upgrade HBOOT and "sort of unlock it" using HTCDEV's method. Then we were able to install a custom recovery, and then everything got very easy.
Let's see if the simple things work before we have to do the harder things

Thnak you very much for hint with HTCDEV. Now I have at least fastboot
RUU image allways fail at signature error. OI have tried three of them. Same error.
I have run RUU under fastboot usb.
Also I can't flash recovery image even I have successfully unlocked hboot with htcdev.
C:\ADB>fastboot flash recovery recovery-clockwork-2.5.0.7-magic.img
sending 'recovery' (2642 KB)... OKAY [ 0.923s]
writing 'recovery'... FAILED (remote: not allow)
finished. total time: 0.926s
Any other idea ?

pero256 said:
Thnak you very much for hint with HTCDEV. Now I have at least fastboot
RUU image allways fail at signature error. OI have tried three of them. Same error.
I have run RUU under fastboot usb.
Also I can't flash recovery image even I have successfully unlocked hboot with htcdev.
C:\ADB>fastboot flash recovery recovery-clockwork-2.5.0.7-magic.img
sending 'recovery' (2642 KB)... OKAY [ 0.923s]
writing 'recovery'... FAILED (remote: not allow)
finished. total time: 0.926s
Any other idea ?
Click to expand...
Click to collapse
Could you give me the new details of the fastboot page? Your HBOOT version will have changed, and it will say "UNLOCKED" or "RELOCKED" at the top and S-ON. If it says "RELOCKED", try running the HTCDEV unlock command from fastboot again (you should still have the Unlock_code.bin file in your email) and then reboot.
Let's see how that goes.

DasBub said:
Could you give me the new details of the fastboot page? Your HBOOT version will have changed, and it will say "UNLOCKED" or "RELOCKED" at the top and S-ON. If it says "RELOCKED", try running the HTCDEV unlock command from fastboot again (you should still have the Unlock_code.bin file in your email) and then reboot.
Let's see how that goes.
Click to expand...
Click to collapse
I have attached Fastboot details.Status is: UNLOCKED.
But when I try to flash recovery I get an error message which I already wrote.
I think it is because of S-ON which is checking signature.

pero256 said:
I have attached Fastboot details.Status is: UNLOCKED.
But when I try to flash recovery I get an error message which I already wrote.
I think it is because of S-ON which is checking signature.
Click to expand...
Click to collapse
Sounds reasonable. I wish I kept better notes That way I wouldn't have to re-learn things every time.
I just want to make sure I understand the timeline of events:
You said you tried to flash an RUU over an existing custom ROM install, right?
What was the configuration of your phone before you tried the RUU and ran into trouble? If you were running a custom ROM, did you have a magic SPL or a custom recovery in order to install that custom ROM?
Anyway, on to the work:
Let's see if we can get an RUU to work now.
Go to the command prompt and run "fastboot getvar version-main" and let us know what it is, for future reference.
Once we know that, we can find a higher-numbered RUU from this list of Official RUUs.
I think I ended up using BrightStar Brazil, but anything higher than your phone's reported main version should work.
Have you made a goldcard? If you try to use an RUU and it complains about your CID, this will help.
Before you try to install an RUU, you will need to relock the bootloader using "fastboot oem lock" (you'll be able to unlock it again using the Unlock_token.bin)
Place the SAPPIMG.zip of the RUU in the root folder of your SD card and reboot into HBOOT (or reboot to fastboot and select HBOOT).
After a few seconds it should start scanning your SD card and then it will try to use the SAPPIMG.
Let us know.

Yes I had custom rom with s-off. But can't remeber which version.
Than I tried to install RUU: 42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP format]
Than I get error while flashing.
Strange thing is that I get this now:
C:\ADB>fastboot getvar version-main
version-main: 3.54.0.0
finished. total time: 0.001s
So it seems that I have lower version than I tried to install
I didn't try to use goldcard for now.

I have created Gold Card using this link: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
I have to use another HTC phone (Wildfire) to get CID from HTC Magic SD card
I have tried to put 3.54.631.3 Rogers Canada rom as SAPPIMG.zip but HBOOT claims that there is no image.
I get: Loading...(SAPPIMG.zip) No image!

I forget to say that I have set HBOOT to RELOCKED state before using GOLD CARD and SAPPIMG.zip

pero256 said:
I forget to say that I have set HBOOT to RELOCKED state before using GOLD CARD and SAPPIMG.zip
Click to expand...
Click to collapse
1) Check the filename. Make sure it is "SAPPIMG.zip" exactly, with SAPPIMG in capital letters.
2) Run these fastboot commands and then switch back to HBOOT mode.
Code:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
This procedure has fixed SD card problems in the past.
3) Check the SD card using a computer or another phone to be sure that the file is on the card. I've had Windows unmount the card improperly a few times, so that's a possibility.
4) Compare a checksum of the original ZIP file to the checksum of the ZIP on your SD card. I use 7-Zip to get the checksum, but there are other ways.
5) You can download another copy of the SAPPIMG.zip file.
It also helps to wave a dead chicken over the phone as an offering to the phone god.

Unfortuntly can't get goldcard to work.
I have used 3 different SD card.
1. 2GB
2. 2GB
3. 1GB
Non of them works.
Also everything is fine in the process of creating them.
Problem is about loading to phone SAPPIMG.zip of 3.54.631.3 Rogers Canada rom.
Phone starts to Checking..(SAPPIMG.zip) and then after some period of time stops and waits to press:
1. (back) FastBoot Mode
2. (send) Simlock
I have try to start another flash but get the same result.
So it seems that the gold card is not working as it should because phone is still checking uploaded rom image.

Is there some SD card that works 100% ?

pero256 said:
你好，
任何人都可以建议如何在通过自定义 rom 刷新 Rogers RUU 官方后恢复 HTC 魔法。
ROM 更新在更新系统分区时中止。
问题是我无法上传 rom 的任何部分，因为手机现在是 S-ON。我收到签名错误。
闪烁的 RUU：42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP 格式]
亚行不再可能。只有 FASTBOOT 和 RUU USB。
有关快速启动的详细信息，请参阅随附的照片。
提前致谢。
Click to expand...
Click to collapse
You use what method to let it enter FASTBOOT

[FIRMWARE] Stock AT&T 1.32.502.31 RUU

Directly from the HTC Website:
http://www.htc.com/us/support/htc-one-m9-att/news/
PLEASE BE SURE TO READ THE POST FIRST. THIS FIRMWARE WILL WIPE YOUR PHONE.
Direct link to download full RUU file here:
http://dl3.htc.com/application/RUU_...21_62.05.50320G_F_release_426950_signed_2.exe
UPDATE 4/23/15
Converted firmware update files in .zip format for other platforms courtesy of clsA to be found in post 7
clsA said:
RUU_HIMA_UL_L50_SENSE70_ATT_Cingular_US_1.32.502.3 1.rom.zip
htc_fastboot.exe >> https://www.androidfilehost.com/?fid=96042739161891970
fastboot-mac.zip >> https://www.androidfilehost.com/?fid=96042739161891971
I have not tested the fastboot-mac so I'm not sure it works with the above Ruu or not
Flash with
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip
htc_fastboot flash zip RUU.zip <this may not be needed it might restart on it's own>
htc_fastboot reboot
Click to expand...
Click to collapse

I can confirm that the RUU downloaded from the HTC site (link above) at 2.1G works correctly.
You will NOT lose Unlock or S-off if you have done so already. However, the process WILL wipe your system, so you will need to reinstall TWRP 2.8.6.4 (unofficial), SuperSU beta and any custom ROM you want.
Have at it!

BillTheCat said:
I can confirm that the RUU downloaded from the HTC site (link above) at 2.1G works correctly.
You will NOT lose Unlock or S-off if you have done so already. However, the process WILL wipe your system, so you will need to reinstall TWRP 2.8.6.4 (unofficial), SuperSU beta and any custom ROM you want.
Have at it!
Click to expand...
Click to collapse
Hey, so right now I'm still running Sense. I understand that this will remove root and the custom recovery but will this also reset the device back to factory default settings and data? I know, dumb question, but I just want to make sure I'm able to keep all my messages, apps, data, ect. If not, then I'll just make a backup with HTC sync manager.
Thanks

anbrine said:
I just want to make sure I'm able to keep all my messages, apps, data, ect. If not, then I'll just make a backup with HTC sync manager.
Click to expand...
Click to collapse
Nope. They'll get blown away. You should ALWAYS have a backup saved to your PC.

BillTheCat said:
Directly from the HTC Website:
http://www.htc.com/us/support/htc-one-m9-att/news/
PLEASE BE SURE TO READ THE POST FIRST. THIS FIRMWARE WILL WIPE YOUR PHONE.
Direct link to download file here:
http://dl3.htc.com/application/RUU_...21_62.05.50320G_F_release_426950_signed_2.exe
Click to expand...
Click to collapse
are you going to upload the rom.zip from the RUU and the htc_fastboot for MAC and Linux users ? If not I'll add them to my thread

clsA said:
are you going to upload the rom.zip from the RUU and the htc_fastboot for MAC and Linux users ? If not I'll add them to my thread
Click to expand...
Click to collapse
I have no clue how to do that. I was hoping someone else would. If you're able, I'll NE happy to update my op with the corresponding links.

BillTheCat said:
I have no clue how to do that. I was hoping someone else would. If you're able, I'll NE happy to update my op with the corresponding links.
Click to expand...
Click to collapse
I'm uploading them now ..I'll post here
RUU_HIMA_UL_L50_SENSE70_ATT_Cingular_US_1.32.502.31.rom.zip
htc_fastboot.exe >> https://www.androidfilehost.com/?fid=96042739161891970
fastboot-mac.zip >> https://www.androidfilehost.com/?fid=96042739161891971
I have not tested the fastboot-mac so I'm not sure it works with the above Ruu or not
Flash with
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip
htc_fastboot flash zip RUU.zip <this may not be needed it might restart on it's own>
htc_fastboot reboot
The other method to flash is to rename the RUU.zip to 0PJAIMG.zip and copy it to a fat32 sdcard and flash it in download mode

clsA said:
I'm uploading them now ..I'll post here
Click to expand...
Click to collapse
Works for me, or you could pm the links and I'll credit you in the 1st post.

Anyone has instruction to decrypt the ROM.zip on windows ?

yardi4life said:
Anyone has instruction to decrypt the ROM.zip on windows ?
Click to expand...
Click to collapse
sure do >> http://forum.xda-developers.com/one-m9/development/dev-how-to-extract-one-m9-rom-dump-image-t3062808

Stuck with 155 errors on the .exe RUU Utility from HTC. clsA, i tried the manual update using htc_fastboot zip RUU.zip and getting a FAILdata too large error.
Now I'm stuck locked and can't update or unlock my current version. Any ideas?

gnomish said:
Stuck with 155 errors on the .exe RUU Utility from HTC. clsA, i tried the manual update using htc_fastboot zip RUU.zip and getting a FAILdata too large error.
Now I'm stuck locked and can't update or unlock my current version. Any ideas?
Click to expand...
Click to collapse
are you sure you are doing it right and using htc_fastboot? Make sure you are not using fastboot or any mac ver of fastboot. You must be in download mode
htc_fastboot.exe oem rebootRUU
htc_fastboot.exe flash zip ruu.zip
htc_fastboot.exe flash zip ruu.zip
htc_fastboot.exe reboot
I have confirmed this working on my at&t m9
or if you have a 32gig or smaller sd card, rename file to 0PJAIMG.ZIP and put it in the root of your sd card and go to download mode, MUST be formatted in fat32 from a computer first.
btw for the op, I have confirmed the fastboot-mac nor fastboot for mac work with this. They have to be decrypted in order for it to work with plain old mac fastboot. It was like this on m7 and m8 too. wish someone would port the htc_fastboot to mac then I could take off this darn parallels

Yes, unfortunately can confirm I followed the above steps and am using htc_fastboot.exe. I continue to get the same error below.
I will continue trying as I don't have a small enough sd card for the other method.
C:\adb>htc_fastboot.exe flash zip ruu.zip
sending 'zip'... (2141801 KB) FAILdata too large, 2193204239 > 1430073344
FAILED (data size is too large(2141801 KB) for device to download ZIP file 'ruu.
zip'
Click to expand...
Click to collapse

gnomish said:
Yes, unfortunately can confirm I followed the above steps and am using htc_fastboot.exe. I continue to get the same error below.
I will continue trying as I don't have a small enough sd card for the other method.
Click to expand...
Click to collapse
This is the htc_fastboot from the AT&T RUU
https://www.androidfilehost.com/?fid=96042739161891970
If you using a different one try that one
Are you md5 checking your download ? are you starting the flash in download mode (black screen not the white bootloader)
try it without the htc_fastboot oem rebootRUU
just boot to download mode and flash it
fastboot flash zip RUU.zip
if the phone reboots during the process hold volume down to enter download mode again and let it finish