Is there a chance for my (new) Magic ? - myTouch 3G, Magic General

Hi all,
Well, that's the way, it sometimes goes....
On Tuesday i received in exchange my new Vodafone Magic. After only two days i'm stuck with a "deadlock" situation. Following happened:
The Magic was delivered with the standard 1.6 Donut on it. I then manually flashed the OTA update to 2.1.1 and the apps that I use regularly. Yesterday I used the "Gingerbread.apk from the XDA forum to gain root. Armed with root, i downloaded Rom-Manager from the Market and installed ist. Next, i installed the Clockwork Recovery via Rom-Manager. Then reboot into the recovery and Voila .... Clockwork recovery.
Ok, first thing i did was to make a backup of my current ROM and then came the big mistake ...
I wanted to have a black Notficationbar in OTA. So i flashed "blackbar.zip" from "http://www50.zippyshare.com/d/43974308/12150/blackbar.zip". But after reboot it didn't work (Bootloop).
Well, I thought I reboot back into the recovery and restore my backup.
And then came the shock ...
What I saw then was not the Clockwork recovery but the original HTC Magic recovery.
Ok, tried to flash the 2nd part of the OTA Update again.... Nope. The HTC Recovery reports "Assert Failure". Obviously checksum tests are done and after flasing the blackbar, "framework-res" no longer matches the checksum.
OK, so back to 1.6 with the NBH Image .... Nope, The Magic reads the image, but refuses to install with the comment "main version is older"
Since the OTA update, installs an "S-ON" Spl, no more fastboot...
Searched in Google and found a lot of Posts saying "try using this image", "try using that image", but nothing worked.
So the Situation now is as follows:
- Magic can not start anymore. Bootloop in the "android" Bootscreen
- Fast boot is not possible because of the SPL
- New import of the OTA update, part 2 not possible due to checksum error
- Back to 1.6 not possible due to "Main version older"
- I only have the the original Magic Recovery. (and of course can boot into HBOOT / FASTBOOT mode)
What I would need would be a flash-ready image of Enginnering SPL or an update, however, in the format, which is accepted by the original recovery of the Magic. I also dealt with the idea of creating a Goldcard. Could this be a way to save my Magic?
Has anyone else an idea, or anyone knows how to create a flash-ready image, which is accepted by the original recovery?
Thanks and greetings. lagloose

Is this a 32B or 32A? I've been in that situation before. If you can get into fastboot you can save it. Get a RUU (for 32A I used 3.5.401 from Rogers) and install it. In the process, it'll try to get the phone into fastboot mode, but it's already there, so you'll factory-reset it. After that, you can apply an Engineering SPL through update.zip (using the recovery from the RUU itself, not AmonRa or others's) and then you can do anything else you want on your device.
Good luck! ^^.

I think you're going to have to make a goldcard, which is a problem since you can't boot. If you can somehow make (find?) a goldcard then you should be able to flash a RUU. Can you post you're device specs? Vodafone Magics are supposed to be 32A's right?

I don 't know your phone information,but i think you need a goldcard and flash ruu

Related

Flashing problem on Magic_Rogers 3.54.631 rom

hi everybody!
some days ago i flashed my magic (TIM Italy, so 32A) whit the Magic_Rogers3.54.631.3 rom, that was a ruu exe file.
It flashed my spl and radio, that now are hboot-1.76.0010 (SAPP10000) and 6.35.16.19.
Now i wanted to change rom because of the language (i'm not able to put an italian dictionary when i write), but i don't succeed.. i tried to reflash the recovery, but i can't because fastboot says that is not possible to send data to the phone, so i can't also boot some recovery image.. same problem via adb or via terminal on the phone.
i rooted the phone with the last universal androot, but it's the same..
i succeeded to change recovery only with rom manager, but the phone doesn't go in recovery mode (it's still on the "rogers" splash screen), or if it goes, it reboot alone after a few seconds.
oh, at last, i'm not able to flash other rom, like the RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver or my original TIM rom.
I'll be really grateful to who will help me!!
thanks for reading!
download this application FlashRec
install it to your device
then download any of Amon_RA recovery imgs (HERE) (Choose the correct one for your device)
then push it to your sdcard
then open the FlashRec and press backup,
then write in the blank box "sdcard/xxxxx.img"
where xxxxx is the name of the img you pushed to your SD
then press flash .. if it is successful, connect your phone to adb
and write "adb shell reboot recovery"
I tried this on 32A 1.33.0010 and Radio 3.22,
I'm NOT 100% sure it will work with you,
try it at your own risk.
it says "phone type is EBI1/32A"
i press backup with or without the name in the box,and the result is
"backup failed: could not run command."
first: this is the false place for this thread. this is for general!
second:
follow this thread http://forum.xda-developers.com/showthread.php?t=756918
it is not possible to flash or backup with flashrec. the new roms are bugfixed.
renedlog said:
first: this is the false place for this thread. this is for general!
second:
follow this thread http://forum.xda-developers.com/showthread.php?t=756918
it is not possible to flash or backup with flashrec. the new roms are bugfixed.
Click to expand...
Click to collapse
I think you are right, because i was on stock 1.5 when i used this method.
OmarAta said:
I think you are right, because i was on stock 1.5 when i used this method.
Click to expand...
Click to collapse
me too... but the htc magic 32a with the actual stock rom, android 1.5 with sense form january, is already bugfixed.
Moving to General
sorry for the mistake, i thought it was the right section..
anyway i followed the guide in the post linked by renedlog and.. it worked!!! i didn't know where to put the flash_image file.. but it was written there.. so i did all, and now my rom is the RCMagic 5.0!
do you think it's good to try something different?
i use RCMagic 4.2
the version 5 is still a little buggy with the wake up from standby.
i will upgrade to an android 2.2 rom, if there is an update today for the 32B and hopefully it will be patched to my 32A.
yeah, i saw that bug.. it's really a pity, the rom was a little faster than the 4.2..
i suppose it would not be a big bug, so i hope somebody that is able will fix it!!
are there so big changes beetwen the 2.1 and 2.2?

[Q] Please help!! I may have messed up my MT3G!!

Okay, so I installed a radio version 2.22.27.08 via clockwork recovery on my 32A device when it should be only used on 32B!!!! I wanted to use yoshi's rom and I followed the directions but must have clicked on the wrong one!
I downloaded the old radio (3.22....) and tried to flash it via fastboot (it only comes in a .img file) but it keeps failing on the signature!
Is there anything I can do to downgrade to that radio?
I made a nandroid backup and my phone still works fine with the wrong radio, but I am not able to install another rom that I want!
Give us complete fastboot info

want shipped hboot and rom with s-on

hey guyz...
i have rooted my device with AlphaRev X and downgrade my hboot to 1.01.0001.
now i have a problem with the touch while in the dial-pad, I'm not able to dial the 4 5 6 row buttons(even in the all apps menu) , the touch isn't responding. I have a 1 yr warranty for my phone.
So i want to avail the warranty.
there is only 1 service center near to my place Andhra Pradesh, India which really sucks(i have been there twice) and i dont want to mess up.
Can i get the original HBOOT and S-on with the shipped rom on my phone so that i can avail the warranty easily.
Thnxxx...
First, restore your Stock ROM and/or flash the RUU. This will remove any Custom ROM's and will also remove Clockworkmod Recovery. Now, the only thing left is to remove AlphaRev's HBoot with the Stock HBoot
Download this OTA ZIP from Shipped ROM's:
OTA_Buzz_Froyo_hTC_Asia_India_2.25.720.1-1.25.720.1_release_161546bwou4mclajggz2mu.zip
Extract the HBoot image from this Zip. It will have a name like Hboot_xxxxx_.nb0
Once you have the stock HBoot file from the ZIP, follow this guide to remove AlphaRev's HBoot and install the Stock HBoot you just extracted:
http://forum.xda-developers.com/showthread.php?t=1160251
That's it.
NOTE - Make sure you are performing this last, i.e. after you have got back the Stock ROM and removed Clockworkmod. Once you are S-ON and have not removed these, it just may be a bit more of a hassle.
Yes. Download the Indian eclair RUU (the one with recent build number). Flash it.
Then use the fastboot command which allows for downgrade (check dev section). Then flash the hboot 0.80 from the above downloaded ruu.
Now just it to warranty. Or u can even do a froyo ota update and give to warranty. Perfect stock.
Edit: oops. Either way. Never mind.
Sent from my Blade using XDA App
OTA_Buzz_Froyo_hTC_Asia_India_2.25.720.1-1.25.720.1_release_161546bwou4mclajggz2mu.zip
is not working..
so i downloaded the RUU ROM and installed it from my PC.
the version is 2.1 update 1.
all the home screens are empty. and im not getting the setup menu after the reset i.e. setup ur account etc. i tried manually also its not working,,,..
right now im updating it from the phone (software update-might to to 2.2).
hope it works..
That was only to extract the India specific HBoot 1.01.0002 file. To actually install the zip, you have to rename it to update.zip, place it on the SDCard and use the stock recovery to install.
thank a ton u guyz...
finally i got it..
will go to the service center now

Booting stuck on HTC logo

Hello,
I want to install custom ROM on my Desire HD. I had some problems, which thanks to forum member, I have solved ( this thread ). I found that I can unlock my device to install custom ROM's using htcdev.com site. I have done everything, what I had to do. On HBOOT now I have *** UNLOCKED *** on the top, but still I have S-ON. I installed root-test application, where was the message, that phone has root. Then I have installed EXT4 recovery and Blackout ICS v 3.0. After that, booting stuck on HTC logo and nothing happens. I tried with other ROM's and theres the same issue. I can't use RUU files also - it throws an error when it's checking signatures.
What I supposed to do ?
Cause the flashing method is different if you were to have s-off. You need to extract the boot image and do it that way. That's about all I know.
Sent from a dream.
Thanks a lot!!!
I have flashed boot.img from extracted zip file by fastboot and now everything works fine.

[Q] Cannot boot into any custom ROM!

A friend of mine wanted to change the stock rom on his old tmobile MyTouch 4G to CM7.2
It is currently running the latest 2.3.4 (hboot_0.89.0007, radio 12.62.60.27_26.13.04.19), I unlocked the phone following the steps from HTC Dev website. And they explained that unlocking is enough to flash custom rom since it enabled write access to recovery, system and boot http://www.htcdev.com/bootloader/about_unlock_process.
I was able to flash and run both TWRP and CWM (twrp2.2.2.1-glacier-recovery & recovery-clockwork-touch-5.8.1.0-glacier) adn used them to flash CM7.2 stable and the latest nightly and some other custom ROMs i found on the developers forum at XDA, however, not of them do boot. The phone will get stock at the first screen showing Tmobile and myTouch 4g logo.
I followed many threads/steps that recommended downgrading to stock froyo first to turn security off (S-OFF) but it won't let me since it is older version, then some says to downgrade the radio first, but that is also not possible with S-ON and i get signature error. i tried doing it from the sd-card using the file name "PD15IMG.zip" for the stock rom but didn't work neither from the fastboot rebootRUU thingy.
From the recovery i wiped every thing even system, then checked it to make sure it is empty, flashed CM7.2 and mounted system and there are the files as they should be but it won't boot, and "adb devices" won't show anything so i cannot see the log. which means it didn't even start.
Am I missing something trivial?
* BTW, i had to lock the bootloader again to flash the stock 2.3.4 back, but I have the unlock token "Unlock_code.bin" and I can unlock it again if someone knows the answer to this problem

Categories

Resources