I have a ChugHwa Magic 32A, which I believe I may have bricked.
I applied Roger's recent Magic RUU (3.54.631.3), which worked fine. I then needed to provide assistance to someone who was trying to root their phone (on 3.03.751.4) , so downgraded my phone using the ChungHwa RUU, which installed the 1.76.0007 SPL (S-ON), but failed to complete the install.
Now I'm stuck in RUU. If I try to use the Rogers RUU to upgrade again, it says the current image version is 3.54.631.3 (even though the SPL and radio are of the earlier versions), when I try to fastboot flash anything, it gives "FAILED (remote: 12 signature verify fail)".
Any attempts at using a different RUU freeze with the empty progress bar on the phone, and "Sending ... Updating the ROM image on your Android phone..." on the PC. After four or five minutes, the PC says "ERROR [155]: UNKNOWN ERROR".
I've spent the larger part of the day trying to fix this, and I've exhausted the ideas I can think of. Could anyone provide direction?
Related
Hello to all ,
Yesterday my friend received a message on his Magic that proposed to update the system. He did the upgrade, but something went wrong and the phone is locked in red Vodafone splash screen.
I was reading and trying various things, with the following results:
adb not recognize the device, the command fastboot tells me: FAILED (remote: not allow). The same on Linux and Windows.
By combining keys, I can access on the phone to fastboot and Android System Recovery.
Anyone have any ideas I can try to return to normal?
Magic data are:
Sapphire 32B SHP S-ON G, HBoot 1.33.006 (SAPP 10000)
CPLD-10
Radio 2.22.19.56I
Thanks in advance ! Best Regards !
I read a little more and saw the error (fastboot remote: not allow) is caused by a "perfect spl" (I guess)
And to solve this I need to create a goldcard and other things, which is impossible since adb does not recognize the magic. I'm going the right way? Any suggestions?
Thanks
The fight continues, I'm trying to change the SPL with the update.zip method, but I get the error
"No Signature verification fail".
It is necessary to create a goldcard?
Because I can not, since adb does not work.
Anyone have any recommendation? Thanks and regards
I am attempting to root a mytouch 3G 2.1 (w/ the headphone jack)
I followed the directions from theunlockr
got my goldcard working (according to the link on that page that tells you how)
After flashing the sappimg file on that page, I still had touch screen. (the site said I wouldn't)
and when I got to step 7 - the step about flashing through fastboot - I got the error "(remote: not allow)"
I flashed the attached file and got the same error.
I searched some more and found a supposed fix I downloaded the first and tried it, got "model ID incorrect! Update Fail!"
At this point, my phone would not show up in adb, but it would in fastboot, and it would boot to the login to google screen (didnt bother logging in earlier)
Tried the second one, same error.
Reset the device, booted fine. Restarted into fast boot, it is recognized, but still getting error "(remote: not allow)". Still not showing in adb.
My phone currently says:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
so my phone works, but it is not rooted and I still have the stock recovery. If I could get Amon_ra on it I feel comfortable with doing the updates through recovery.
And if I understand it correctly, this root is like a droid, caused by the ROM and not actually part of the stock ROM, correct?
I've done 4 g-1 and a droid in less than 3 hours each, but I've been at this all day.
Help! What can I try?
I tried to show links, but I'm new to the board and cant.
Ok, So I will document as I go, so either someome can help me at some point or I can help someone else if they have the same problem.
Redownloaded the sapping file (through the cyan wiki)
Reformated my goldcard through phone.
used a sd card adapter and HxD to put goldcard back on sdcard.
transfered new sapping file to sd card
booted in bootloader, got "Model ID Incorrect" Update failed.
I do have the three skating androids though... is that stock?
I will try rebooting my computer, maybe windows is being stupid...
Rebooted, Windows is not seeing the phone. Neither is the HTC sync thing, and neither is adb
Changed USB ports, uninstalled unknown device, changed usb ports again,
ADB recognized it (not in bootloader mode)
ok, found another site with adb commands. forums .tmonews. com /index. php? topic= 10412 .0;wap2
did a google search for "vodaphone sappimg", came up with a forum post on here, downloaded it to my goldcard, still get model ID incorrect.
so I started over from the beginning using cyan instructions. update failed again.
No idea what is going on!
After installing the latest cyanogen mod my phone started to act sluggishly. So I decided to try and unroot the device, restoring the device to its factory status using fastboot. However, I accidently used the wrong .nbh file for this. I used Sappimg.nbh (which is designed for 32A models). Chaos ensues.
The phone picked up the sappimg and overwrote the system/recovery/spl succesfully, but since it's the wrong image, my phone is bricked. It can still boot, but it will not do anything once you enter your PIN-code, an error pops up after any second of activity, force closing everything. The only thing I am able to do is connect the SD-card to my computer trough quick use of the notification bar. I can't get to my recovery or create a goldcard since it will no longer accept fastboot commands (remote: not allowed error).
Model: HTC Magic Vodafone (Netherlands)
Hboot info:
Sapphire PVT 32B SHIP S-ON G
HBOOT-1.33.006 (SAPP10000)
CPLD-10
RADIO-2.22.19.261
Does anyone have any suggestions? I haven't really tried the goldcard method yet, and I have an additional android phone available it this helps in a way.
You can make a GoldCard with the other phone and it will work in your's. You'll need to get an engineering SPL loaded on your phone before you'll be able to reflash the correct SPL. Go the GoldCard route.
Alright, I've created a working goldcard using my spare android phone. I have never used a goldcard before though, and I'm not really sure how to use it. What are the steps nescessary to flash a new spl?
You just need to grab the correct sapping.nbh for your phone, copy it to your goldcard, put the goldcard in your phone, and boot into fastboot pressing back and power. The phone will check the image then tell you to press the trackball to flash if your goldcard is working right.
Sent from my HTC Magic using XDA App
Using the Sappimg extracted from the Vodafone NL RUU.exe still gives me CID incorrect errors. I have a goldcard inserted; are there certain steps necessary to guarantee its succes? If your pc can still read it after altering the hex values it should be working right?
Meanwhile, I've poked around a bit after booting the phone up, and it turns out I can still get to certain apps, but anything that requires the home screen results in an error that force closes everything, so I can't get into setttings. I can only get to items that are presented in the notification bar like text messages or e-mails. If only I could get to USB-debugging settings I could fastboot my way out of this mess...
I've managed to fix the software part by installing a home replacement app, so I'm good for now; I'll just have to see how I can re-root the device if I want to fix the default launcher I guess
For the incorrect CID, your GoldCard may not be any good. I ran into a problem when I first made mine and it didn't work. I ended up redoing everything, including reobtaining the CID via ADB and it worked the second time around.
Yep, that did the trick! It worked this time, I managed to get the code from my own phone this time through adb, and went through the steps of creating a goldcard again. Thank you, almighty goldcard, my phone is now up and running again Even managed to re-root and re-install cyanogenmod now.
\o/
A bunch of people with rooted phones are reporting that when they attempted to flash the 2.1 RUU overtop of CM6 they would get a signature error during the update process.
It's looking like the SPL is getting changed to 1.76.0010 and the radio is getting changed to 6.35.16.19 after which the update hangs with the signature error. Either recovery is failing during flash or is not replaced with this RUU but either way recovery is dead. and the RUU won't complete.
My opinion is that Amon-Ra recovery for the Magic is still on there and won't work because it won't work with that SPL/Radio combination. I've had one person report to me that he received the signature error even when attempting to manually flash the Amon-Ra Hero version onto the phone.
Also from a couple of pics that I've seen, it looks like the phone is stuck in RUU USB mode.
So are they bricked or is there a way for them to breathe life back into their phones?
This happened to me... my phone is currently stuck on the RUU screen and shows:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0008 (SAPP50000)
CPLD-12
RADIO-3.22.20.17
Nov 3 2009, 15:56:29
It seems I can also send files with flashboot, but everything comes back as Failed (remote: 12 signature verify fail).
Any suggestions to get out of this? Or am I firmly in the bricked category?
Thanks!
for others that r looking to flash the rogers stock rom.
Would it work if we flash rogers's old 1.5 911 RUU over CM6 first, then flash the new 2.1 RUU?
Obviously the 2nd step will be straight forward, but how about the first step?
do u guys heard sth called goldcard? make one and run the ruu again.
i have the issue, i am trying with a glodcard but i have a problem to get the cid of the sd card. because the phone is briked ! adb is not working
i will keep you inform if i found any solutions
edit :still not working any other idea !!! i cant find the way to get cid of sd card without adb...
finnaly i got the glodcard but the RUU is still not working ! error bad signature !
hi,
i need ur guys opinion,
story goes
i have Magic 32a unlocked version.
then i root it to android 2.2.1 using the old radio / hboot combo.
then, i thought i want to update to android 2.3.1
now here is where the problem begins.
i accidently flashed the 32b radio on the phone. now the phone wouldnt go past the HTC Magic logo.
to fix this, i download the mytouch3G sappmig.img file and completely flash the phone over.
when i open fastboot it still using the 32b radio / hboot but this time the os loaded fine.
i install superandroot and superoneclick on the phone to root it
after rooting i tried flashing 32a radio / hboot but it say not allow.
next step i tried installing custom recovery and finally manage to do it using the flashrec app. i installed 32a recovery but it failed to boot it. i tried installing 32b recovery and it run fine.
now from the recovery itself i tried flashing 1.76 radio and the recovery unpack the file just fine. but when it says reboot, the 'Box with arrow and phone outside' image appear for a sec and then dissapear.
after that my htc magic is completely dead. pressing any button, pluging in usb cable or charger yield no effect (like a brick)
have i completely bricked my phone? please help.
Sad to say this, but yes.
You just had a bad radio flash...
Try JTAG.
i tried again after leaving the phone overnight, these are the only thing iam able to do with the phone:
trackball + power = blue led
long press power = led blink red once
plug in charger = battery charge indication light on, orange and then yellow indicating the battery is full.
and thats about it. no other button combo works. and fastboot devices and adb devices booth shows no device.
anyone doing this JTAG repair service?
bump...
im having the same problem...just posted my issue here: http://forum.xda-developers.com/showthread.php?t=959938
i have the blue LED as well...
i googled how to make a JTAG cable...but its really past my level of competence...
were you ever able to get your phone fixed?
you found any solid step by step guide to make the jtag? please post the link here. i want to explore further. tq.
i was having the same problem...initially all went well, manage to change the from SHIP S-on to ENG S-off. i brick my device right after updated the rom to froyo and thereafter unable to boot. everytime i booted my magic, i only sees the RUU (fastbot) page. i cant do adb command. luckily the fastboot flash command still work.
i have try flashing with a lot of different images but always got stuck @ either
FAILED (remote: 42 custom id check fail) or FAILED (remote: 12 signature verify fail). never go beyond that...after going thru so much hassle of finding the right image, i finally manage to get it up and running. it flashes by ROM to enclair (2.1), good enough for me to use whatapp..
specification of my Magic is 32A S-O; radio 6.35.16.19; hboot 1.76.0010
this is how i "unbrick"
Download the SAPPIMG from shipped-roms.com, download Brasil_SAPPIMG_3.54.zip
place the file in android sdk folder, where fastboot resided.
make sure your device is fully charged...
boot your device and connect it to the usb, you will sees RUU USB.
type this command fastboot flash zip XXXXXXX.zip
i hope this help...