Another total brick? magic vodafone spain - myTouch 3G, Magic General

Heloo, while y was trying to update my perfect spl, i meka a mistake and put inside spl for 32A instead o B
now, when I press power on button, it makes a little vibration and after that HTC MAGIC appears on the screen and nothin happens.
I have try to make fast boot commands, when starting with back and power, but computer foesn't recognize it.
Any suggestions??
the problem is the first splash is changed and is not vodafone's one, and I cannot access to it

What spl did you get? If you got it from Amon_Ra, his spl's work for both 32A and 32B. Are you sure you didn't flash a 32B radio?
What commands did you use?

recovery-RA-magic-v1.3.2H.img I use this one and it works, but on the next step, when i was trying to put
update.Engineering-SPL-HBOOT-1.33.2010-signed
using the recovery, it ask me for press 2 keys for rebooting. I read that in a wrong way and I press menu and use the menu for reboot the magic. After that it hangs on the first screen and I cannot use the fastboot commands, trying to boot with back+power.
I read it can be done if the first splash freezes but it is not my case.
Thanks a lot for your reply

Hmm, try installing HTC sync with the drivers again.
And download a recovery rom 1.4 with nandroid backup and download that into your fastboot.

No way to do a fastboot or recovery so I think that we can't download into our fastboot...
I have same problem and reading in the forum I think that we have Total bricked phone.
I have tried this solution http://forum.xda-developers.com/showthread.php?t=571457 but the cmd still "waiting for device" so i can't acces to my magic with my pc...
I hope that i am wrong

yes, I have try what people says on that post and waiting...
is not possible to make anything to allow the computer to recognize the device??

Related

Probs with getting into recovery menu

Hey XDA
Im having a little problem with my Magic.
I would like to flash a new ROM, but i cant get into the recovery menu.
Here is what i do:
I have installed the latest version of SDK on my computer.
I then connect my Magic with the cable, and when Vista comes up with the note saying that want to install the software i tell it to use the drivers that are in the SDK/usb_driver/x86 folder.
I then turn off the phone, and press and hold back button + power button until the phone shows the "3 androids on skateboard" menu.
Then on my computer in the cmd prompt i write: fastboot boot recovery.img, and the the cmd prompt says: <waiting for device> and the nothing else happens, the recovery image dosn't show up on the phone either.
I have checked with adb devices that my phone is connected.
Are there anyone that can help me with this problem because its beginning to annoy me alot, i would like to root my phone and flash another ROM.
So any help would be much appreciated.
Per
Just to check, you made sure you have a spl that's rootable?
http://forum.xda-developers.com/showthread.php?t=529019
And fallowed this before fastboot.
First, setting up your PC (I'm going to assume you're using windows for this) to work with Android in a debugging enviroment.
1. Get the latest Android SDK from here (http://developer.android.com/sdk/1.5_r2/index.html) and unzip it into a convienent directory (most people use C:\Android\, so I suggest you do the same). The result should be something along the lines of C:\Android\android-sdk-windows-1.5_r2\.
2. Set up your phone to work with debugging drivers. The method of doing so can be found here (http://developer.android.com/guide/...ing/device.html) in the "Setting up a Device for Development" section, steps 2 and 3. To test that it works properly, open up a command prompt and navigate to the tools directory (C:\Android\android-sdk-windows-1.5_r2\tools). Type into the prompt:
Code:
adb devices
If it returns your device and serial number, then you're all set.
3. Lastly, grab fastboot.exe from here (http://www.htc.com/www/support/android/adp.html) and place it in the tools directory of the sdk.
Next up, rooting.
Clinton
Thx for the answer, but there is a problem with one of the links you posted, the last one of them (http://developer.android.com/guide/...ing/device.html). it dosn't work.
But you also write something about the SPL, i dont know if i have the right SPL, how can I see if its the right one i have? I've tried reading the link about the SPL, but my problem is that i cant even get into the recovery menu, so i cant flash a new SPL either, or am i wrong?
Please help me
Per
To check your SPL just boot up fastboot (back + power) then just look at the top and see what it says. Then check on the first link I posted and see if your SPL is rootable or not.
Don't know why the last link didn't post proper Here it is.
Clinton
perevers said:
Hey XDA
Im having a little problem with my Magic.
I would like to flash a new ROM, but i cant get into the recovery menu.
Here is what i do:
I have installed the latest version of SDK on my computer.
I then connect my Magic with the cable, and when Vista comes up with the note saying that want to install the software i tell it to use the drivers that are in the SDK/usb_driver/x86 folder.
I then turn off the phone, and press and hold back button + power button until the phone shows the "3 androids on skateboard" menu.
Then on my computer in the cmd prompt i write: fastboot boot recovery.img, and the the cmd prompt says: <waiting for device> and the nothing else happens, the recovery image dosn't show up on the phone either.
I have checked with adb devices that my phone is connected.
Are there anyone that can help me with this problem because its beginning to annoy me alot, i would like to root my phone and flash another ROM.
So any help would be much appreciated.
Per
Click to expand...
Click to collapse
Sound like you're not using the right Recovery .img
Check here to start with: http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec03
ClintonH said:
To check your SPL just boot up fastboot (back + power) then just look at the top and see what it says. Then check on the first link I posted and see if your SPL is rootable or not.
Don't know why the last link didn't post proper Here it is.
Clinton
Click to expand...
Click to collapse
I have the: SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0010 (SAPP10000)
CPLD-12
If what im reading at the first link is correct, my SPL cant be root'et, or im not reading the first link correctly?
And if i need a new SPL, how do i flash that one? and what SPL should i choose? and last, how can i then get my SPL back to how it is now if i need to get the phone to repair?
Per
antonram said:
Sound like you're not using the right Recovery .img
Check here to start with: http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec03
Click to expand...
Click to collapse
I am using the right recovery image, i also tried the one you linked, that didn't work either
Per
perevers said:
I have the: SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0010 (SAPP10000)
CPLD-12
If what im reading at the first link is correct, my SPL cant be root'et, or im not reading the first link correctly?
Per
Click to expand...
Click to collapse
Afraid your not going to be able to root right now. It's in the works though so it might be soon.
Clinton
ClintonH said:
Afraid your not going to be able to root right now. It's in the works though so it might be soon.
Clinton
Click to expand...
Click to collapse
Damn, thats a load of ..... (sorry).
I have just got my phone back from the repair shop because the camera restarted the phone everytime i tried to use it. Before i sent it to repair i had no problem rooting it or getting in the recovery menu.
But can you tell what the problem is? is it because the recovery image dosn't work with my SPl and the recovery image guys need to "crack" my SPL first or what?
Per
perevers said:
Damn, thats a load of ..... (sorry).
I have just got my phone back from the repair shop because the camera restarted the phone everytime i tried to use it. Before i sent it to repair i had no problem rooting it or getting in the recovery menu.
But can you tell what the problem is? is it because the recovery image dosn't work with my SPl and the recovery image guys need to "crack" my SPL first or what?
Per
Click to expand...
Click to collapse
Here you go read This on the SPL. By the way which phone do you have? Is it a Rogers Magic? Just good to know what's not rootable, you should post your phone details in that thread if it's something not listed on the first page.
Clinton
ClintonH said:
Here you go read This on the SPL. By the way which phone do you have? Is it a Rogers Magic? Just good to know what's not rootable, you should post your phone details in that thread if it's something not listed on the first page.
Clinton
Click to expand...
Click to collapse
Its a HTC branded magic, dont know if its a rogers. But im from Denmark, and bought it in Denmark. dont know if that helps.
Thx for the help, will read the thread.
Btw. can you tell where i can see how far they are in "cracking" this SPL?
Per

Magic Docomo bricked

There wasn't any info that was an exact fit for the Docomo, but I gave it a go.
It's a 32B SAP2000
It had a perfected SPL 1.33.0006, so I flashed a 1.33.0009 SPL.
It got to Fastboot, but now showed H instead of G and the radio was different.
Fastbooted into RA's 1.5.2 recovery.
Instead of applying my nandroid backup I thought I'd apply the radio from HTC site. The one for 32B.
Rebooted to the unboxing screen for 20 seconds, then back to HTC Magic splash screen.
Since then I can't get fasboot or recovery.
Putting in the battery causes the phone to instantly vibrate a little and come on.
Holding the different combinations of buttons whilst the cable is connected/unconnceted does nothing.
I can't issue fastboot commands via cmd prompt.
Hmm... this seems like a challenge, no? Anyone think they know where to even begin to de-brick this?!
No challenge, it's impossible! unfortunately once you've bricked it only HTC can help. Try to get it replaced if it's under warranty (tell them that you've tried to install an official update and that something went wrong).
No fastboot (back+power) or recovery (home+power) = dead phone
Shame. Ah well. Time to bid on another one!
This time I'll hunt down with Android 1.5; will make life so much easier!

No! I bricked my phone!!

I just rooted my Mytouch a couple days ago and everything worked perfect and i did it without bricking my phone. I was trying to get the supercsdiv4 rom, but i needed to flash the lateset radio and heres where the problem started. the radio tried to flash was 2.22.23.02. I used the recovery image to flash it and then when i rebooted the phone it stayed stuck at the splash screen and i cant get into fastboot or recovery anymore. it just boot to the splash screen and stays there. I know i cant get my phone back but i want to know what i did wrong so that i dont ever do it again. maybe it was because the radio i had was a 32a radio and this radio i tried to flash might have been 32b but im not sure why that wouldn't work if my phone is 32b
here was my system
pvt 32b
Hboot 1.33.2005
radio 3.22.20.17
have you tried taking the battery out for a bit.. relax a while, then put it back in and try to get into recovery mode (home and power)
this actually happened yesterday and my phone was off the whole time so it has had plenty of time to rest. My phone is truly bricked
well im sorry to hear that, but i have no idea what you did wrong, unless you did flash a 32a over a 32b or the other way around, im sure that could really mess up the phone.
may be a useless idea but have you tried a hard reset
1. With the phone turned off, press and hold the HOME and BACK buttons.
2. Briefly press the END CALL/POWER button while continuing to press the HOME and BACK buttons.
3. When you see the screen with the 3 Android
images, release the HOME and BACK buttons, and then press the TRACKBALL.
i have no idea if it will do anything but might as well explore EVERYTHING.
Similar Problem (Partial Brick?)
Not to take anything away from clint1225 but
I have a similar problem and didn't want to start another thread.
I tried unrooting my devices using the method
described at theUnlockr.com. Everything was fine up until I tried using
their sappimg file (said it worked for all old magics).
At the hboot stage, it found the sappimg but the update failed.
However, the magic now says:
SPL-1.33.0006 (SAP50000)
Radio- 2.22.19.261
Ship S-On G.
It's a 32A version.
I had an engineering spl and 6.35xx radio before I attempted to unroot.
Oh I'm not able to access recovery but I can access
fastboot (computer can't find it though under "fastboot devices")
Other than that, it's stuck at the first splash screen.
Any advice/tips?
Sorry for the long post and thank you.
Good luck to you too, clint1225!
UPDATE *Similar Problem (Partial Brick?)*
In the adb, the serial number
of the htc magic is coming
up under "fastboot devices".
However, if I try to
flash a recovery for example, the adb
returns "remote access not allowed".
I've read about the gold card method
but my phone won't boot up properly
(stuck at splash screen) and I can't
access recovery. Only fastboot seems to be
working.
Any help is greatly appreciated.
Thanks!
Take it for what it's worth coming from a newb. But from my understanding if you can reach your phone with Fastboot your a NOT bricked. But this is what I have heard here on XDA, I haven't proven this myself.
Check around and hopefully with fastboot you can get your phone back. Good luck.
I did the exact same thing a few weeks back. I flashed a 3.22 radio over my 2.22 radio, thinking it's an upgrade but after it reboots, it wont get past the logo screen. I spent the whole day trying to find ways to recover it but cannot find any. Thank god I have warrenty on it so I went to the Tmobile store, told them I updated it and when it restart, it got stuck on the logo screen. They gave me a new phone and told me dont f-up this one. Now I'm afraid of updating my phone to the 6.something radio.
Update *Similar Problem (Partial Brick?)*...again.
MasterColdSoul and koolpre,
Thanks for the tips and luck!
I figured it wasn't a total brick so I searched
the whole day on google and xda.
What I can tell you is that I now have a functional phone.
I used the rogers "mandatory" update (2 sappimgs) to
get my phone (rogers 32a) working again (boots fully).
However, I now have the SPL 1.76.0010 which means
I've lost root functionality and it's harder to get root.
But I could use the phone to make a gold card and get root again.
Boy I'm glad this worked! I should have learned my lesson
but I will probably try to root, hehe!
Thanks to google search and xda community!
koolpre said:
I did the exact same thing a few weeks back. I flashed a 3.22 radio over my 2.22 radio, thinking it's an upgrade but after it reboots, it wont get past the logo screen. I spent the whole day trying to find ways to recover it but cannot find any. Thank god I have warrenty on it so I went to the Tmobile store, told them I updated it and when it restart, it got stuck on the logo screen. They gave me a new phone and told me dont f-up this one. Now I'm afraid of updating my phone to the 6.something radio.
Click to expand...
Click to collapse
just because the radio starts with bigger numbers doesn't make it an update. 3.22 was the old radio and 2.33.23.02 is the latest radio so you were actually downgrading your radio and thats why your phone brick. Just letting you know because you seem to be under the wrong impression. Dont make that mistake again. just do a little research to find the latest radio.

[Q] mt3g 1.2 stuck at boot screen

Yesterday I went ahead and tried to flash the new 2.22.27.08 radio for my mt3g 1.2. I thought I read some posts saying that it is compatible with the mt3g 1.2. after flashing the radio and rebooting, my phone became stuck at the htc magic boot screen.
I no longer am able to enter recovery (home + power) or hboot (vol down + power)
the only thing I can do is access fastboot commands: when I power on the device, at the top of the boot screen is says "fastboot usb"
fastboot devices shows my device but my spl is perfect spl with s=on so I cant flash any img files. Ive tried flashing all the partitions, even with a zip file but I get the same errors, remote: not allow.
I tried installing with RUU and the command "fastboot oem rebootRUU" but the RUU app cannot find the connected usb device.
a lot of posts suggest to make a goldcard and put the SAPPIMG.zip on sdcard and let it fastboot auto load the file, since vol down + power doesnt work for me i thought this wasnt an option.
here is my phone info:
pvt 32a ship s-on g
hboot 1.33.0013
cpld 13
radio 2.22.27.08
anyone have any suggestions?
I would hate if the phone was unrecoverable but it is an old phone, maybe time to upgrade.
cloths55 said:
Yesterday I went ahead and tried to flash the new 2.22.27.08 radio for my mt3g 1.2. I thought I read some posts saying that it is compatible with the mt3g 1.2. after flashing the radio and rebooting, my phone became stuck at the htc magic boot screen.
I no longer am able to enter recovery (home + power) or hboot (vol down + power)
the only thing I can do is access fastboot commands: when I power on the device, at the top of the boot screen is says "fastboot usb"
fastboot devices shows my device but my spl is perfect spl with s=on so I cant flash any img files. Ive tried flashing all the partitions, even with a zip file but I get the same errors, remote: not allow.
I tried installing with RUU and the command "fastboot oem rebootRUU" but the RUU app cannot find the connected usb device.
a lot of posts suggest to make a goldcard and put the SAPPIMG.zip on sdcard and let it fastboot auto load the file, since vol down + power doesnt work for me i thought this wasnt an option.
here is my phone info:
pvt 32a ship s-on g
hboot 1.33.0013
cpld 13
radio 2.22.27.08
anyone have any suggestions?
I would hate if the phone was unrecoverable but it is an old phone, maybe time to upgrade.
Click to expand...
Click to collapse
Goldcard method. If you cannot access the bootloader, have no recovery and phone will not start then you just bricked your phone.
Make the goldcard, do a battery pull, put the goldcard in, hold the volume down button, put the battery in and power on the device while holding the volume down button. If it boots to a white screen then your in luck. If not then ask for a new phone for the Holidays.
Binary100100 said:
Goldcard method. If you cannot access the bootloader, have no recovery and phone will not start then you just bricked your phone.
Make the goldcard, do a battery pull, put the goldcard in, hold the volume down button, put the battery in and power on the device while holding the volume down button. If it boots to a white screen then your in luck. If not then ask for a new phone for the Holidays.
Click to expand...
Click to collapse
Thank you for the replay. I just made a goldcard and tried your suggestion but didnt work I also tried different combos of battery pull/ vol down + power. no dice. I guess im sol for now.
thanks again for the reply.
EDIT: haha ya I bricked my phone just in time for the holidays! Cant complain when getting a new phone I guess. I might pick up a jtag kit and try to unbrick the 1.2, just for fun though

[Q] HELP - Magic 32a Bricked! weird + Bad

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...

Categories

Resources