cyanogene won't boot on Vodafone 32b - myTouch 3G, Magic Android Development

Hi guys.
yesterday i tried to install cyanogene mod.
because i had an perfect spl, i used a Goldcard and flashed this -> ROM v2.53.707.2 (Engineerings SPL v1.33.2010)
Everything worked fine. But then i tried to boot/flash the recovery mod but it didn't boot. I tried CM recovery and recovery-RA "G" then out of coriousity it tried the HTC version, and it worked. I thought i have to use the Google version for the 32B from Vodafone?
Anyway, then i wiped and flased HTC_ADP_1.6_DRC83_rooted_base.zip and then CM 4.2.5.
(i also only flased the HTC base rom without the CMod but it didnt boot either)
Then i rebooted and got stuck at the HTC MAgic screen forever. i waited like 10 minutes. i tried to make a nandriod backup -> restore but didnt worked either.
I dont know what to do =( now i'm back on original vodafone rom

Buddy, CyanogenMod is for 32A, Vodafone Magics are 32B, you won't be able to boot a 32A image on a 32B device. Sorry.

incredulous said:
Buddy, CyanogenMod is for 32A, Vodafone Magics are 32B, you won't be able to boot a 32A image on a 32B device. Sorry.
Click to expand...
Click to collapse
CyanogenMod is originally built for 32B/Dream users. There are updates that allow it to run on 32A.
Natively your phone should be able to run Cyanogen ROM, but you've somehow flashed the 32A radio, SPL and recovery onto your phone.
You need to get back to the 32B radio and recovery.
This should point you in the right direction.
http://forum.xda-developers.com/showthread.php?t=548834

huh? so why is there a tutorial on the Cyanogen Mod wiki für 32B devices?
--edit--
you mean i flashed a 32A cyanogene rom?
when i flashed via goldcard everything was fine. i could boot into the os

What I'm saying is that by flashing the HTC 2.53 update you've essentially turned your phone into a 32A with less memory. It will boot, but it won't be ideal.
You'd be much better off not using a goldcard for anything and going back to the 32B radio and the G recovery image.

ah okay.
but other methods didnt work for me, because of the SPL version. (wasnt able to boot recovery image from adb with this SPL [fastboot remote: not allow)])
this Relentless Rooter for Magic program didnt work on my pc

Related

Technical Think Tank for Bricked MyTouch3G / Magic

Mirror the similar thread in Dream forum, I started this thread as a constructive and positive place for those of us that have recently lost our MyTouch or Magic.
I am going to document the steps I took and hopefully reverse engineer this issue and also prevent other folks from doing the same mistake. This forum has been and good source of info. Thanks
What I did
Following [How-To] Root the T-Mobile myTouch 3G and I was able to flush to 2005 SPL and root successful as 32A rom.
Then I stop at "For Daredevils" and went with a different route.
I took the MT3G OTA (signed-opal-ota-150449.95700137.zip) and resigned it with test key and try to update it.
Update was done successfully and radio firmware updated at the same time and once reboot I got red screen of death.
What I got now
Red brick or Red screen of death
Power up while holding 'Back' button, volume down or any other button always result in Red Vodafone logo of death. I can't get to fastboot.
I can't get to recovery or fastboot which mean I can't do anything at all.
What I suspect
Flashing the radio (unclear what ver#) from MT3G OTA build (signed-opal-ota-150449.95700137.zip) might be that reason why it bricked.
Perhaps I probably should have followed the rest of the steps on "For Daredevils" and flash the ION radio and 32B RAv1.2.0G recovery, after that than trying to update with MT3G OTA without the radio.
I read somewhere in the forum (I forgot where), the reason why a bricked phone couldn't boot to SPL and not able to fastboot was because the radio firmware was loaded during SPL startup. Due to issue with loading radio firmware, SPL won't start properly.
Base on that, what we can try is to re-flash the radio firmware. How?
Maybe i can put the radio firmware as update.zip but how can i get the phone to load it when i can't fastboot
waacow said:
I read somewhere in the forum (I forgot where), the reason why a bricked phone couldn't boot to SPL and not able to fastboot was because the radio firmware was loaded during SPL startup. Due to issue with loading radio firmware, SPL won't start properly.
Base on that, what we can try is to re-flash the radio firmware. How?
Maybe i can put the radio firmware as update.zip but how can i get the phone to load it when i can't fastboot
Click to expand...
Click to collapse
It's my opinion. If there is a way, that probably (track ball)+(power), the only key combination we(?) can see .
Let's find a way!
waacow said:
What I suspect
Flashing the radio (unclear what ver#) from MT3G OTA build (signed-opal-ota-150449.95700137.zip) might be that reason why it bricked.
Perhaps I probably should have followed the rest of the steps on "For Daredevils" and flash the ION radio and 32B RAv1.2.0G recovery, after that than trying to update with MT3G OTA without the radio.
Click to expand...
Click to collapse
I think we have exactly same problem.
I'm sorry. I misunderstood. But I flashed ION radio. then...I got a pretty red brick!
I do not believe my phone is bricked but I believe it's pretty close...
My Rogers HTC Magic will not boot/load any recovery. I had a fully functional magic for several months using lots of different roms, however I developed a problem with one of the roms and after trying to install a new one, I can no longer boot any rom.
I can only boot into the fastboot screen, which says the following:
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP50000)
CPLD-12
RADIO-2.22.19.26I
Apr 20 2009,15:30:43
Everytime I try to either boot ANY (RA/cyan version) recoveries from either fastboot or flashing it, it does not want to start up.
I can flash just fine, however I do not know if anything is working correctly because only fastboot is accessible, everything else just sits at a rogers logo.
What should I do next?
drewX2 said:
I do not believe my phone is bricked but I believe it's pretty close...
My Rogers HTC Magic will not boot/load any recovery. I had a fully functional magic for several months using lots of different roms, however I developed a problem with one of the roms and after trying to install a new one, I can no longer boot any rom.
I can only boot into the fastboot screen, which says the following:
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP50000)
CPLD-12
RADIO-2.22.19.26I
Apr 20 2009,15:30:43
Everytime I try to either boot ANY (RA/cyan version) recoveries from either fastboot or flashing it, it does not want to start up.
I can flash just fine, however I do not know if anything is working correctly because only fastboot is accessible, everything else just sits at a rogers logo.
What should I do next?
Click to expand...
Click to collapse
fastboot flash radio <the correct radio>
Where do I find these radio files? And thanks for the help! I had no clue I needed to flash the radio
drewX2 said:
Where do I find these radio files? And thanks for the help! I had no clue I needed to flash the radio
Click to expand...
Click to collapse
you can get the radio img's from htc...
http://developer.htc.com/google-io-device.html
I have flashed the radio and still get only a rogers screen. I also have reflashed everything with original rogers magic files found on the forum (boot/system/userdata/recovery).
Still only have fastboot working
UPDATE: Got Recovery working. I flashed the radio/recovery from a givemeroot.zip I saw for those flashing the mt3g. I believe it can be used on this as well. Next step is to get a rom loaded
Flashed HardSPL and permabrick mt3g
I have been running Hero ROM's with no issues until today when I flashed a Hard SPL because I wanted to try Cyanogen latest. The new SPL bricked the phone, no power -splash- hboot, just a black screen.
The previous ROM's I have been flashing didn't need a new SPL. Are you not supposed to flash the SPL on the mt3g?
Thanks in advance for the input.
robotician said:
I think we have exactly same problem.
I'm sorry. I misunderstood. But I flashed ION radio. then...I got a pretty red brick!
Click to expand...
Click to collapse
Same thing happend to me too, followed the steps till the radio part, flashed the radio - red brick. luckily i manged to get mine exchanged.
edit: duh, sorry seemed to be a somewhat old post/topic
Any progress on this guys???
drewX2 said:
I do not believe my phone is bricked but I believe it's pretty close...
My Rogers HTC Magic will not boot/load any recovery. I had a fully functional magic for several months using lots of different roms, however I developed a problem with one of the roms and after trying to install a new one, I can no longer boot any rom.
I can only boot into the fastboot screen, which says the following:
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP50000)
CPLD-12
RADIO-2.22.19.26I
Apr 20 2009,15:30:43
Everytime I try to either boot ANY (RA/cyan version) recoveries from either fastboot or flashing it, it does not want to start up.
I can flash just fine, however I do not know if anything is working correctly because only fastboot is accessible, everything else just sits at a rogers logo.
What should I do next?
Click to expand...
Click to collapse
ummm... okay, I believe it could be easy goings here, if you go to one of the threads, which I believe you can find fairly easily, to switch radio/SPL through fastboot...
Rogers Magic should NOT use 2.22 radio, but either 3.22 or 6.35, unless of course you are using the dream, which is a different thing all together. Then, push the recovery you want (clockwork or amon RA), if after switch spl/radio, does not work. and voila, theres your fix
**NVM, didn't realize your question got answered

Help flashing new rom ?

im having trouble flashing a rom to my magic 32b everytime i flash a cutom rom it gets stuck on the htc magic screen
i have
Sapphire PVT 32B ENG S-OFF H
HBOOT-1.33.2010
Radio 3.22.20.17
i had to make a gold card because i had a perfect spl and have installed the engineers spl
can anyone help ir point me in the right direction ?
you would need to tell which rom your trying to get in, to be sure it would work with your config
capychimp said:
you would need to tell which rom your trying to get in, to be sure it would work with your config
Click to expand...
Click to collapse
i have tried a few diffrent roms
cynogens latest 4.2
stokes 1.4
and kingklixk rom 1.7.1
all have frozen on the same boot screen
PS i CAN get into fastboot recovery ect
pls check your messages i wrote you something there
just tried flashing a recovery rom G but it hung on htc screen then did the same with a H recovery it installed fine but then the rom hangs on boot screen :S
how can you change phone from a H to a G would this need a new sappimage flashed to it to change it ?
you should use the H recovery (i believe thats whatu need to use) did you flash the DRC83 for your phone befoer flashing CM? try using a port as well if necessary

I think I messed up my Magic.. help?

Hi everyone! I've been following some guides and what not (in order to install a new ROM- st0kes.v1.4.1). I have a 32B board (got it from Vodafone Australia).
I had the SPL that ended with 0009 (I think this was the 'Perfect' SPL?). Anyway, I slapped on the Engineering SPL 1.33.2010, or something like that (ends with 2010).
I tried RA's recovery rom through fastboot, v1.6.2G. As I understand it, those with the 32B board (and hence, a google branded phone) should use the 'G' version of RA's recovery rom. When I run it, command prompt tells me that everything goes okay. However, it leaves my phone hanging indefinitely on the splash screen that displays "HTC Magic". It doesn't even go to the recovery menu or anything. I have to take out the battery and put it back in to make the phone work again. I downloaded it 3-4 more times and tried (even checking the md5sum), and it still didn't work.
So, since the 'G' version didn't work, I tried the 'H' version. Command prompt tells me it boots okay, and this time, my phone at least goes past the splash screen and into the recovery menu. I had already copied over a ROM to my SD card and named it 'update.zip' (the st0kes.v1.4.1, which is 32B compatible). So I told the recovery rom to install the update.
Now, my phone just hangs at the "HTC Magic" splash screen forever when I boot it normally.
Can anyone help me? My phone is virtually unusable right now. I don't mind reverting back to an older version, if it's not possible to upgrade to the new ROM. And stupid me, didn't backup using nandroid.
Sorry if this has been answered before, but I cannot for the life of me find a solution. Thanks.
try restoring ur phone with nandroid backup
scumm said:
Can anyone help me? My phone is virtually unusable right now. I don't mind reverting back to an older version, if it's not possible to upgrade to the new ROM. And stupid me, didn't backup using nandroid.
Click to expand...
Click to collapse
Thanks anyway though~ :/
More info is needed, old or new radio? also it stands to reason if a 32a recovery works and not the 32b you should try a 32a rom for your radio.
If the H version of the recovery works then you probably flashed a 32A radio at some point during rooting hence you will need to apply a 32A port after every ROM OR flash back a 32B radio.
It says "RADIO-3.22.20.17". I have no idea what that is meant to be or mean. If it is a 32A radio, how can I apply a 32B radio?
I'm not sure when this could have happened either. It might have been when I was creating a goldcard (since I was getting the 'remote: not allow' crap).
Thanks for the quick replies~
Yes, thats a 32A radio. Your goldcard update flashed it (probably).
Get a 2.xx.xx.xx radio which is for 32B devices, connect your magic to a PC while in fastboot and in CMD type:
fastboot flash radio nameoftheradio.img
fastboot flash recovery Grecovery.img
then you will be able to flash any 32B ROM.
I would just try a 32a old radio rom to first make sure everything works first, and make damn sure you use fastboot (as eyegor said)and not recovery if you are going to flash a 32b radio
Thanks, you guys are legends
I flashed a 32B radio, and installed a new ROM (went with a 1.6 instead of the 2.1, 2.1 was too laggy and glitchy in my experience). Everything's fine now.
Thanks again

myTouch 1.2 32A/32B SPL/Radio/Kernel confusion

I've got a myTouch 3G/1.2/3.5mm headphone jack phone. Y'know, the 32A/B hybrid with extended RAM deal. I had SPL 1.33.0013d and radio 2.22.28.25 (I don't remember the process I used to upgrade to those), using SenseLX and decided to go back to COS-DS because the camcorder didn't work. Well, I superwiped, flashed it, Gapps, and the COS kernel. When I booted into the ROM, for some reason, I couldn't install anything via Market ("could not install to current location"), Superuser was working but nothing could actually attain root access, and WiFi wouldn't connect. So I superwiped again, and attempted to flash GRP-CM7.1, but kept getting a Status 7 code in recovery. Stumped, I decided to flash a Sappimg and start over. Now this is where it screws up.
The phone boots into a Cupcake ROM, which has non-responsive touchscreen controls. The current fastboot info is this:
Sapphire unknown 32B Eng S-off H
hboot 1.33.2010 (Sapp31000)
Clpd-13
Radio 3.22.20.17
Now, here's the problem. I can flash CWM recovery, reboot into it, but I can't flash GRP7.1, STILL. So I'm stuck with the Cupcake ROM. And once I flash the new radio and SPL, recovery won't load anymore, and neither will the ROM itself. What the hell is wrong with it?
UndeadSquirrel said:
I've got a myTouch 3G/1.2/3.5mm headphone jack phone. Y'know, the 32A/B hybrid with extended RAM deal. I had SPL 1.33.0013d and radio 2.22.28.25 (I don't remember the process I used to upgrade to those), using SenseLX and decided to go back to COS-DS because the camcorder didn't work. Well, I superwiped, flashed it, Gapps, and the COS kernel. When I booted into the ROM, for some reason, I couldn't install anything via Market ("could not install to current location"), Superuser was working but nothing could actually attain root access, and WiFi wouldn't connect. So I superwiped again, and attempted to flash GRP-CM7.1, but kept getting a Status 7 code in recovery. Stumped, I decided to flash a Sappimg and start over. Now this is where it screws up.
The phone boots into a Cupcake ROM, which has non-responsive touchscreen controls. The current fastboot info is this:
Sapphire unknown 32B Eng S-off H
hboot 1.33.2010 (Sapp31000)
Clpd-13
Radio 3.22.20.17
Now, here's the problem. I can flash CWM recovery, reboot into it, but I can't flash GRP7.1, STILL. So I'm stuck with the Cupcake ROM. And once I flash the new radio and SPL, recovery won't load anymore, and neither will the ROM itself. What the hell is wrong with it?
Click to expand...
Click to collapse
Make sure you flash a proper recovery. (I consider myself a noob. This post could contain a lot of incorrect info) you are currently using the 3.22 radio and are using ebi1 kernels and recoveries. Make sure you have the proper so and radio for your phone and a recovery that works with it.
In fastboot
Flash ebi0 recovery
Flash spl
Flash radio
Reboot
Now flash your rom
(Again I consider myself a noob and this info could easily be incorrect. Continue at your own risk)
The recovery is the correct one, for sure. As far as the radio and SPL, I don't know. I don't remember how I originally updated them, but these current ones I've been attempting to use don't seem to be working. I can't seem to find the official T-Mobile OTA update, either. I kinda figured if I can get that flashed, it would have the new radio and SPL flashed with it, then I can use Super1Click and root the phone again, then flash my custom recovery and ROM. But that OTA is nowhere to be found.
Ok, I finally got a ROM that flashed and booted (COS-DS again). Hopefully it doesn't have those weird issues again. Oh, wait. Jeez.... the phone thinks the headphones are plugged in. At least it seems the WiFi and sideloading/Market installs are working for now.
Attempting to flash GRP CM7.1 gives me a "assert failed: getprop("rro.bootloader") == "1.33.0013" .... "Status 7." Which is why I need that SPL.
Hmmmm... ok, I think I got somewhere here... I just found a SAPPIMG on my USB drive called "Sapphire_T-Mobile_US_2.10.531.4," which seems to be ROM my phone was shipped with. I flashed it in fastboot, booted up, connected to WiFi, and it automatically downloaded the T-Mobile 1.2 update to Android 2.2.1. I've installed it, looking good so far.
For now I've gotta run but later I will attempt to root it and install a custom recovery, nandroid backup, and attempt to flash a Gingerbread ROM and new kernel.
EDIT: I've uploaded it HERE.
UndeadSquirrel said:
Sapphire unknown 32B Eng S-off H
hboot 1.33.2010 (Sapp31000)
Clpd-13
Radio 3.22.20.17
Click to expand...
Click to collapse
While I see you solved it some way or other:
Usually 3.22 on a stock sapphire image is 32a.. but it will work obviously on a 32b phone. (actually may be officially this way on some carriers with both 32a/32b models to make the one rom support both versions but I'm not sure of this.. Verifone users however seem to frequently end up in the 3.22 radio on a 32b device)
Regardless of 32a/32b however while you have a 3.22 radio the kernel (both recovery and the rom) must be ebi1 .. its likely you got the right recovery; but the rom didn't have the ebi1 image.
The particular state mentioned however is a 32b unit with s=off 1.33.2010 SPL thus if you wanted from here to go to a 2708+ kernel the easiest way is the original 2708+ dream/sapphire instructions http://forum.xda-developers.com/showthread.php?t=831139
Just remember you must use fastboot to install the 2.22 radio when a 3.22 radio is currently installed or you may well brick your phone.
Yeah, I was hoping you could clear up the confusion with the 32A/B but what stumped me was, I had the radio and SPL before. And I followed your thread to update them again, but I couldn't get into/flash recovery or ROM afterwards no matter what I did. So now, I'm running the 2.2.1 T-Mobile ROM, 32A .0013 SPL and 28.25 radio, got it rooted. So now I just need to flash a recovery, but I'm kind of hesitant to do so until I know for sure how to progress from this point. Any tips?
EDIT: Got it. I used ROM Manager to flash CWM recovery (the ION/myTouch one worked), and flash the GRP CM 7.1 port. Annoyingly enough, the camera STILL causes a reboot after taking a photo. Fffffuuuuuuuuuuu.......!!! Eh, whatever.
EDIT: Flashed ezTerry's ezBiff 2708 kernel, which even though it worked for me fine before, caused an infinite boot loop (it made it briefly to the desktop each time and rebooted, for some reason). The ebi0 kernel, which went through a couple reboots, seemed to fix the camera again, but no extra RAM.
EDIT: Wait. WiFi is broken. Settings simply state, "Error". USB connection won't even allow me to mount the SD card. My phone is a retard! Ebi0 is a no-go.
Yet another edit: ClockworkMod-flashed ezTerry's ezGBv1.5 kernel. Everything's working fine now. Though still no extra RAM. Hmmm... Terry? Did I get something mixed up here? It worked fine before...
Arrrgh, I am SO confused!
Hope this thread can provide some helpful info to anyone else who may screw up the way I did!

[Q] Magic 32a Recovery/Flash Issue

Hoping someone can help. I have a magic 32a. I was running cyanogen 6.0, or 6.1 I believe, and I thought it was time to change. In the mix of trying to install new ROM, I did an SD wipe and removed my backups....
I downloaded SDK tools and I have done everything I possibly can, so I'm looking for help.
SAPPHIRE PVT ENG S-OFF H
HBOOT-1.76.2007 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
I had the old radio and SPL, but then I couldn't reboot into recovery. I FINALLY got the radio flashed, and it took my ability to enter recovery away( Amon Ra, don't remember what version).
Now I'm trying the new radio, but every time I try and flash the radio my phone freezes in the middle of the flash. The SPL flashed just fine, but now I can't even boot into recovery and even trying to boot it sticks on the mytouch screen.
My question is, do I have the wrong spl/radio combo, which one I might need, or any ideas on how to get my phone running again.
Thanks.
Alright I got the new radio to flash. Everytime I flash a recovery, it flashes no problem, but gets stuck when I try and boot into recovery....I don't get it.

Categories

Resources