I don't know what had happened to my magic, but when i try to turn on it, it will not boot properly and stay at the HTC logo startup....
I know I able to factory reset the MAGIC, but that it will be very painful to me as those data will be wiped off...
Can any expert give me help? Is there anyway to solve this problem without losing all my data inside the magic??
are you on a custom ROM?
I am sure everyone will need a lot more info to help you.
so here is a basic list
1. Type (32A/32B)
2. Current ROM
3. Did you flash anything before it became that way? (SPL/RADIO/ROM/Theme)
connect your phone via usb (no need to mount) start the adb app with cmd and type 'adb logcat' you can see whats going on see if your getting errors
i flashed a rom and it took about 8 min to get to the home screen
I have a sapphire (32B)
With a Rav 1.???g recovery.
I tried updating my SPL but my phone didn't reboot after flashing now I get nothing. Did I brick my phone?
technubi : i think you did. But i could be wrong (i hope i am)
Related
Hey everyone,
i was trying to root my HTC Magic, following this guide:
http://android-dls.com/wiki/index.php?title=Magic_Rooting
i installed RAv1.2.0 : Modded ION recovery! (the H version)
used fastboot
fastboot boot recovery-new.img
then i told it to update from the update.zip that i put on the microSD card.
it said it finished loading the firmware, i did a reset, and now the phone wont load
its just stuck in the "HTC Magic" message that it does when loading, and dosnt get out of it.
I tried doing a battery pull, dosnt solve it.
i can still get into fastboot mode.
Can anyone tell me what i did wrong and how to recover my phone?
thanks.
BTW, my phone is rev 32A
OK, i fixed my issue,
connected my microSD to another phone, put the version
[Updated 7/22] [ROM] RAv1.1.0 (HTC branded Magics)
Can anyone tell me whats the most recommended version?
maybe something with multitouch?
I liked the original one as well
but i needed root to install the hebrew fonts
Hello there,
I got my HTC Magic (from belgian operator "Proximus") stuck on the first boot sceen. I can no longer acces the fastboot nor recovery.
The only thing i can do is put the phone in radio bootloader (screen off + blue led).
I have searched the forums alot and some have reported being able to send fastboot comands in this state but i did not manage so as the fastboot shell waits for the phone...
Here is what i got installed / did:
- rooted
- cyanogen mod 4.1.3
** t this point the phone was working great and used several months. then i tryed the following: **
- recovery-RA-sapphire-v1.5.2H.img (worked, wiped the memory and installed the following from here)
- signed-google-ion-ota-14721 (installation worked, auoupdate the radio, reboots and...just the logo) I intended to then go to cyanogen 4.1.9
Any idea what went wrong and even better, if i can make the phone boot again ?
Thanks in advance for your help !
What probably went wrong is that you installed a 32B Radio (the ion's) on a 32A device.
Now if you can't get into fastboot, hboot or recovery then there isn't anything you can do, unfortunately
Try to get the device replaced if it's still under warranty.
pelaon said:
Hello there,
I got my HTC Magic (from belgian operator "Proximus") stuck on the first boot sceen. I can no longer acces the fastboot nor recovery.
The only thing i can do is put the phone in radio bootloader (screen off + blue led).
I have searched the forums alot and some have reported being able to send fastboot comands in this state but i did not manage so as the fastboot shell waits for the phone...
Here is what i got installed / did:
- rooted
- cyanogen mod 4.1.3
** t this point the phone was working great and used several months. then i tryed the following: **
- recovery-RA-sapphire-v1.5.2H.img (worked, wiped the memory and installed the following from here)
- signed-google-ion-ota-14721 (installation worked, auoupdate the radio, reboots and...just the logo) I intended to then go to cyanogen 4.1.9
Any idea what went wrong and even better, if i can make the phone boot again ?
Thanks in advance for your help !
Click to expand...
Click to collapse
I'm pretty sure your phone is finished but you didn't happen to mention what you were doing in the first place? Were you just updating your ROM or flashing a new Radio?
Hum, i fear it has become a very expensive white brick indeed.
I confirm it was a 32A...and i tryed to flash an ion rom wich is 32B.. gasp !
My bad... sould have waited to have my head clear before doing this :/
i'll try to see if i can get the unit replaced/fixed by official means..but idoubt it
Anyone interrested by replacement parts ?
Oh, and what is the radio bootloader mode for (action+power => blue led)...?
Several qustions as i am deseperately trying to revive my Magic:
- Is there anyway to make the phone pick up a special boot on the sdcard Without accessing recovery/fastboot ? If so what file do i need on the sdcard (sappimg ?)
- What is the radio bootloader mode for ???
Try to connect your phone to your computer using USB. Start it in different ways, and see if fastboot or adb finds your phone. As you said you can start it in radio bootloader, try boot in that too, to see if fastboot or adb finds your phone.
If it does, post your radio and hboot, maybe I can help.
Did try all possible boot method, but the phone never registers on the usb with fastboot or adb. It just keeps showing me the operator splashpage.
The last thing i installed on the phone was the "signed-google-ion-ota-14721" (now i see this was for 32B...didn't pay attention enough that day). This overrode the radio with another one included in the zip.
The installation went quite smoothly but when the phone rebooted, it froze on that logo screen...
well i'm here in the same situation...
there must be something to do...
cmon where is the nerd within you, solve this and get a ****load of respect from me
My friend asked me to try recovering his T-mobile DE Hero, it was bricked while my friend was trying to root it
I tried to flash official rom, but RUU gets error 170...
This what appears on screen when device is on:
error 170... thats the usb connection error right?
this could be because the drivers are not installed properly.
read this thread, then try again
http://forum.xda-developers.com/showthread.php?t=647353
Although error 170 is indeed USB error, (with windows 7 normally) the nasty looking Icon at the bottom of the screen does not look good, never seen that before
Let us know how you get on please
I had the same error with mine.
I ended up in installing a custom ROM, since NOTHING would work. No drivers no nothing. It just refused to read the phone.
I installed VillainROM 12, it has OS 2.1 so it's working perfectly
I had the same problem, but I was trying to flash my German G2 using an HTC Official RUU. I've been able to flash the recovery rom using fastboot and then boot it, but that's where my progress has ended. I'm about to flash VillainROM12.0.0-Full and see what happens. I'll let you know.
EDIT: VillainROM12 installed via AmonRa Recovery menu, but rebooting takes me right back to the RUU screen with an Xed-out EPROM
Nothing helped
I tried everything You said, but device is showing same screen, I also tried using SD card method but when I turn Hero on (while holding Vol-) same screen appears
Does anyone have any other idea what to do?
Its looking like a problem with a radio (drivers etc). Try to update it through recovery if u can enter there.
You can see in my first post the only screen where I can enter...
Well.. This icon with a "chip" probably say a SPL or Radio of phone is just f***ed up.. :/ You can enter to fastboot so drivers of graphics and other modules are in good condition..
wheeeler i think u should find a .zip with a official SPL and radio and update it through recovery like u did it with Villain ROM
I got some idea but I think u tried it before.
iwanrakic U can connect to phone via SDK?
Try this command. It should update it.
C:\sdk\tools>fastboot flash radio radio.img
Of course u need image of official radio.
What driver does Windows report installed when you plug it into your PC in that mode?
I think I just bricked my G2! The phone wont start up anymore, it gets stuck at the htc loading screen. What can I do to fix this?
another scaremongerer....
its NOT BRICKED!
such a drama queen.
Just run an official RRU EXE or go into your recovery and flash a different custom rom (if you have a recovery).
i think that I have a similar problem..
I was doing some flash rom( in case Flykernel-11c)...after the process, the android had a strange behavior:
1. The SD card stopped to work.
2. And ALSO, the USB connection stopped. But the power connection is working.
I can't use the adb shell to connect because it doesn't find the device.
So, i cant use the recovery of backup, because i can't acess the backup allocated in SDCARD.
Just a note: I tested the SDCARD in another device, and its WORKING.
Any ideia?
That happened to me a while ago. Unless you have an engineering spl where you can access the sd-card reset command (or whatever it is) I think you're knackered. Someone else feel free to correct me if I'm wrong though.
doubt
TheReverend210 said:
That happened to me a while ago. Unless you have an engineering spl where you can access the sd-card reset command (or whatever it is) I think you're knackered. Someone else feel free to correct me if I'm wrong though.
Click to expand...
Click to collapse
What do you mean? "Unless you have an engineering spl"
Turn your phone off, then turn on whilst holding the back button. There is a white screen and a few lines of text at the top. If it says s-on, you have a normal, locked spl, if it says s-off its an engineering one. Anyway, the engineering spl has a few more commands you can access, one of which resets access to the sd card and usb. Unless you have an engineering spl and can access that command, I don't think there is too much you can do.
hi there, im new here and ive been searching on the forum for a long time, but i didnt see any solution for my problem... (or maybe i was blind) so when i was trying to flash back original ROM from bootloader screen through USB, it didnt show my current image version info on the screen, but it did show the image version that im going to upgrade... however, i still let it updated and it said its succeed. but when my phone going to reboot, it stuck on the "stick together" screen... btw, my phone is PB81120 SS-B3 SPL-2.08. HSPL 8G XE. hope someone can help me solve my problem... thanks first :]
Go into bootloader again and connect the device to your PC via usb (should show USB at the the bottom in bootloader) and run the Rom Update Utility again. But first make sure the ROM is compatible with TmoUS Hd2.
I would recommend flashing stock from the bootloader just to be safe.
but i was trying to install T-Mobile_HD2_MR_Software_2.13.531.1 under bootloader, and it still the same... :[
Was that what you origonally tried updating to? Or was it a custom rom you had tried?
Sent from my HTC HD2 using XDA App
that was the latest i tried to updating to, or any different kinds of version of original ROMs... before, i tried to update a custom ROM on it first, but it failed :[ actually, when i first got my phone it was unlocked, so while i was waiting to get the unlock code for it, i decided to install android on it... later on i had successfuly putting android on it, and by that time i got my unlock code too. then i typed it in and my phone just reboot and stuck on the "stick together" screen till now... so i started to look through the forum and found out that most ppl said is to reflash the ROM back to the original one first, and then everything would be alright... but i guess it didnt work on my phone D:
Have you tried a hard reset? (Hold both volume buttons while booting)
Sent from my HTC HD2 using XDA App
yeah... i tried everything :[
hi,
don't worry, your problem is resolvable. (as long as you see something on screen, you are lucky.)
1) When the stick together screen comes, do you see any numbers on left bottom after waiting for some time say 1 min.
if yes, then your problem is missing OS image only.
in this case, take out the battery. after that, keep volume down pressed all the time and insert battery again. press power button, if mobile does not start immediately. please keep volume down button pressed till the time tricolor screen does not come on. after that connect cable to computer and update normally.
2) If you don't see any number, it may mean multiple things, which all are resolvable. (most likely bootloader stuck in another mode.)
in any case, try steps in given in 1 and report back. before reporting back please install mtty on your computer as it is needed to send commands to mobile to get out of this mode.
Try this: http://forum.xda-developers.com/showthread.php?t=668347