Related
Hi all,
I've been trying to install the amon RA recovery rom on mg gf's magic, but I'm stuck in a loop.
I've got a non perfect SPL loaded which boots into cupcake
Sapphire PVT 32B Ship S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-10
RADIO-3.22.20.17
However when I try to run fastboot boot recovery.img it restarts and gets stuck on the splash screen.
I've re-made the sd card to be a gold card and I've still got the issue.
I've also tried running fastboot flash recovery recovery.img
and I get Infosignature checking... FAILED )remote : signature verify fail).
Can anyone help me sort this?
Many thanks
will
You're using a non-engineering SPL, so all fastboot commands will fail. 1.33.2005 has fastboot enabled and you should be able to flash it from your currect state, however I was on .26i radio when I flashed it so I don't know for certain.
EDIT: Since you're on cupcake you should be able to use flashrec to flash the recovery image, so not engineering SPL required!
Hi Adrian,
thanks so much for replying.
In the meantime I've tried another sappimg and this has taken me to 1.33.2010 which has let me fastboot flash recovery... but when I try to boot into recovery (hold home and restart) all i get is the htc magic spash screen
The other issue is that the rom ive now got is lacking the google tools and therefore market, so i cant get flashrec
Any thoughts?
thx
No problem about missing the market, do "adb install *Drag FlashRec APK here*", that will get it installed.
How long did you hold down home+power to get to recovery? The first time I did it after loading up Amon Ra's 1.7.0 it took me holding them for around 1.5-2 minutes before it finally booted in.
Hiya,
I waited about 5 mins or so
I've now got flashrec installed... looking for what to do next?
Here. Start at step 12 assuming you've already got a recovery image.
Hmm, just tried that and it flashes in an instant (too quick tbh!), so im wondering if this is because its already got the recovery on it from when i did it via fastboot
After restarting and holding home im still getting just the splash screen
Is there a way to view what is on the /recovery/ partition, or is there a reason its not wanting to boot into it?
thx
Which recovery image are you using?
billytkid said:
Hmm, just tried that and it flashes in an instant (too quick tbh!), so im wondering if this is because its already got the recovery on it from when i did it via fastboot
After restarting and holding home im still getting just the splash screen
Is there a way to view what is on the /recovery/ partition, or is there a reason its not wanting to boot into it?
thx
Click to expand...
Click to collapse
try
fastboot erase recovery, then reflash recovery
AdrianK said:
try
fastboot erase recovery, then reflash recovery
Click to expand...
Click to collapse
He can't complete any fastboot commands since he doesn't have an engineering SPL.
DonJuan692006 said:
He can't complete any fastboot commands since he doesn't have an engineering SPL.
Click to expand...
Click to collapse
I did tell him how to get one ;-P
Hopefully it won't come to that. I think he's loading the wrong recovery image.
recovery-RA-sapphire-v1.7.0G.img
Try re-downloading the recovery image from here and try flashing again. If it doesn't work I think your going to have to try going Adrian's route.
Better yet, you can get it from step 5 here for a quicker download.
Also, when you were in FlashRec running the "/sdcard/recovery-RA-dream-v1.2.3.img" command did you change recovery-RA-dream-v1.2.3.img to match the filename of your recovery image?
I've just managed to update the recovery, but strangely this is using the 32A recovery.. and not 32B.. but I've got a vodafone Magic
So I can now get into recovery and have followed the steps or dangerSPL, followed by cyanogen mod + gapps, but not i cant get it to fully start up and im stuck on splash screen
V confused now.. just checked in hboot and its still showing sapphire pvt 32b eng s-off H
Hboot 1.76.2007
radio 3.22.20.17
looks like the gf's not having a mobile tomorow.. oh dear im in trouble!
any ideas again much appreciated!
thx
Can you run any fastboot commands?
Yes I can now run fastboot commands and use the recovery tool
thx
Hi all,
hope to get some more help, sorry!!
After looking more into this it seems that one of the previous images i put on the 32b phone was a 32a radio... hence the issue with putting on the recovery image for the 32b not working.
So... i downloaded myTouch-radio-2_22_23_02.zip and using the recovery did an update from zip.. now however the phone boots and all i get is a picture of a box with an arrow pointing to an android robot (see attached!)
At this rate its looking like i need to buy a new phone!
cheers all
Hi,
I followed the process introduced in the HTC Sapphire Hacking
(http://forum.xda-developers.com/wiki/index.php?title=HTC_Sapphire_Hacking)
trying to boot an Amon_RA recovery image that I got from
"http://forum.xda-developers.com/showthread.php?t=530492" (tried
recovery-RA-sapphire-v1.7.0G.img and
recovery-RA-sapphire-v1.7.0G-cyan.img). The problem is the image seem
booting but stalled in the very first boot screen (The white HTC Magic
log on the whole dark background). Then I had to remove the battery to get it back
The command line I was using is:
$ fastboot boot recovery-rom.img
and it told me that writing and booting are okay and finished.
Does anyone get a clue for the problem? Is there anything wrong with
my method?
Here are my phone information,
--
SAPPHIRE PVT 32B ENG S-OFF H
HBOOT-1.33.2010
--
Thanks in advance.
-
narke
You have ENG spl and s-off...
That's very good..
You only need the recovery...
Try to flash it, instead of booting it...
In fastboot try typing this:
fastboot flash recovery recoveryImageNameHere.img
Restart into recovery by holding the home+power together...
This should do the trick :0)
Development is NOT for your own development. It is for the community.
Thread moved to General (Q&A)
So I have been trying all night to flash my buddy's MyTouch 3g to Cyanogenmod 6 and have run into several issues.
1. Created golddisk and updated the bootloader
2. Flashed radio (fastboot)
3. Flashed hboot (fastboot)
4. Flashed Clockwork recovery (fastboot)
I have been able to access Clockwork and install CM 6, and google apps. After all of this, the splash sreen hangs and never loads the ROM. For some reason, I decided to update the radio again to the radio img I downloaded from Cyanogen. After radio flash the hanging splash screen happens again. So I remove the battery and try to enter the bootloader (vol down+power) and it goes staight to the splash screen. Tried to enter recovery rom, same thing. The only thing that works is trackball+power to get the blue LED. HELP!!! I would prefer not to buy him another phone. (THIS WOULD BE THE THIRD PHONE I HAVE LOADED WITH CM6. NEXUS ONE, SPRINT HERO CDMA BEING THE OTHER TWO.)
Provide this info:
All fastboot info. ALL of it.
Run this command and post the output:
Code:
fastboot getvar version-main
When ALL info is provided we can help you!
mumilover said:
Provide this info:
All fastboot info. ALL of it.
Run this command and post the output:
Code:
fastboot getvar version-main
When ALL info is provided we can help you!
Click to expand...
Click to collapse
How can I get that information without access to the bootloader where the Comand Prompt can access fastboot?
My mistake :0)
i have ran into the same problem
this happened to me because i basically tried downgrading the radio with the one of the cyanogen website
now my phone is bricked cannot access fastboot ,
have tried this method ?
i am about to try it see if it works
forum.xda-developers.com/showthread.php?t=656798
hmm..
i feel like the goldcard method is last years root method, although i know nothing of it, i just remember it having to many steps. theunlockr.com has the way i rooted and its never done me wrong as far trouble shooting.
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.