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!
Related
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.
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.
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
I have a Rogers Dream. My goal was to hopefully get it working more smoothly again (CM 6.x was just running way too slow on it), so I set out to try to get Yoshi's ROM working on it. I saw that I needed an updated bootloader and radio from what I currently had.
Well, to make it short, now nothing will fastboot flash. Here is the current state of my phone as said by the bootloader:
Code:
DREAM PVT 32B SHIP S-ON
HBOOT-1.33.0013d (DREA21000)
CPLD-4
RADIO-3.22.26.17
When I try to fastboot flash an image (all have been MD5sum verified) - lets just say I am trying to flash a RA recovery image - using "fastboot flash recovery <filename>", I just get the following:
Code:
sending 'recovery' (4594 KB)...
OKAY [ 1.719s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.094s
This is true no matter what I try to flash...
Is there something I am missing here?
You should have read Terry's thread about the 1.33.0013d/2708 combo, then you knew that flashing a single partition is not supported by that SPL. You can only erase partitions and flash complete .nbh files. Flashing ROMs needs to be done by recovery.
Sent from my Gingerbread on Dream using XDA
OK - so I assume you are talking about this thread, right? http://forum.xda-developers.com/showthread.php?t=831139
Just to make sure I understand things correctly, it looks like I should be following this process:
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
Click to expand...
Click to collapse
This will give me a stock radio/hboot/recovery, correct? So, then I would flash over an RA bootloader (unless there are better now - I haven't played with my Dream in a while - hence me getting myself into this mess...), a radio (2.22.27.08 and 2.22.28.25 seem to be the best ones from a quick view of the forums - which is recommended?), and then 1.33.0013d again.
Does this all sound right?
The goal of all of this is to be able to give this Dream to a person to use as their main phone until they get a new one, so I am looking for a fast, stable ROM to put on it. It certainly doesn't have to be flashy or whatever is the latest version of android that works on the Dream. From what people are saying, it seemed like Yoshi's was the ROM that would most fit these goals. Would you agree?
yes thats the thread
with the 1.33.0013d the only thing you can do is fastboot -w
no big deal since most everything can still be done in recovery.
lost your recovery?
flash the orange.nbh
now you have an engineering spl
now flash recovery... yeah your happy
well no know you need 1.33.0013d again
be safer this time
fastboot flash recovery, fastboot flash radio, fastboot flash hboot
so yes you are correct in following these steps!
have fun!
Yes follow the orange.nbh instructions then the flashing at the top of the recovery, spl, and hboot. Don't reboot inbetween those. Do exactly what the thread says.
And also, FroyobyLaszlo is probably the best "phone" rom. CM7 is the smexiest one.
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