Database Users

[Q] Trouble rooting MT3g Fender - Cannot verify signature

I have looked through all of the threads dealing with this and I cannot find the answer I am looking for.
I am trying to root the MyTouch Fender and have gotten as far as the sappimg.img
However, once I am in command prompt and I try to flash the radio, I am getting that it cannot verify the signature.
All of the instructions/files I am using are from theunlockr.com
Moderators, if this is in the wrong section, please feel free to move it.

Forget about the sappimg... follow my guide... it's much more simple...
Check out my signature

Ok, I have two questions. First, will this method work with the Fender/1.2 model?
Also, as I have already mentioned, I have ran the sappimg and now the phone is stuck with a non working touch screen. I have no way of running the app. Everything has to be done through adb now.

Do you have access to the system/OS ?

Not at all.

Post here ALL your fastboot info.. ALL
Also the output from this command
Code:
fastboot getvar version-main

Ok, a new problem, now when I plug the phone in, it is not showing up in adb devices like it did two days ago.
Here is the fastboot info:
Sapphire Unknown 32b ship 2-on h
hboot-1.33.0009 (sapp31000)
cpld-13
radio-3.22.20.17
may 8 2009, 21:02:32
Fastboot USB
<Vol down> HBoot Mode
<Send> Reset Device
<Action> Restart to HBoot
<Menu> Power down
I do not know if it is any help but I punched in the command anyways and this is what it said:
version-main: 2.16.151.1
finished. total time: 0.00s

Follow this guide:
http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
I just checked out the numbers... you should be good to go!
Just use this rom instead when you reach step 9:
http://cyanogenmod-mirror.local.host.name/ds/cm/stable/update-cm-6.0.0-DS-signed.zip

That was the guide that I was using to begin with. My original problem is that I cannot get past step 6. Every time I try to flash anything (the radio, hboot, recovery, etc) it tells me that it has failed, the signature could not be verified. Why would it be doing this?

Well.. you have been using the wrong sappimg.zip
Use this: http://rapidshare.com/files/436753940/2.53.707.2_-_sappimg.zip
Just rename it to sappimg.zip
Then follow the guide again... From step 2 :0)

Ok, I'll give it a shot and let you know!

Ok, I just tried it again and here is what I am getting:
sending 'radio' <21504 KB>...OKAY [35.703s]
writing 'radio'... INFOsignature checking...
FAILED <remote: signature verify fail>
finished. total time: 41.875s
This is where I have been stuck.

You need to follow the steps...
Like the goldcard og hboot mode are essentials for success...
Try again without using fastboot commands :0)

What do you mean about not using fastboot commands?

Chris.Thompson said:
Ok, I just tried it again and here is what I am getting:
sending 'radio' <21504 KB>...OKAY [35.703s]
writing 'radio'... INFOsignature checking...
FAILED <remote: signature verify fail>
finished. total time: 41.875s
This is where I have been stuck.
Click to expand...
Click to collapse
This is what i mean with fastboot commands...
Don't do the commands... use a goldcard and the right sappimg.zip

I need you to be a little more specific. What steps need to be taken when you say just use a gold card and the right sappimg? I am using a working gold card and the sappimg that you recommended but when the phone starts back up, I do not have a working touch screen.
To my knowledge, the way to correct this is to flash the proper recovery image. How can I do this without using fastboot commands?
Is there a writeup on the method you are recommending?

Ok, when in fasboot, at the top of the screen it says "s-on". Does this need to say "off" before it will stop rejecting the signature? Am I even on the right track?

Still haven't solved it. Any additional help would be very much appreciated! Thanks.

Hey. I had a similar problem and I fixed it by downloading a new SPL from this thread http://forum.xda-developers.com/showthread.php?t=529019 and putting it onto my SD Card.
Using Clockworkmod recovery, I installed the SPL from my SD Card (I chose Engineering SPL 1.33.2010) and then used the recovery to reboot, which completed the installation. When I later rebooted into fastboot mode, my info had changed to S-OFF. Then I had no problem upgrading the radio and SPL to the newer versions (which is what I was trying to do in the first place).
Hope that helps you.

Chris.Thompson said:
Still haven't solved it. Any additional help would be very much appreciated! Thanks.
Click to expand...
Click to collapse
What is your fastboot info now? I know this is kind of dead, but we'll see.

Mytouch 3g accidently flashed using wrong tutorial

I have read through for or so hours of everything I can find. I have a MT3G 3.5mm and thought I was following the proper steps to be able to flash ginger yoshi so I started to update.
I had this:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT 1.33.0013 (SAPP31000)
CPLD-13
RADIO 2.22.23.024
Now I have:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT 1.33.0013 (SAPP31000)
CPLD-13
RADIO 6.35.08.29
I have a sappimg.zip that is actually trying to flash except it starts to hang when it updates the radio. It will sit there for forever. I have left it going and the battery will die before it will finish updating the radio. I have been at this for quite a while now and really need help. I know I am supposed to be able to find a matching radio and spl. I tried flashing just the eng spl first, doesn't really do anything it just goes back to hboot. I have tried using fast boot and because it s-on it says no remote. I have tried going into the RUU usb mode and tried booting a recovery but it just sits there. It says it's booting but nothing happens. I did flash a recovery but that was with a 2.22 radio so I am guessing that the new radio that shouldn't be on there is messing it up. What else can i do here? I really need help!

You need read this topic: http://forum.xda-developers.com/showthread.php?t=1169301

##Calling fastboot with: flash zip C:\Users\Adonis\Downloads\special_sappimg.zip###
sending 'zip' (11094 KB)... OKAY [ 3.166s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 6.384s
********************************
This is what I get when I try the first step. However, my situation is even more screwed. I am stuck at the RUU screen so all i have now is access via usb fastboot and fastboot commander. I can't get access through android commander. I have been trying to flash everything under the sun and when I do flash the proper sappimg.zip it just hangs when updating the radio and it hangs at like 97 percent and will not go any further no matter how long it's there.
To sum up. Followed this tutorial before and that's how I got here in the first place, because I thought I was following the right instructions to be able to get ginger yoshi but it turns out, my phone isn't what I thought it was.

Did you create goldcard properly?
Sent from my A7-040 using Tapatalk

HAAAAAAAA! SCREW ALL THAT .
I have the Mytouch 3G 1.2 (3.5mm Headphone jack) .
it was running android 2.2.1 and i used SuperoneClick root, then downloaded Rom Manager changed my Recovery and flashed ezGingerbread .
SIMPLE!

That's great and all but I would like help. I do not care about how awesome you are. I was unable to do superoneclick for some reason when I downgraded to 1.6. Nothing would work right. Rom manager would force close, universal androot would say that the phone was rooted and superoneclick would say that it wasn't.
Stuck in Ruu can't flash anything. Gets stuck on radio flash. Help. Accidentally flashed 32b board and chip files.
I did create a goldcard properly because i've used it over and over again without fail. It just hangs when flashing and doesn't finish flashing the radio.

Adonisd said:
##Calling fastboot with: flash zip C:\Users\Adonis\Downloads\special_sappimg.zip###
sending 'zip' (11094 KB)... OKAY [ 3.166s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 6.384s
********************************
Click to expand...
Click to collapse
Did you ever read tutorial?
The steps to follow:
1) Read and understand the above.
2) Rename special_sappimg.zip to sappimg.zip
3) Make sure that you have a working goldcard and flash the sappimg.zip
The device should reboot by it's self. If you get any error saying model id is no correct, you have a faulty goldcard. Also, please verify that the spl has changed to 1.76.xxxx. (flash by holding volume decrease (-) together with power and wait for the hboot to automatically pick up the file)
4) Once the device has rebooted, you should rename the 2.53.707.2_-_sappimg.zip to sappimg.zip and flash it using the goldcard. This image should give you an eng spl. If you device will not accept it/or you wish to have stock image, then rename the stock sappimg(2.10.531.4) to sappimg.zip and flash it the same way as the special sappimg.
5) If you indeed get the eng spl, then you have full control and we can do almost anything we want. Just post here and we can take it from there. The eng spl has the following nr: 1.33.2010.
If you flashed the stock sappimg, then you only need to root and flash custom recovery and you should almost be there... also here post the progress and we will take it from there.
After item 2 you must flash in hboot-mode (Turn off, then turn on by pressing VolumeDown + Power)
Please read always carefully, try to understand process and don't rush...

I cannot follow those steps to the T. I am stuck in RUU mode on my phone. So I cannot get back to the Hboot. I have been trying to flash everything with fastboot commander. I have a working gold card, just can't get back to where i can access it via phone. When I did have it working though, it was giving the same problem. It would just hang when trying to update the radio.
I have read and understood this particular tutorial. Infact it was the first I found after this particular problem started to occur. However, when I renamed and tried the files it would give the same error with the gold card. I have even, formatted and redone the gold card, which has always worked. Now I am stuck in Ruu and I do not think i can get access back to the bootloader.

Turn phone off (Remove battery, wait 2-3 minutes, place it back)
Turn on by pressing and holding Volumedown + power
What happening in this moment?
Sent from my A7-040 using Tapatalk

It goes straight to Ruu mode, no matter what i press or what buttons I hold down or no matter how long I leave the battery out.

Adonisd said:
It goes straight to Ruu mode, no matter what i press or what buttons I hold down or no matter how long I leave the battery out.
Click to expand...
Click to collapse
Try to run (it should escape from ruu-mode)
Code:
fastboot oem boot
Then turn off (cause phone is bootlooping) and load into hboot-mode

i got a bunch of text in the command prompt when I tried to run it that made it look like it was going to do it, then it just hung and did nothing.
Still in Ruu mode.

Once you are stock in ruu mode, you kinda fu*ked.
You need hboot and goldcard to fix the problem.
There is a command called: fastboot oem resetRUUflag
Try it out, but most likely it is not permitted...

Adonisd said:
I cannot follow those steps to the T. I am stuck in RUU mode on my phone. So I cannot get back to the Hboot. I have been trying to flash everything with fastboot commander. I have a working gold card, just can't get back to where i can access it via phone. When I did have it working though, it was giving the same problem. It would just hang when trying to update the radio.
I have read and understood this particular tutorial. Infact it was the first I found after this particular problem started to occur. However, when I renamed and tried the files it would give the same error with the gold card. I have even, formatted and redone the gold card, which has always worked. Now I am stuck in Ruu and I do not think i can get access back to the bootloader.
Click to expand...
Click to collapse
hmm if by now you havnt been able to access your phone, then maby perhaps you can do so by the commmand "" fastboot oem boot""

i have the same problem with this. STUCK IN RUU MODE!!!!
BUT I can open my phone via "fastboot oem boot". The only problem is whenever my phone has been turned off, it STUCKED in RUU MODE, so I need to go through "fastboot oem boot" again just to open my phone.
here's my device:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0010 (SAPP10000)
CPLD-12
RADIO-6.35.10.18
Jan 14 2010, 00:14:58
RUU
=======HELP====ME======PLS==========

If this is not too late. Adonisd you need to stay on the 2.22 radio with that mt3g 1.2
Sent from my Dream/Sapphire using Tapatalk

Help with Mytouch 3G

Hi Guys!
I need help with a MyTouch3G with 3.5mm jack (cell for my little niece), I was reading but don't want to make the same mistakes.
I brick my cell and it don't turn on, just the blue light (holding trackball + Power)
I send it to repair, and now the cell turned on Hboot, Fastboot, But NO Recovery or ROM.
I open the Commander program the info that show is:
SAPPHIRE UNKNOWN 32A ENG S-OFF H
Code:
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
Radio version: 6.35.10.18.
SPL/hboot version: 1.76.2007.
product: sapphire.
mid: sapp*****.
security: off.
build-mode: eng.
Cannot flash Newfiles (Radio, Hboot)
Code:
Flashing "radio" - PLEASE WAIT.
"radio" flash FAILURE.
Can flash the Recovery but when try to access to it don't work, stuck @ Mytouch 3G First Screen
Code:
C:\Users\User\Desktop\New folder (4)\Tools>fastboot flash recovery recovery.img
sending 'recovery' (3954 KB)... OKAY [ 1.572s]
writing 'recovery'... OKAY [ 2.110s]
finished. total time: 3.684s
C:\Users\User\Desktop\New folder (4)\Tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 1.572s]
booting... OKAY [ 0.003s]
finished. total time: 1.576s
I also try:
RUU_Sapphire_T-Mobile_US_2.10.531.4_release_signed_NoDriver.exe
I receive error communication
To be honest don't know what to do next
Any help will be appreciated!
PD: Sorry for my English.

Your current SPL-info mismatches with model.
Never use MT3G v1.2 with hboot 1.76.XXXX / radio 6.35.XX.XX - it will not work.
But, repair-shop half-fixed your brick and you able to restore right configuration.
If you really have MT3G v1.2 (with 3.5" audiojack), download: http://www.multiupload.nl/S7BVSOWB8J
There are:
hboot 1.33.0013d
radio 2.22.28.25
recovery AmonRa 1.7.0 G
1. Unpack
2. Run following code (radio first, then hboot, then recovery). Sure, you can rename files from archive.
Code:
fastboot flash radio radio.img
fastboot flash hboot hboot.img
fastboot flash recovery recovery.img
fastboot reboot-bootloader
3. Last command will reboot into fastboot-mode again and you will see new SPL-info. Check it, then you can install custom ROM via recovery

I will try it in a minute and report back if work or not...
Thanks!

Ok. I try it
Flash all without problem...
I try boot from recovery (Home + power Button), but don't boot.
Stuck @ Mytouch 3G Screen
I was thinking maybe the home button don't work, so tried
fastboot boot recovery.img
Click to expand...
Click to collapse
I receive the message
Downloading....OK
Booting... Failed
Then I tried:
RUU_Sapphire_T-Mobile_US_2.10.531.4_release_signed_NoDriver.exe
Detect the cell, flash all, now the cell turn on and have the ROM, but the touch screen is not working :S. I cant do anything.
So I'm stuck here, don't want to do nothing more, because don't want to brick my phone again..
The info that the cell display now is:
SAPPHIRE UNKNOWN 32B SHIP S-ON G
Hboot-1.33.0013 (SAPP*****)
Radio-2.22.23.02
Oct 21 2009, 22:33:27
Why now is 32B and not 32A? :S
(I remember that it was 32A before I brick it the first time, when I install a Sappimg.nbh and it was for vodafone and the number change to unknown 32B, Then it was stuck @ RUU and then I brick it.
Now I saw the S is On too, I think is because I use the official RUU.
If is possible fix this to stock I'm Ok, but if is possible root or change the Rom will be great.
Thanks in Advance.

HTC Magic Bricked?

Hello XDA-developers,
A few days ago I've received a HTC Magic from a friend of mine.
I already told him not to flash the phone if yo'don;t know what you're doing, but he did it anyway
He tried to flash it to a different software version, but he got stuck.
Now I am stuck with this phone.
I've tried probably all the tutorials on this forum and all the others, but now I'm really desperate.
So please help me.
Here is the situation:
Type of Phone: HTC Magic
Hboot: 1.33.0007 (SAPP10000)
CPLD-10
Radio: 2.22.19.261
The phone cannot access its SD-card in recovery mode(2e).
It gives me the following error:
"E:Can't mount /dev/blcok/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)"
It does not boot anymore to the system(it does boot but gets stuck at the lockscreen, where it has no option to unlock).
It's not accessible with adb.
It's accessible with fastboot.
Tried to enable SD with flashboot:
"fastboot oem enableqxdm 0"
But getting:
"...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s"
Tried to flash bootloader:
"fastboot boot recovery.img"
But getting:
"downloading 'boot.img'...
FAILED (remote: not allow)
finished. total time: 0.000s"
Tried to copy sappimg.zip to SD-card, but since it's probably not accessible,
it cannot find it in HBOOT-mode so also doesn't flash it.
It's a Dutch Vodafone Branded HTC Magic.
I've been working on this phone for the last 48 hours, I know it's not worthed, but it's the principle
I know the problem is in SPL version, but all the tutorials mention that you update this throught the SD-card, which I cannot access.
Anyone there to help me with this problem?

[Q] [Magic 32B] Can't install or boot cust recovery after htdev unlocked

Hi everyone,
I have an HTC Magic 32B (SFR/Vodafone FR).
I updated hboot from 1.33.0013 to 1.33.0014G (*1) to be able to unlock the bootloader with htcdev unlock.
I unlocked it successfully using HTC official instructions.
Now I want to boot or install a custom recovery (recovery-RA-sapphire-v1.7.0G.img) and it doesn't work.
My hboot boot says :
Code:
*** UNLOCKED ***
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0014G (SAPP10000)
CPLD-10
RADIO-2.22.28.25
Jan 31 2012,14:43:52
HBOOT
<BACK> FastBoot Mode
From fastboot (when I hit Return) I have the "FASTBOOT USB" string, from fastboot if I try :
1)
Code:
C:\android\downloads>[B]fastboot boot recovery-RA-sapphire-v1.7.0G.img[/B]
downloading 'boot.img'...
OKAY [ 1.712s]
booting...
[B]FAILED (remote: not allow)[/B]
finished. total time: 1.733s
2)
Code:
C:\android\downloads>[B]fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img[/B]
sending 'recovery' (4520 KB)...
OKAY [ 1.712s]
writing 'recovery'...
[B]FAILED (remote: not allow)[/B]
finished. total time: 1.738s
After reading htc instructions to flash img, I also tried from RUU mode using "fastboot oem rebootRUU", that gives me RUU USB on the phone and on the computer :
Code:
C:\android\downloads>fastboot oem rebootRUU
...
OKAY [ 0.012s]
finished. total time: 0.016s
Then I try :
1)
Code:
C:\android\downloads>[B]fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img[/B]
sending 'recovery' (4520 KB)...
OKAY [ 1.718s]
writing 'recovery'...
[B]FAILED (remote: image type not support)[/B]
finished. total time: 1.749s
2)
Code:
C:\android\downloads>[B]fastboot boot recovery-RA-sapphire-v1.7.0G.img[/B]
downloading 'boot.img'...
OKAY [ 1.714s]
[B]booting...[/B]
Here it hangs, I must enter a fastboot reboot to regain the control on the device.
I don't know what's wrong here. Either from fastboot (usb) or ruu (usb) it don't work even if the bootloader is unlocked.
amonra recovery should install and work on this phone right ?
Currently I don't want to root or S-OFF the phone because I like to apply not too much modification on it.
Can you help me ?
Thanks for the attention, and even more if you can help
(*1) 1.33.0013 cannot be htcdev unlocked because it don't accept "fastboot oem get_identifier_token", that's why I updated to 1.33.0014G.
The update was given by htcdev.com through an RUU that didn't work because I started it from adp (phone started normally with usb debugging on) and for an unkown reason adp reboot bootloader didn't work, I made it work be starting RUU exe from fastboot directly.

I think my problem/solution may be related to the error : "remote: image type not support" when I try to flash recovery being in RUU mode.
From the official updates files (official ruu and fota) I've found that some images are not of the img format but the nb0 format. Maybe I need to flash an image that is of this format (nb0), the problem is that I have no idea how to find or convert amonra recovery image to this format...
If it is the problem, it is lame not to be able to flash img files ...
Also, one idea I had is that I have to flash files through an update.zip file rather than a single img. But it is a lot more complex to figure out (making a valid update.zip package)...
I'm quite lost and decieved about the HTC "unlock" (I think I'm not the first one to be) ... (And I don't want to brick my phone)

superbob56 said:
I think my problem/solution may be related to the error : "remote: image type not support" when I try to flash recovery being in RUU mode.
From the official updates files (official ruu and fota) I've found that some images are not of the img format but the nb0 format. Maybe I need to flash an image that is of this format (nb0), the problem is that I have no idea how to find or convert amonra recovery image to this format...
If it is the problem, it is lame not to be able to flash img files ...
Also, one idea I had is that I have to flash files through an update.zip file rather than a single img. But it is a lot more complex to figure out (making a valid update.zip package)...
I'm quite lost and decieved about the HTC "unlock" (I think I'm not the first one to be) ... (And I don't want to brick my phone)
Click to expand...
Click to collapse
hi, i have same problem on my HTC Magic, from hboot 1.33.0014 i can`t do enything (flash new recovery or new rom or make RUU)
did u resolved that problem?

I must admit I've given up.
I recently bought myself a fresh Nexus 5...
Gold luck to you if you try to go on with the HTC Magic !