Related
Applied the latest Rogers ROM...what a bad move...
Now my HTC Magic got stuck in RUU screen showing the following:
SAPPHIRE UNKNOWN 32A SHIP S-OFF H
HBOOT-1.76.0010 (SAPP50000)
CPLD-11
RADIO-6.35.10.18
Jan 14 2010, 00:14:58
RUU
I tried many ways to get rid of this screen but didn't work.
My phone original has the rogers 2.17.631.2 build, and I did a bad move to upgrade to Android 1.5.=( The RUU process flashed my HBOOT and RADIO, but as soon as it starts the "system" steps, the screen shows unzipping for over an hour and eventually failed. Now my phone will start up with the above screen only!! i can't get myphone startup in recovery mode or fastboot mode.
I tried re-run the RUU porgram on my PC and the tool still shows i have the old anroid build. Hence i know that i now have NEW HBOOT and RADIO but still the old Android build.
Is there a way for me to get out of this RUU screen? Any help is appreciated.
Is the security off (S-OFF) allows me to downgrade the SPL? If so, how can i do that given i can only boot my HTC Magic in this screen only.
One more side note, fastboot can detect the phone.
Urgently need help! Appreciated.
If you have constant security S-OFF, it accepts all ROMs and HBoot and RUU. Probably you have engineering Magic (not Hboot, the whole device)
1. Try this...
If fastboot can detect phone, so try flash Amon_RA Hero recovery http://forum.xda-developers.com/showthread.php?t=561124
fastboot flash recovery recovery.img
(recovery.img or other filename must be in folder with fastboot.exe)
Then start into recovery (Home + Power) and flash CursorSense
If you need original ROM (without root), so search forum for it
(it has been posted already). Just get rom1.zip (system.img, userdata.img and more...) and flash it (Saying again: official doesn't contain root)
2. Or try run another RUU
5[Strogino] said:
Oh... you have S_OFF after official upgrade, it isn't often to meet.
If fastboot can detect phone, so try flash Amon_RA Hero recovery
fastboot flash recovery recovery.img
(recovery.img or other filename must be in folder with fastboot.exe)
Then start into recovery (Home + Power) and flash CursorSense
If you need original ROM (without root), so search forum for it
(it has been posted already). Just get rom1.zip (system.img, userdata.img and more...) and flash it (Saying again: official doesn't contain root)
Click to expand...
Click to collapse
but the fastboot method requires engineering SPL, but my phone was upgraded to the perfected SPL. Shall I try the RA_Hero or RA_Sapphire ?
ngecw said:
but the fastboot method requires engineering SPL, but my phone was upgraded to the perfected SPL. Shall I try the RA_Hero or RA_Sapphire ?
Click to expand...
Click to collapse
Yes, common fastboot required to be engineering. But you have S-OFF now, so no checks.
use RA_Hero, cause you have radio 6.35.X.X
5[Strogino] said:
Yes, common fastboot required to be engineering. But you have S-OFF now, so no checks.
use RA_Hero, cause you have radio 6.35.X.X
Click to expand...
Click to collapse
Tried flashing the recovery.img (RA_Hero) but failed.
i typed fastboot flash recovery recovery.img [ renamed the file to recovery.img] but got the error...
sending 'recovery' <3362 KB>... OKAY
writing 'recovery'... FAILED <remote: image type not support>
Just to clarify more, the screen only shows "RUU USB" not "FASTBOOT" although fastboot can see my device... could that be the reason why it failed?
According to your 2nd suggestion, where can i find other RUU and how do i know which is the proper one?
ngecw said:
Applied the latest Rogers ROM...what a bad move...
Now my HTC Magic got stuch in RUU screen showing the following:
SAPPHIRE UNKNOWN 32A SHIP S-OFF H
HBOOT-1.76.0010 (SAPP50000)
CPLD-11
RADIO-6.35.10.18
Jan 14 2010, 00:14:58
RUU
I tried many ways to get rid of this screen but didn't work.
My phone original has the rogers 2.17.631.2 build, and I did a bad move to upgrade to Android 1.5.=( The RUU process flashed my HBOOT and RADIO, but as soon as it starts the "system" steps, the screen shows unzipping for over an hour and eventually failed. Now my phone will start up with the above screen only!! i can't get myphone startup in recovery mode or fastboot mode.
I tried re-run the RUU porgram on my PC and the tool still shows i have the old anroid build. Hence i know that i now have NEW HBOOT and RADIO but still the old Android build.
Is there a way for me to get out of this RUU screen? Any help is appreciated.
Is the security off (S-OFF) allows me to downgrade the SPL? If so, how can i do that given i can only boot my HTC Magic in this screen only.
One more side note, fastboot can detect the phone.
Urgently need help! Appreciated.
Click to expand...
Click to collapse
the rogers ROM is not working right. Too many crashes and so on .. so try this one
RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe
You can download it from HTC main site ...
Also, you have to keep in mind that you can RUU as many as you want. So do the procedure again and keep us posted if it's working. If not send me a PM and i'll resolve it step by step.
best of luck !
I have one Magic and it show in Bootloader :
PVT 32 S-OFF
1.76.0007 (SAPP*****).
Why the SAPP is SAPP*****? Is there something wrong?
Also, the device detected by fastboot is 1234567890... , not like other HTC Magic.
Now I get stuck with RUU Flash at 81% (Hong Kong RUU). --> When the device start to update system STEP. So the Magic now just show RUU, can connect by Fastboot but when use fastboot flash system or recovery, only can send to phone and write error.
Anybody help me to solve this?
ntphuong said:
I have one Magic and it show in Bootloader :
PVT 32 S-OFF
1.76.0007 (SAPP*****).
Why the SAPP is SAPP*****? Is there something wrong?
Also, the device detected by fastboot is 1234567890... , not like other HTC Magic.
Now I get stuck with RUU Flash at 81% (Hong Kong RUU). --> When the device start to update system STEP. So the Magic now just show RUU, can connect by Fastboot but when use fastboot flash system or recovery, only can send to phone and write error.
Anybody help me to solve this?
Click to expand...
Click to collapse
I do have the same problem with my RUU flash with the new Rogers RUU. Stuck at 81% when device starts updating at step[4] "system". Phone will show "unzipping" for over an hour and eventually failed with error code [155].
I tried the RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_ NoDriver.exe but still the same problem. Can anyone help here?
Did more investigation, and seems like both RUU ROMs i tried might not match the CID, hence the system ROM updating failed.
Now the question is, i am stuck in RUU and cannot use adb to check my CID now. How can i manually update the system ROM given i am in RUU mode only?
How can i manually update the HBOOT and RADIO if i am stuck in RUU screen? If the RUU program can automate the process in one click, is there program to allow me to update each individually? Note that i cannot get into fastboot mode.
Any advice? Thanks!
Help
ngecw said:
Did more investigation, and seems like both RUU ROMs i tried might not match the CID, hence the system ROM updating failed.
Now the question is, i am stuck in RUU and cannot use adb to check my CID now. How can i manually update the system ROM given i am in RUU mode only?
How can i manually update the HBOOT and RADIO if i am stuck in RUU screen? If the RUU program can automate the process in one click, is there program to allow me to update each individually? Note that i cannot get into fastboot mode.
Any advice? Thanks!
Click to expand...
Click to collapse
Same problem here. Can someone help?
Thanks in advance.
ntphuong said:
I have one Magic and it show in Bootloader :
PVT 32 S-OFF
1.76.0007 (SAPP*****).
Why the SAPP is SAPP*****? Is there something wrong?
Also, the device detected by fastboot is 1234567890... , not like other HTC Magic.
Now I get stuck with RUU Flash at 81% (Hong Kong RUU). --> When the device start to update system STEP. So the Magic now just show RUU, can connect by Fastboot but when use fastboot flash system or recovery, only can send to phone and write error.
Anybody help me to solve this?
Click to expand...
Click to collapse
I had a 32B G2,it was brikked at the first time when I ruu flash the rom(Sense official). G2 couldn't received any RUU rom.it would stop at 22%.
Today,when I ruu flash the rom（HTC_Europe_3.04.401.2）,I also found it stop at 81%.
SPL is updated to 1.76.0008 from 1.76.0007.
It seems much better than before. But it still could not accept the cmd "adb shell"
Hoping somebody could help us.
I used the following RUU after upgrading to sense RUU stopped at 81%
hxxp://suntharee.com/android/RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_sign ed_NoDriver.exe
Here is another link, its the first RUU in this post:
hxxp://forum.xda-developers.com/showthread.php?t=548096
You will end up with an ENG SPL that allows you to flash what ever you want then.
I manually updated Radio and SPL and now using CursorSense ROM.
Obviously replace the "hxxp" with "http". Hope it helps at least some of you like it did for me.
Rugga said:
I used the following RUU after upgrading to sense RUU stopped at 81%
hxxp://suntharee.com/android/RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_sign ed_NoDriver.exe
Here is another link, its the first RUU in this post:
hxxp://forum.xda-developers.com/showthread.php?t=548096
You will end up with an ENG SPL that allows you to flash what ever you want then.
I manually updated Radio and SPL and now using CursorSense ROM.
Obviously replace the "hxxp" with "http". Hope it helps at least some of you like it did for me.
Click to expand...
Click to collapse
I tried but already got stuck in the first step of unzipping system.img. Looks like this RUU will upgrade system first before HBOOT and RADIO, hence i am still stuck with Perfected SPL.
Given that my phone has security off (SOFF), is there way to downgrade my HBOOT?
I had the same problem when HK SenseUI appeared and I managed to pass the RUU screen with a gold-card. You will find tutorials in this forum.
Good luck!
vbucuroiu said:
I had the same problem when HK SenseUI appeared and I managed to pass the RUU screen with a gold-card. You will find tutorials in this forum.
Good luck!
Click to expand...
Click to collapse
Were you upgraded to the latest perfected SPL when the same problem happens? I had my goldcard configured properly, but everytime i run RUU, the process hang at 81%, which is the time when unzipping system.img happens.
I understanding the latest SPL is still yet hard to crack, but will my phone being S=OFF, can have some ways to get the system check bypassed?
Thanks!
Hi. I have the some problem. My magic stops at 81% (system - unzipping), or when i try with another RUU_.exe stops at 22% (system - unzipping).
S-ON.
Anyone can help us?
PS: Sorry for my english.
(
Nobody knows?
ONX said:
Nobody knows?
Click to expand...
Click to collapse
Same boat...
ONX said:
Hi. I have the some problem. My magic stops at 81% (system - unzipping), or when i try with another RUU_.exe stops at 22% (system - unzipping).
S-ON.
Anyone can help us?
PS: Sorry for my english.
Click to expand...
Click to collapse
What did you do??? 32B Magic not compatible with RUU Upgrades
What exactly do you have? You posted in one place - that you have 32B
But on picture you have 32A
I installing RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe
I make a goldcard for installing _HTC Magic_RUU_Sapphire_SMC_Voda_WWE_3.03.990.6_release_signed_NoDriver.exe (with this update can enter in fastboot and vol down + power) but stops when loading system.img
Sorry for my english.
Yes, i have 32B.
Before:
SAPPHIRE PVT 32B Ship S-ON H
HBOOT-1.33.0010 (SAPP10000)
CPLD 10
RADIO-3.22.20.17
Jun 2 2009 17.28.28
After:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.007 (SAPP10000)
CPLD-10
RADIO-6.35.07.29
Aug 4 2009, 19:43:30
Dear users,
I wanted to root HTC Magic with the following helpful tutorial.
http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/
However, I faced a problem about the motherboard version. When I check the motherboard version as tutorial suggested, I saw that it is 32B. However, Recovery Flasher app claims that it is EBI1/32A and it does not allow to flash the recovery image of 32B.
On the other hand, when I checked /proc/meminfo file, it says that
MemTotal: 99708 kB
MemFree: 12068 kB
which is 32B as suggested by Amon_Ra
So, I am confused. Could you please tell me which recovery image should I use? A small background information, I bricked the phone before with rooting procedure by the same reason and gave it back and got it refurbished. So, I am not sure but the motherboard information recorded somewhere else may mislead the Recovery Flasher application.
Thank you,
Omer
Which version of the recovery you should use is dictated by the version of your radio, not motherboard.
2.xx.xx.xx - G version
3.22.xx.xx - H version
hope it helps!
Thank you for the reply. I checked the radio version and it was 3.22.xx.xx. So, I tried the HTC version. However; The recovery manager didn't let me flash with this image. I think, I have the same situation as this post has
http://forum.xda-developers.com/showthread.php?t=680793
But, I didn't yet root my device.
Thank you,
Omer
What exactly spl do you have?
Turn off, then turn on by pressing Back + Power, post first 5 strings.
If you have 1.33.2010 S-OFF you can revert back to radio 2.22.XX.XX
This is the 5 lines.
SAPPHIRE PVT 32B SHIP S-OFF H
HBOOT-1.33.0010 (SAPP10000)
CPLD-7
RADIO-3.22.20.17
Jun 2 2009, 17:28:28
Should I root it first or revert back the radio?
Thank you for your help.
Since you have s-off already, just download 1.33.2005 SPL and do
fastboot flash hboot 1.33.2005
and
fastboot flash recovery recovery.img
Wrong forum by the way dude
But before flashing SPL, shouldn't I flash radio? Sorry to ask newbie questions but I am really lost and I don't want to brick the device.
By the way, My device is HTC Sapphire aka HTC Magic. That's why; I wrote in here. Is it wrong?
Thanks.
osaatcioglu said:
But before flashing SPL, shouldn't I flash radio? Sorry to ask newbie questions but I am really lost and I don't want to brick the device.
By the way, My device is HTC Sapphire aka HTC Magic. That's why; I wrote in here. Is it wrong?
Thanks.
Click to expand...
Click to collapse
I did not find any info, when someone did it in the past already. I'm not sure for this, but it looks logical. Anyway, if you don't want brick device - don't use it
You have 2 methods to restore 32B radio and hboot and get ability to flash 32B-roms
Method 1.
As you wrote - you have S-OFF, so fastboot commands are allowed
You can simply run
Code:
fastboot flash radio radio.img
fastboot flash hboot hboot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot reboot-bootloader
where:
radio.img - radio 2.22.19.26I
http://member.america.htc.com/download/RomCode/ADP/GIO/ota-radio-2_22_19_26I.zip?
Unpack it from archive
hboot.img - hboot 1.33.2005 eng s-off (Haykuro DangerSPL)
http://rapidshare.com/files/247838950/update.Engineering-SPL-HBOOT-1.33.2005-signed.zip
Unpack it from archive
recovery.img - Amon_RA Sapphire recovery 1.6.2 G version
Important: flash radio then hboot. Don't reboot after flashing only radio.
Method 2. You can use rom.nbh from official update for 32B Magics:
create goldcard
unpack rom.nbh and rename to sappimg.nbh, copy it to goldcard
flash in hboot-mode (VolumeDown + Power)
You will get 1.33.0007 perfected SPL, so you must root device next
But one thing... you have S-OFF - may be you have engineering device - so you can use fastboot commans always - it makes flash-process very easy)
5 thank you for the instructions. This is what i was looking for. If any other experienced user confirms it might work, i would like to take the risks and do the instructions then share the results.
Experienced users, what do you think?
-------------------------------------
Sent via the XDA Tapatalk App
Go for it.
I took the encouragement and gave the first command and unfortunately got this error. I guess, this is not engineering device :/
fastboot flash radio radio.img
sending 'radio' (21504 KB)... FAILED (remote: not allow)
Does anybody has an idea? Please.
Please help. I'm a NOOB, but been managing to install the ROM specific for MT3G/Fender, but I want to know if I'm able to do more with my myTouch 3.5mm Jack version. This is what I have:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.013 (SAPP31000)
CPLD-13
OCT 21 2009, 22:33:27
When I try to install a ROM with 32A listed, it doesn't boot. Can someone please help me understand what phone I have and what ROM's are compatible with it?
I would appreciate it very much, THANK YOU
stlouie65 said:
Please help. I'm a NOOB, but been managing to install the ROM specific for MT3G/Fender, but I want to know if I'm able to do more with my myTouch 3.5mm Jack version. This is what I have:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.013 (SAPP31000)
CPLD-13
OCT 21 2009, 22:33:27
When I try to install a ROM with 32A listed, it doesn't boot. Can someone please help me understand what phone I have and what ROM's are compatible with it?
I would appreciate it very much, THANK YOU
Click to expand...
Click to collapse
You have T-Mobile MyTouch 3G v1.2
Read these topics:
http://forum.xda-developers.com/showthread.php?t=622530
http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
Thanks 5, just wanted to make sure so when I'm installing ROMS, I know which ones will work and the ones that are not for my phone
stlouie65 said:
Thanks 5, just wanted to make sure so when I'm installing ROMS, I know which ones will work and the ones that are not for my phone
Click to expand...
Click to collapse
Mmm. It's hard. All ROMs for MT3G 1.2 marked [mt3g 1.2] or something special
You must not use [32A]-marked ROMs
Forum need to be restructuzired...
Thanks for that VALUABLE TIP. That's good to know also. I've noticed you have S-OFF H and I have S-ON G, is my less or what? Haven't found anywhere that could explain the configurations properly
stlouie65 said:
Thanks for that VALUABLE TIP. That's good to know also. I've noticed you have S-OFF H and I have S-ON G, is my less or what? Haven't found anywhere that could explain the configurations properly
Click to expand...
Click to collapse
S-OFF - it is hboot without security. It means, that everyone can use fastboot commands without any warnings.
Magics have S-OFF, if it developer or engineering device OR if hboot patched by someone
There are some patched (engineering) hboots for Magics, but not for [MT3G 1.2]
In manual to root patched hboot is using, but if you stay with it - touchscreen does not work. Don't know why.
Thanks 5. I believe I'm good now, just have to be patient and await the arrival of new ROMS for my MT3G 1.2
Appreciate all your assistance in helping understand better about my phone.
5[Strogino] said:
I did not find any info, when someone did it in the past already. I'm not sure for this, but it looks logical. Anyway, if you don't want brick device - don't use it
You have 2 methods to restore 32B radio and hboot and get ability to flash 32B-roms
Method 1.
As you wrote - you have S-OFF, so fastboot commands are allowed
You can simply run
Code:
fastboot flash radio radio.img
fastboot flash hboot hboot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot reboot-bootloader
where:
radio.img - radio 2.22.19.26I
http://member.america.htc.com/download/RomCode/ADP/GIO/ota-radio-2_22_19_26I.zip?
Unpack it from archive
hboot.img - hboot 1.33.2005 eng s-off (Haykuro DangerSPL)
http://rapidshare.com/files/247838950/update.Engineering-SPL-HBOOT-1.33.2005-signed.zip
Unpack it from archive
recovery.img - Amon_RA Sapphire recovery 1.6.2 G version
Important: flash radio then hboot. Don't reboot after flashing only radio.
Method 2. You can use rom.nbh from official update for 32B Magics:
create goldcard
unpack rom.nbh and rename to sappimg.nbh, copy it to goldcard
flash in hboot-mode (VolumeDown + Power)
You will get 1.33.0007 perfected SPL, so you must root device next
But one thing... you have S-OFF - may be you have engineering device - so you can use fastboot commans always - it makes flash-process very easy)
Click to expand...
Click to collapse
I am trying to do method 2. But I couldn't find rom.nbh from official update for 32B Magic. Could any body tell me where I can find it?
Thanks.
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0007
CPLD-12
RADIO-6.35.07.29
Android 1.5
listed is my phone details. i have tried every single method found in the forum to root my phone or flash into a new rom but it just all doesnt work.
I have previously update the HTC ROM [HTC Sense] Version: 3.03.707.5 a few months back.
1. I have tried this link by using the rom1.zip copied from the temp when running the Official RUU Sapphire HTC Europe AT test signed. but it failed.. Wrong model CID i think..
*If you have ENG SPL 1.76.2007 you can simply unpack only rom.zip without new HBoot and radio and flash directly*
forum.xda-developers.com/showthread.php?t=625108
2. I have tried using using the rom1.zip copied from the temp when runing the RUU_Sapphire_HTC_Asia_WWE_3.03.707.5_R_SG_release_signed_NoDriver.exe but everything is same and the flashrec or fastboot method all failed..
2.1 I have tried using a flashrec and recover image to root my phone
but i received backup failed and was not able to flash the image too..
theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/
2.2 fastboot method when fastboot devices indicate the devices serial no. but when i try to fastboot recovery .. [failed : remote not allow is the error]
2.3 when i tried adb method.. it just failed too
I am lost and i hate the new sense rom i updated few months back.. before that i did flash the hero rom before i changed to the new sense rom..
i read some post saying that the new sense rom will block all ways to root or flash new room.. but some post said that with a gold card created, it will overcome that.
Please i have been reseting my phone for the whole week now.
Please guide me to the light.. Awaiting for some enlightenment~
Hello All,
I have been trying for the past few hours to root my HTC Magic 32B (Vodafone UK) and flash Cyanogen to get me some android 2.2!
The phone was on Android 1.6 before i started the process. I have since managed to roll it back to the vulnerable 1.5 version using a goldcard and sapping.zip
I have also managed to push RA-sapphire-v1.7.0H onto the phone.
Now every time i wipe and then flash any of the cyanogen ROMs using the recovery mode, it hangs at the Vodafone screen when booting. Now I had a look around and there were suggestions of trying a different ROM. I tried this and get the same result every time. I have installed 4 different versions of Cyanogen as well as numerous other ROMS.
An interesting point, I have a magic 32b and yet when trying to push the 'G' version of the recovery-RA file, the phone does not turn up under 'adb devices' but when pushing the H version, the phone responds as it should and loads the correct recovery file. I have tried both 32A and 32B ROMs to no avail they both still lock up at the Vodafone splash screen
I can restore to 1.5 without any problems, but I dont want to be stuck on this version of Android
A little info about the phone:
Firmware version: 1.5
Build Number: 2.16.151.1 146733 CL#31685 test-keys
SAPPHIRE PVT 32B SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-10
RADIO-3.22.20.17
May 8 2009,21:02:32
Many thanks in advance for any help you can provide!
There is guide on wiki.cyanogen you must be ona 1.5 version just read whole guide and it will be a success
If you have RA -h recovery working use it to flash hboot 1.33.2009
Then boot into fastboot and issue
Code:
fastboot erase system -w
fastboot erase boot
Here you can either boot onto recovery and flash the ebi1 version of cm. (Yes historical for 32a but seems your newer rom is using the 32a radio)
Or install a 2.x radio via fastboot (you must not flash it from recovery or you will brick your phone)
Last I checked cm wiki deals with 32a radios on 32b devices badly
Diekund said:
An interesting point, I have a magic 32b and yet when trying to push the 'G' version of the recovery-RA file, the phone does not turn up under 'adb devices' but when pushing the H version, the phone responds as it should and loads the correct recovery file.
SAPPHIRE PVT 32B SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-10
RADIO-3.22.20.17
May 8 2009,21:02:32
Click to expand...
Click to collapse
1) You see the last "H" in the first line of your info?
That means you need to use H-recovery and not G-recovery!!!
First problem solved....
2) You see the radio version 3.22.20.17?
Thats is only for 32A boards.. be lucky that you did not brick your device..
You need this radio and only this radio: 2.22.19.26I
But there is something wrong with combination of the info you wrote..
All 32B devices have G as the last letter in the first line of thire spl..
Are you sure that what you wrote is correct?
To solve this, flash back your stock version... use RUU or whatever... No sappimg or goldcard...
Just bring back the phone to where is was when you got it from the shop.
Then follow this guide made by me:
http://forum.xda-developers.com/showthread.php?t=756942
it will root you device in 5 mins... and for 5 min extra you get custom recovery and engineer spl( <-optionel)... FULL CONTROL OF DEVICE, the right way!
mumilover said:
2) You see the radio version 3.22.20.17?
Thats is only for 32A boards.. be lucky that you did not brick your device..
You need this radio and only this radio: 2.22.19.26I
Click to expand...
Click to collapse
This is FUD .. thats why its not bricked.
3.x = EBI1 (The -h recovery [magic] and -r recovery [dream*] is EBI1)
2.x = EBI0 (The -g recovery [magic] and default recovery [dream*] is EBI0)
* Please don't install the dream recovery on the magic it won't work its missing a config file for sapphire
both magic 32a/32b can run both
HOWEVER you must have the correct kernel to boot the device and if you have a 3.x radio and flash a radio from recovery you will brick since your current recovery can't boot after the flash.
Easiest is as I said install the engineering SPL that also supports both radios and fastboot yourself a stable system.
(the only reason its not booting with the EBI1 magic32a rom now is probably its not being properly wiped)
As far as using fastboot to restore a 2.x radio and -G recovery:
32A devices (ignoring the fender for the moment) will not be able to use all their memory on a 2.x radio
32B devices run the same on both radios; however more roms assume you have a 2.x radio.
If you go to cyanogens website, the EBI1 kernel should be available in the downloads. Just reflash the 5.0.8.zip, then flash the EBI1.zip, and then GAPPS.
EDIT: Here you go http://forum.cyanogenmod.com/topic/394-cyanogenmod-5-for-dreammagic-mean-lean-pastry-machine-v508-06192010/.
Sent from my HTC Magic using XDA App
DonJuan692006 said:
If you go to cyanogens website, the EBI1 kernel should be available in the downloads. Just reflash the 5.0.8.zip, then flash the EBI1.zip, and then GAPPS.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
you rock my world haha
Thanks so much buddy, this little trick hit the spot and im now running android 2.2! hopefully its nice and easy to update my roms from now on
I've rooted my Magic, got Cyanogenmod running nicely, etc. I was then trying to flash a new splash screen, and noticed that my security in fastboot shows as begin on (S-ON). Sure enough it wouldn't let me flash the splash screen, it said the signature was not valid.
So, I tried flashing every single engineering SPL possible, and it never changes to off.
Here is my info from the fastboot/hboot screen.
SAPPHIRE PVT 32A ENG S-ON H
HBOOT 1.33.2010 (SAPP5000)
CPLD-12
RADIO-3.22.20.17
June 2 2009, 17:27:03
Thanks!
Find zipped hboot, put it in your sd card and flash it trough recovery...
pera987 said:
Find zipped hboot, put it in your sd card and flash it trough recovery...
Click to expand...
Click to collapse
That's what I've done. I've flashed every single engineering hboot file I can find and each one still shows S-ON during fastboot/hboot, and I"m unable to flash through fastboot.
Follow these steps (you should find it in this Mytouch Room)
1. Create your goldcard.
2. Comeback to 1.5 version by flashing rom 1.5 from goldcard.
3. Install Recovery Flasher (RF).
4. Run RF, chose Flash Cyanogen 1.4 img
5. Copy new E-SPL to root of Sdcard, Boot to Recovery mode, flash this file SPL
6. You can flash new recovery img (like 1.7.0G) by fastboot mode through your PC.
Check your new SPL now and S-ON becomes S-OFF.
I've successed on Magic 32B with perfect SPL 1.33.0006 and S-ON.
vinamilk said:
Follow these steps (you should find it in this Mytouch Room)
1. Create your goldcard.
2. Comeback to 1.5 version by flashing rom 1.5 from goldcard.
3. Install Recovery Flasher (RF).
4. Run RF, chose Flash Cyanogen 1.4 img
5. Copy new E-SPL to root of Sdcard, Boot to Recovery mode, flash this file SPL
6. You can flash new recovery img (like 1.7.0G) by fastboot mode through your PC.
Check your new SPL now and S-ON becomes S-OFF.
I've successed on Magic 32B with perfect SPL 1.33.0006 and S-ON.
Click to expand...
Click to collapse
Thanks. I'll give this a shot when I get home this afternoon.
PaulieORF said:
That's what I've done. I've flashed every single engineering hboot file I can find and each one still shows S-ON during fastboot/hboot, and I"m unable to flash through fastboot.
Click to expand...
Click to collapse
If this currently a 1.33.20** spl with s=off and a custom recovery can you please do the following
Run 'adb shell dump_image misc /tmp/misc_dat.img'
Then
'adb pull /tmp/misc_dat.img misc_dat.img'
Then send me the resulting image somehow (pm me a rapid share link or ask for my email.. there ought not be any identifiably info in misc but just in case)
This may or may not clear up why there is an issue.. and let a better process to fix it be created.. untill then try unrooting (or installing a stock spl) and re-rooting as was mentioned, just onto forget radio versions may change in the process requiring caution not to skip ahead of yourself and brick.
UPDATE:
So I got the file, misc was nearly all blank without the usual data (boot mode, CID and some other data) this is easily fixed by re-flashing misc from recovery.. I think this can even be made into an update.zip.. (since all magic/dream misc partitions are essentially the same besides the CID, and the CID is still being passed to the recoveries command line when stuck in this state.