Database Users

Problem when applying second custom splash screen

I read two threads about how to apply the splash screens and decided to try it for myself. I followed the directions as they were both nearly identical. The first splash went on like a charm. The second one is giving me troubles however, I send it through fastboot and it says ok, then when it says writing it says that it failed and it is because the partition does not exist. I have searched the forums on both the dream and sapphire and have not been able to find a solution as to why I cannot flash the second splash screen. Any help would be greatly appreciated. Thanks.
Tazz

Could you possibly post the commands you are using and the actual error you are receiving? This information could help us help you.

Sorry. I am using these commands in fastboot:
fastboot flash splash1 mysplash1.rgb565
fastboot flash splash2 mysplash2.rgb565
fastboot reboot
when I get to splash2 I get: "sending splash 2 <300kb>... okay
writing splash2...FAILED <remote: partition does not exist!>"
I hope this helps. Thank you, once again.
Tazz

My SPL
Could this have anything to do with my SPL? I read that if you have a certain SPL you can only flash one boot image. Anyone know if this is correct?

[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.

My DHD is nearly bricked. Please help.

I have a T-Mobile UK DHD that I'd fully rooted, Eng-Off, Radio S-Off & SuperCID
I was running a LeeDroid ROM but yesterday it began frequently locking up so I tried to do a wipe and reinstall the ROM but at the end of the ROM installation after "Writing boot.img" it said:
assert failed: write_raw_image ("/tmp/boot.img","boot")
E:Error in /sdcard/LeeDrOiD_HD_V2.0.0.zip
(Status 7)
Installation aborted.
I also kept getting the messages E:Can't mount CACHE:recovery/log & E:Can't open CACHE:recovery/log
I then tried to install the stock 1.32 RUU but that stuck at the Updating User Data stage at 40%.
I'm now stuck with the bootloader options and simply have a white screen with the below and warning triangles bottom left & right.
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
MICROP-0438
RADIO-26.04.02.17_M2
eMMC-BOOT
Oct 11 2010, 12:47:02
RUU (This is highlighted yellow)
I have tried ADB but the device isn't shown as attached. However, Fastboot shows it attached but I've had no success pushing the ROM this way either. Below is copy of the cmd window:
C:\AndroidSDK\tools>fastboot boot PD98IMG.zip
creating boot image...
creating boot image - 301006848 bytes
downloading 'boot.img'...
OKAY [ 47.302s]
booting...
FAILED (remote: not allowed)
finished. total time: 47.302s
Can anyone offer any assistance as I've run out of ideas and fear I've bricked it.

you cant just flash rom via ADB. you need recovery. Do you have clockwork mod recovery?

The message you get about being unable to write boot suggests you are no longer S-off, whilst bootloader suggests you have s-off, l would start from scratch and s-off again and then try reinstalling the rom

20mark said:
you cant just flash rom via ADB. you need recovery. Do you have clockwork mod recovery?
Click to expand...
Click to collapse
I used to but it's been wiped as part of the the failed RUU installation. Power On/Vol Down now does nothing
ghostofcain said:
The message you get about being unable to write boot suggests you are no longer S-off, whilst bootloader suggests you have s-off, l would start from scratch and s-off again and then try reinstalling the rom
Click to expand...
Click to collapse
Do you mean Eng or Radio off? Can I do that with no bootloader options or recovery?
How would you suggest installing the ROM and which one?
Thanks for any advice.

I've just tried jkolo's easy S-Off tool but I get an error message pop-up "Module or hboot fail. Aborting."

So what happenes when you choose the recovery option?
Oh and btw don't worry too much about the void warranty, I've read of a few people who've had to send phones back to HTC without being able to revert to stock first and they've been successful - obviously this is a last resort.

EmprtArea said:
So what happenes when you choose the recovery option?
Click to expand...
Click to collapse
I don't have a recovery option on the Phone.

So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
If you need the image it here: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.6-ace.img

EmprtArea said:
So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
Click to expand...
Click to collapse
I haven't tried that yet but fear the 1st line may wipe my only way of communicating if the 2nd part doesn't work

well you say you haven't got the recovery option anyway, so you could leave that line out I only put it because that's what I'd do.
HOWEVER: I'm no expert.
Question after Re-reading your post: Are you worried you'll delete fastboot? I'm sure that's not what I'm suggesting. But as it's your £500 device wait for someone else to confirm.

EmprtArea said:
So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
If you need the image it here: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.6-ace.img
Click to expand...
Click to collapse
No luck
Code:
C:\AndroidSDK\tools>fastboot flash recovery recovery-clockwork-3.0.0.6-ace.img
sending 'recovery' (3334 KB)...
OKAY [ 0.560s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.562s

Everytine you try writing it fails what else can you do?
Sent from my Desire HD using XDA App

I'd jump to thinking you're not ENG S-Off anymore (got to say probably the failed 1.32 flash that did it. And you can't use that tool so look for an alternative description of how to get there.
If you can't use ADB I don't know how to get there.
If somehow ADB does start working then the CyanogenMod wiki might be useful.
http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Root_Guide

If you lost s-off while flashing the 1.32 rom then I also suspect you lost root.
Sent from my Desire HD using XDA App

I've got backups of:
hboot_original.bin & part7backup-1294609557.bin
Are they of any help?
I can't see any way to gain Eng-Off without root so I'm at a loss.
The frustrating thing is I don't know what happened in the 1st place that froze my phone and kicked all this off. I'm guessing I have a hardware fault of some sort
Would T-Mobile exchange or repair under warranty, despite the mods I'd made?

Aamir.Badat said:
If you lost s-off while flashing the 1.32 rom then I also suspect you lost root.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I'm starting to regret trying that as a solution now

I remembered something similar being posted on these forums a few months ago, so I had a search and found this thread:
http://forum.xda-developers.com/showthread.php?p=9139950
I'm not an expert on these things, so I don't know if this would work for you. I would suggest waiting for someone with a bit more experience than me to join the discussion, as I don't know how similar your circumstances are to the ones in that thread. Do you get any error messages on your PC when you run the RUU? I take it that it finds your phone, whereas in the thread above the RUU wasn't seeing the phone.
However I thought reading that might give you some hope. Worth reading the thread all the way through.

I think what disabled most of your options was flashing a stock ruu. It overwrites hboot and the recovery.
Edit: since the ruus fail installing, maybe someting is off with your device, NAND error or someting.

this sort of thing doesnt happen if you are flashing custom roms though right? its making me nervous now!

preacher65 said:
I remembered something similar being posted on these forums a few months ago, so I had a search and found this thread:
http://forum.xda-developers.com/showthread.php?p=9139950
I'm not an expert on these things, so I don't know if this would work for you. I would suggest waiting for someone with a bit more experience than me to join the discussion, as I don't know how similar your circumstances are to the ones in that thread. Do you get any error messages on your PC when you run the RUU? I take it that it finds your phone, whereas in the thread above the RUU wasn't seeing the phone.
However I thought reading that might give you some hope. Worth reading the thread all the way through.
Click to expand...
Click to collapse
Thanks for the tip. I'll have a read and may give that a go.
KamikaZeeFu said:
I think what disabled most of your options was flashing a stock ruu. It overwrites hboot and the recovery.
Edit: since the ruus fail installing, maybe someting is off with your device, NAND error or someting.
Click to expand...
Click to collapse
I don't get errors, the RUU just freezes and I have to pull the plug.
danrobz said:
this sort of thing doesnt happen if you are flashing custom roms though right? its making me nervous now!
Click to expand...
Click to collapse
The errors started when I was on a Custom ROM but my suspicion is that it's a hardware fault to blame. If I can't fix this then whilst the custom ROM probably didn't cause the damage, the general unlocking etc may have voided my warranty.

Phone wont let me downgrade through P15GIMG or fastboot StockRom. Please Help!

I bought a used phone and it had 2.3.4. I've rooted about 4 MT4G with visionary and TE with no problems. I put the file in the root of the SD card. Booted into bootliader and it started checking the file. It then said "Upgrade failed because file is older than current" . Never once did it ask me if I wanted to install upgrade. It just tells me to reboot after all that. Can anybody help? Thanks in advance!
June 5 Update:
Hey guys...Im trying to fast boot flash the StockRom zip for the MT4G but I'm getting this message:
C:\androidsdk\tools>fastboot flash zip StockRom.zip
sending 'zip' (319593 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
Any help would be appreciated. Thanks

http://forum.xda-developers.com/showthread.php?t=1178912
Sent from my HTC Glacier using XDA

OP Updated...I tried flashing the stock 2.2.1 through fastboot wityh the instructions through the g2/MT4G downgrade thread. I got the message that I posted in the OP. Please help fellas. Thanks!

Lakeshow423 said:
OP Updated...I tried flashing the stock 2.2.1 through fastboot wityh the instructions through the g2/MT4G downgrade thread. I got the message that I posted in the OP. Please help fellas. Thanks!
Click to expand...
Click to collapse
Maybe cuz your a Lakers fan lol
Edit: what boot loader do u have
Sent from my HTC Glacier using Tapatalk 2

You didn't downgrade the main version. You missed something in the instructions and/or prerequisites and/or failed to follow a perfectly detailed guide. Sorry, but what help are you expecting? Please follow the guide you've been pointed to until you realize what was the mistake you were making.
I guess that the options are:
1) You didn't complete the "Gaining temp root" and "Changing Version Number to Allow Downgrade" parts, assuming that you don't need those and can skip straight to downgrading part.
2) You successfully followed the guide, but the downgrade wasn't accepted - please look at your bootloader info and confirm that you have **UNLOCKED** in big red letters above it. Then, as Google would have suggested, please relock the bootloader - and it'll allow you to downgrade.

Hboot 1.02.000 Root/Cwm recovery help

so i unlocked my bootloader using the htcdev guide. this updated my hboot to 1.02.000 and when i try to flash CWM i get this error.
Code:
sending 'recovery' (1685 KB)... OKAY
writing 'recovery'... FAILED (remote: image error! (BootMagic check fail))

The Usual Suspect said:
so i unlocked my bootloader using the htcdev guide. this updated my hboot to 1.02.000 and when i try to flash CWM i get this error.
Code:
sending 'recovery' (1685 KB)... OKAY
writing 'recovery'... FAILED (remote: image error! (BootMagic check fail))
Click to expand...
Click to collapse
how (which method) are you trying to flash the recovery?

Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(boot.img can be found in ur stock ruu )
Type fastboot flash recovery 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.

help needed.
hey der. i have rooted my phone with s-on. but i am facing the same problem as i cannot boot in cwm recovery mode and hence cannot install a custom rom. i am no developer. so please can you elaborate your above method step by step. sorry i am a noob here.
thanx anywayz

Have you managed to install cwm?