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!

[Q] Phone will not boot up

I hate to do this but I this is my last resort to getting my phone back working. I currently can not get pass splash screen. Phone was already rooted running cm7 and I wanted to go back to one of my old nandroid so I flashed CW 2.5.1.2. It was working fine but was running slow so I did a data format and wipe cache and ever since then it will not boot up. I am getting a E:Cant' mount CACHE:recovery/command and log message when recovery loads up.
I can get into fastboot and recovery fine but I cant seem to flash any of my nandroids anymore. I have about 5 of them and none work. I can't flash any roms either. It seems as if my root may be gone because when Im in adb shell and run su it does not give me root and I cannot mount any systems in recovery. I tried everything from trying to flash to stock through hboot and even flashing new recovery in fastboot but that did not work since I do not have ENG HBOOT. Tried rerooting and unrooting it again but I always have to go into that /data/local but I am never able to gain access. I do still have S-OFF but that seems to be about it. Oh yeah and I cant even do a wipe data/factory reset. Says E:format_root device: can't find mmc partition.
So if someone knows anything else I could try to get this resolve that would be cool.

Ok lets start don't panic all is not lost yet you can still have root with S-OFF and have access fastboot and recovery. I am not sure why you reverted back to older CWMR2.5.1.2 as if you had CWMR3.0.0.6 you could have done it without fastboot but makes no diff now.
First go try "fastboot erase system -w" and then boot in to recovery and do full factory wipe and then flash as you normally would do.

BlackSHELF said:
Ok lets start don't panic all is not lost yet you can still have root with S-OFF and have access fastboot and recovery. I am not sure why you reverted back to older CWMR2.5.1.2 as if you had CWMR3.0.0.6 you could have done it without fastboot but makes no diff now.
First go try "fastboot erase system -w" and then boot in to recovery and do full factory wipe and then flash as you normally would do.
Click to expand...
Click to collapse
I reverted back to that one thinking that it would enable me to flash a none cm7 rom.
Here is what I got. From my understanding I am getting this because I do not have ENG HBOOT but please correct me if Im wrong
C:\android-sdk-windows\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.020s

Hmmm I just reread your OP and you saying you somehow lost root trying to unroot and reroot, so I am not sure about the current status.
NOMRAL CASE:
http://forum.xda-developers.com/attachment.php?attachmentid=516463&d=1297577207
^ download that and unzip it and get the recovery.img for 3.0.0.6 and try "fastboot flash recovery recovery.img" as that would do if not try the below.
EXTREME CASE:
http://www.filefactory.com/file/caa....140e_26.03.02.26_M_release_155771_signed.zip
File: PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.1 40e_26.03.02.26_M_release_155771_signed.zip
MD5: 49D07F0EE7DE1765A6A84CB12FA53110
Size: 312 MB
^ go download the file and then rename it from "PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60. 140e_26.03.02.26_M_release_155771_signed.zip" to "PD15IMG.zip" (make sure its not PD15IMG.zip.zip) and put it in root of your SDCard. Go in to bootloader and follow the instructions. This will get you to stock rom/radio from there you can redo all your stuff.

BlackSHELF said:
Hmmm I just reread your OP and you saying you somehow lost root trying to unroot and reroot, so I am not sure about the current status.
NOMRAL CASE:
http://forum.xda-developers.com/attachment.php?attachmentid=516463&d=1297577207
^ download that and unzip it and get the recovery.img for 3.0.0.6 and try "fastboot flash recovery recovery.img" as that would do if not try the below.
EXTREME CASE:
http://www.filefactory.com/file/caa....140e_26.03.02.26_M_release_155771_signed.zip
File: PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.1 40e_26.03.02.26_M_release_155771_signed.zip
MD5: 49D07F0EE7DE1765A6A84CB12FA53110
Size: 312 MB
^ go download the file and then rename it from "PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60. 140e_26.03.02.26_M_release_155771_signed.zip" to "PD15IMG.zip" (make sure its not PD15IMG.zip.zip) and put it in root of your SDCard. Go in to bootloader and follow the instructions. This will get you to stock rom/radio from there you can redo all your stuff.
Click to expand...
Click to collapse
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3426 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.180s
The other file did not work either. It had "Fail-PU" for all the files it tried to flash

Did you try the PD15IMG.zip from bootloader? Download it make sure its not corrupted that is why I provided you with md5 hash to verify. Then put the file in root of your sdcard and then boot in to bootloader, it will scan it and follow the instruction to revert back to original.

BlackSHELF said:
Did you try the PD15IMG.zip from bootloader? Download it make sure its not corrupted that is why I provided you with md5 hash to verify. Then put the file in root of your sdcard and then boot in to bootloader, it will scan it and follow the instruction to revert back to original.
Click to expand...
Click to collapse
Yes I just verified it and it is not corrupt. Thats the way I did it and came up fail-pu

lilterro said:
Yes I just verified it and it is not corrupt. Thats the way I did it and came up fail-pu
Click to expand...
Click to collapse
Hmmm never seen or heard of that I am taking fail pu means failed partition update. What does your HBOOT ver say on the screen? I am not sure what happened but seems like it soft-brick ATM still not sure how you lost root. Hopefully someone who has little more knowledge can shed some light.

BlackSHELF said:
Hmmm never seen or heard of that I am taking fail pu means failed partition update. What does your HBOOT ver say on the screen? I am not sure what happened but seems like it soft-brick ATM still not sure how you lost root. Hopefully someone who has little more knowledge can shed some light.
Click to expand...
Click to collapse
Ok thanks anyway. I am normally able to wok my out of alot of these issues that come up with flashing but this one got me stumped to.
HBOOT-0.86.0000

perm-brick no fix
lilterro said:
Ok thanks anyway. I am normally able to wok my out of alot of these issues that come up with flashing but this one got me stumped to.
HBOOT-0.86.0000
Click to expand...
Click to collapse
I am having the very same problem i am very good at fixing my mistakes but this one is impossible i get that same fail-pu but only difference is mine is s-on and it was never rooted only temp-root i was trying to perm-root and that's when it crashed will not boot up any more and i can't boot into recovery because it never been rooted and i don't know how to do ( C:\android-sdk-windows\tools>fastboot flash recovery recovery.img ) looks like something for the pc and i tried factory reset it will just freeze with the 3 androids skating i go to fastboot and i see bootloader, reboot, reboot bootloader and power down but those did nothing i even offered $100 through paypal to the first person how fixes it but it's an impossible task so there is a full brick out there people say its not but i see different.
perm-brick no fix

Downgrade to 2.2.1 problem

Following this guide http://forum.xda-developers.com/showthread.php?t=1178912
I'm having trouble on the final downgrading step. I've followed all other instructions and everything is working great until I try to reboot into the bootloader and downgrade. When I get into the bootloader and press the power button it takes me to the HBOOT screen and freezes. I tried doing the fastboot method also and it transfers the zip, but then is stuck at the "writing 'zip'..."
md5 matches for the PD15IMG.zip
Any ideas?
Also on the HBOOT screen the top 2 line say:
"GLACIER PVT SHIP S-OFF
HBOOT-0.89.0006"

No ideas on this? I also tried it over again using Ubuntu and no luck

i'm having trouble changing the version number =/. sorry to thread jack

S-OFF means your phone was already rooted, and you don't need to do anything. Look in Developers section, find a thread for re-rooting S-OFF device, it contains PD15IMG with only recovery in it. Flash it.

I'm not sure which thread the PD15IMG with recovery is in. Do you know the title or have a link to it?
Also, why would flashing the PD15IMG w/ recovery not make HBOOT freeze like flashing a completely stock PD15IMG does? If it is actually S-OFF shouldn't it accept the stock 2.2.1 PD15IMG anyways?
EDIT: nevermind, I'm guessing I should be using the PD15IMG from this thread?
http://forum.xda-developers.com/showthread.php?t=1200147
I tried using one of those and HBOOT still freezes as soon as I get to it

Yes, that's the one.
I don't know why you get the freezing - it shouldn't be freezing anyway, stock or not.

Jack_R1 said:
Yes, that's the one.
I don't know why you get the freezing - it shouldn't be freezing anyway, stock or not.
Click to expand...
Click to collapse
Yeah, I'm at a loss as to what to do now. Everything requires using hboot to flash and that's not working

Use another SD card.
Format it in Windows.
Put recovery PD15IMG.ZIP on it.
Attempt flashing in bootloader.
If it doesn't work:
Extract recovery.img from the PD15IMG.ZIP that you downloaded.
Set up fastboot.
Change your bootloader to fastboot mode (select FASTBOOT with power button).
Verify that you see your phone by running "fastboot devices" from command prompt.
Flash recovery by executing "fastboot flash recovery your_extracted_recovery_image.img".

Tried using another SD card and I finally got it working. I can't believe I didn't think to try that lol. Thank you so much.

Jack_R1 said:
S-OFF means your phone was already rooted, and you don't need to do anything. Look in Developers section, find a thread for re-rooting S-OFF device, it contains PD15IMG with only recovery in it. Flash it.
Click to expand...
Click to collapse
Tried manual downgrade could not load image in hboot said was wrong img.
Tried fastboot downgrade stuck htc screen cmd reads can't load stockrom. Now it could be I have the wrong file named stockrom. of the PD15IMG file.I could unlock my bootloader either following htcdev.com i get this message and another one
Please Help me this is Driving me Nuts!!!
FAILED (status malformed (1 bytes))
finished. total time: 0.021s
C:\android-sdk\platform-tools>
GLACIER PVT SHIP S-On
HBOOT-0.89.0006

commandersafi said:
Following this guide http://forum.xda-developers.com/showthread.php?t=1178912
I'm having trouble on the final downgrading step. I've followed all other instructions and everything is working great until I try to reboot into the bootloader and downgrade. When I get into the bootloader and press the power button it takes me to the HBOOT screen and freezes. I tried doing the fastboot method also and it transfers the zip, but then is stuck at the "writing 'zip'..."
md5 matches for the PD15IMG.zip
Any ideas?
Also on the HBOOT screen the top 2 line say:
"GLACIER PVT SHIP S-OFF
HBOOT-0.89.0006"
Click to expand...
Click to collapse
I have wanted to downgrade my mytouch 4g to stock rom , when I flash it it's stuck at "sending "zip" <319593 KB>..." what to do next?
I have used methot "Fastboot Downgrade"
following error says ; FAILED <data transfer failure <too many links>
FAILED <satatus read failed <too many links>>
Thanks