HTC Magic Bricked? - myTouch 3G, Magic Android Development

hi guys
i'm crying
So i've used the amon ra to create goldcard, root, and flash my mytouch.
The procedure finish correctly.
but after when i want to install a new rom (ex :: eclair) in french, i upload the rom, and at reboot the phone stay on vodafone screen.
After some research, i'have put a 32A radio on a 32B phone (i'm not sure)
So i'd try to replace the radio.
I went on the HTC site and download the "ota-radio-2_22_19_261.zip" file
I copy that on my SDCARd, and rename it upload.zi
I went on the AmonRA recovery, and after a wipe, say "apply update.zip"
The phone write that he found,it, and i start the updating.
The phone "reboot", and display a picture which represent a uploading on the phone.
The phone reboot, and .... nothing
i rest on the viodafone display :/
And i've not access to fastboot.
I apolozige that my phone is bricked?:! isn't it?
So i want solutions to send it to the sav, or if there are other things to unbrick that....
thanks for answers, i really need help...
(I thought that the radio flash cant brick the phone, but apparently it's not exact?!)

can u access recovery or hboot ?
what's ur spl n radio ?

i'd access to.... nothing i think
vol- + power = Vodafone screen
Back + power = vodafone screen
home + power = codafone screen...
i think its really breicked
is there another solution than send it to SAV (i'm not sur that the SAV take it on )
Thanks for answers

Try this:
Unzip the ota-radio-2_22_19_261.zip, inside that you should find a radio.img. Unzip that to C:\AndroidSDK\tools\. Boot your phone into hboot (volume down + power). Connect you phone to you computer via USB, open up CMD and type in (pressing enter after each line):
Code:
cd C:\AndroidSDK\tools\
fastboot flash radio radio.img
If that doesn't work, boot your phone to recovery (looks like that worked). Again, connect the USB and type the following in CMD:
Code:
cd C:\AndroidSDK\tools\
adb shell flash_image radio radio.img
Edit: Looks like that didn't work..
When you phone is stuck on the boot logo. Try connect your phone using USB. Open up CMD and type:
Code:
fastboot devices
or
Code:
adb devices
If you get up a serial on any of these, then you should be able to flash a 32B radio and unbrick your device.

Not sure if this will help but This worked for me. Remove the recovery image. Then power off the phone. Power back up holding the Power and Home buttons at the same time. You then should see the "triangle" screen. If you see this, push, One Time, the Power and Home buttons at the same time. This should bring up the factory recover screen. Here you should be able to reset to factory software. You will need to re-root afterwards, but like I had mentioned... this worked for me and not sure if it works for all.

ok so i think it really dead
My computer dont detect my magic when i connect it (no material in the .
I try to send it in the device driver list
And i can't acces to the fastboot / recovery mode ....
thanks a lot for your answers i think i had to rebuy one

Just return it to vodafone.
Did the same thing as you did a couple of moths ago...
6 days later I had a new phone (Returned it to my store in germany )
At least its worth a try and saves a lot of money...

Related

Wifi Xoom Rooted? RSD mode 3 -- no fastboot, no adb

Hi. I was on #xoom at freenode earlier and I got some help, but unfortunately no solution. (thank you Kas, EbonyGhost, Pyrator and the others)
I flashed the recovery here:
http://forum.xda-developers.com/showthread.php?t=1074979
I flashed... THE ZIP!!
The flash went well, then the device rebooted and showed "Starting RSD mode 3"
I have only 2 screens:
- with VolUp + power = dual core techno + "Starting RSD mode 3"
- with VolUp + power then immediately VolDown = only the dual core tech logo, no text
Either way: no adb, no fastboot. Tried other usb slots. Tried reinstalling moto drivers.
The xoom never gets recognised by windows. I don't have the dongdong sound when I plug it, in either mode.
I already tried this:
http://forum.xda-developers.com/showthread.php?t=973355
but I get < waiting for device > because it's not recognised by windows...
Any other idea?
Thanks
Regards
Note: I might be away for several days. I'll try everything you say, but maybe I won't be able to post my feedback until monday night (around GMT timezone)
I have this exact problem.
So, when you power up the device, you press 'vol-down' when you see the Motorola logo? Because that should put you into fastboot mode. Don't use the power+vol-up, only turn on device and press vol-down when you see the logo. I've been in the same situation, but was able to get fastboot working like this...
if you hold the volume down button and power on the device and get no fastboot then you may as well just send it to motorola. looks like this is becoming a problem and cannot be fixed.
mbroeders said:
So, when you power up the device, you press 'vol-down' when you see the Motorola logo? Because that should put you into fastboot mode. Don't use the power+vol-up, only turn on device and press vol-down when you see the logo. I've been in the same situation, but was able to get fastboot working like this...
Click to expand...
Click to collapse
This. Flashing the wrong partition should *not* mean that you can't get into fastboot any more.
I know that volume down should get me to fastboot but in fact it doesn't. Windows never makes dong dong when i plug the xoom... My drivers are ok because my nexus one gets recognized instantly and adb is working fine on the phone...
Any reason you don't use RSD to flash the wifi xoom sbf file? (I'm pretty sure someone said that was released not too long ago)
I didn't try yet, I can't find the SBF for the wifi xoom.
I tried the 3G SBF file it's not even working. I know it's not the right file for my device but since it's already bricked...
I have RSD Lite 4.9, latest moto drivers, updated using the moto tool.
When I load the sbf file in rsd lite, I can't see the device, and pushing start has no effect.
I did that when the device was showing "Starting RSD mode 3"
How can I get it back?! I tried on my windows laptop and also on a macbook, without any luck.
This is happened to me , and i flipped cuz i rendered my $600 Xoom to a paper weight , i rebooted (Volup+power then voldown) , i tried ADB and it didn't work... then i left my computer to do something, i returned to my PC and i was flipping through DOS command lines (up and down arrows) and click enter in one of the commands by mistake and it worked! the command was "fastboot erase cache"
i then typed the following to return to stock (you need the stock files)
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Thanks, but I don't have fastboot. It's always < waiting for device >
Topper Harley said:
Thanks, but I don't have fastboot. It's always < waiting for device >
Click to expand...
Click to collapse
You mentioned you tried the steps in http://forum.xda-developers.com/showthread.php?t=973355, but how did this section go:
"Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img."
ed. The other suggestion I heard floating around is to flash the CDMA Xoom's SBF -- yes, it won't get you all the way there, but it might restore things up to the point where you can get into fastboot and then flash the stock images.
I did try already to fastboot flash boot boot.img (stock), then reboot pushing vol up, vol down, both, using clicking or holding them... no luck
I also tried to flash the VZW SBF file but RSD Lite doesn't even see the device. I'm trying now to get some linux running and use sbf_flash instead because I was told that it's more efficient than the linux one.
No luck yet on that part either.
I was able to get my xoom restore with the following steps:
Hold Power + Vol up to start reboot
immdiately hold Power + Vol down (This will get you to the Fastboot menu)
enter the commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
You've now successfully flashed your Xoom back to stock. Now it's time to relock the device.
Type fastboot oem lock, wait for the menu, the press the volume-down button. Then press the volume up button. It'll take a minute or so, then reboot. You're now completely back to stock and ready for the update.
hoopsdavis said:
I was able to get my xoom restore with the following steps:
Hold Power + Vol up to start reboot
immdiately hold Power + Vol down (This will get you to the Fastboot menu)
Click to expand...
Click to collapse
It stops here. I can't get fastboot.
I tried waiting for the battery to die and tried every combination of vol up/down/power, hold/click/double click the buttons...
I'll let it cool off for one day without battery... maybe it'll wake up wanting to give me fastboot...
I'm losing hope...
Topper Harley said:
It stops here. I can't get fastboot.
I tried waiting for the battery to die and tried every combination of vol up/down/power, hold/click/double click the buttons...
I'll let it cool off for one day without battery... maybe it'll wake up wanting to give me fastboot...
I'm losing hope...
Click to expand...
Click to collapse
I'm in the same situation here... tried basically all the same steps. I'm lost too... can't connect with ADB, Fastboot or RSD... tried all kinds of key combos as well. "Starting RSD Mode 3"... its wearing me down!!
How can i change the topic title? I wanted to say "xoom bricked?" but I typed rooted by mistake
I'm in this exact situation, and I've tried everything suggested here. I spent some time in IRC talking to a few developers, and we tried pretty much everything to get fastboot to work. No luck, so I tried RSD like you said, and that didn't work, either. Eventually we gave up, and I got an RMA from Motorola via their website. I should receive the FedEx box tomorrow so I can return it to them.
If you want, I'll report back here when the whole process is over and tell you if they end up fixing it for free or not. It sounds like it'll probably be at least a week, though.
benso87: yes, tell me. I have time don't worry (away from home until may 28th)
Otherwise, I think mine is definitely a brick. I tried the last thing I didn't: boot linux and test sbf_flash: not working.
I'll try to send it to moto (the device is imported).
I'm kinda sad... not for the money, but for the bad command that completely destroys a device in seconds... and right, for the money aswell...
Small update: I got the box yesterday and sent it back, then got an email this morning saying Motorola received it. Hopefully the whole process will go this fast.
They gave me a tracking number and a site to check to see how things are going, so that's more info than I was expecting. They haven't asked any questions yet, so that's also good.

[Q] bricked HTC Hero 200 please help

I got a used HTC Hero 200 yesterday, and it only took about 1 hour for me to brick it.
I ran "Universal Androot" to get superuser permissions, then I overwrite the files "boot.mp3" and "hero_animation.gif" (I think they were somewhere like /system/media/bootanimation) in a failed attempt to change the boot animation. After resetting, the screen just displays the HTC logo for about 30 seconds then goes blank... so Im guessing my boot animation screwed it up.
When I boot to recovery mode (with the triangle and "!") using PWR + HOME buttons, I can see the option "Wipe data/factory reset [Alt + W]" and I can highlight this option with the trackball, but I CAN NOT click on it. Also, the phone has no keyboard, so I can not press [Alt + W].
When I boot into fastboot (with the skateboarding androids) using PWR + VOLUME DOWN buttons, I plug in USB and the command "fastboot devices" finds my phone (but "adb devices" cant find it).
Is there a way to get this phone working again?
Im new to Android, and Im easily confused. So if anyone can help me through this, Id appreciate it. thanks.
You're more likley to get a better responce in the Hero section however, I'm like 90% sure you will be able to fix, And technically not bricked
But, perhaps an RUU from HTC could help to fix
THANK YOU MAX!!!! that was all I needed. I downloaded the RUU from the phone's old service provider (cellcom) and just executed it as an administrator whilst in fastboot usb mode. everything works great now, and Ive even got a newer version of Android... except it reinstalled that same lousy boot animation...
Anytime dude Glad you got it working again!

Need help with HTC sensation, i think he's bricked?

K got this HTC from a friend of me, was working before, had it rooted and fixed with custom rom
It was S-on on v1.27
k now gonna try to explain what's going wrong:
When i shut down the phone, put battery out, back in, connect to usb, i get the phone recognized by ADB (my HTC phone)
when i type adb reboot-bootloader, device responds and boots into fastboot mode
when i use vul up i get Fastboot usb on screen
from this point i can't get any further, device doesnt respond from any button action except for vol up.
Device is not recongized in windows now (windows 8 64bit) got the famous error 43
So in ADB everything is fine, but in fastboot nothing is working/responding
when i pull battery out, then put it back in, i can succesfully boot with volup en power, then i get everything running (custom rom from before) but it says safe mode
Any ideas what i can do to get this thing back on it's feet?
regards,
Robin
robin-sips said:
K got this HTC from a friend of me, was working before, had it rooted and fixed with custom rom
It was S-on on v1.27
k now gonna try to explain what's going wrong:
When i shut down the phone, put battery out, back in, connect to usb, i get the phone recognized by ADB (my HTC phone)
when i type adb reboot-bootloader, device responds and boots into fastboot mode
when i use vul up i get Fastboot usb on screen
from this point i can't get any further, device doesnt respond from any button action except for vol up.
Device is not recongized in windows now (windows 8 64bit) got the famous error 43
So in ADB everything is fine, but in fastboot nothing is working/responding
when i pull battery out, then put it back in, i can succesfully boot with volup en power, then i get everything running (custom rom from before) but it says safe mode
Any ideas what i can do to get this thing back on it's feet?
regards,
Robin
Click to expand...
Click to collapse
In bootloader(fastboot mode) no buttons will works except vol up,down and power..
If you want to flash a custom rom then
First goto bootloader
Now enter to recovery by using vol down and then power button to ok.
Place a Rom.zip in sdcard format cache/dalvik , all partition except sd and then flash rom..
ahsan64 said:
In bootloader(fastboot mode) no buttons will works except vol up,down and power..
If you want to flash a custom rom then
First goto bootloader
Now enter to recovery by using vol down and then power button to ok.
Place a Rom.zip in sdcard format cache/dalvik , all partition except sd and then flash rom..
Click to expand...
Click to collapse
problem was that none of the button's where responsive, i found the cause of this, volume buttons are damaged (the strip inside was broken)
So now i have a new problem much wurse i think
only power button works, so i did a complete reinstall with ruu, booted up fine, but always in safe mode for some strange reason,
Now after shutdown, i can't get the phone on anymore, only goes to Hboot, and there is nothing responsive, non eof the buttons work, can't use vol buttons because they are broken.
Adb is not responding either, only getting HTC Android USB device in my device list....
I think the phone is ready for trash? :S
robin-sips said:
problem was that none of the button's where responsive, i found the cause of this, volume buttons are damaged (the strip inside was broken)
So now i have a new problem much wurse i think
only power button works, so i did a complete reinstall with ruu, booted up fine, but always in safe mode for some strange reason,
Now after shutdown, i can't get the phone on anymore, only goes to Hboot, and there is nothing responsive, non eof the buttons work, can't use vol buttons because they are broken.
Adb is not responding either, only getting HTC Android USB device in my device list....
I think the phone is ready for trash? :S
Click to expand...
Click to collapse
in bootloader adb doesn't work only fastboot
so when you are in hboot screen try this command
fastboot reboot (in the hboot screen should say fastboot usb)
rzr86 said:
in bootloader adb doesn't work only fastboot
so when you are in hboot screen try this command
fastboot reboot (in the hboot screen should say fastboot usb)
Click to expand...
Click to collapse
can't get into adb anymore so i think the phone is dead unless we repair the volume buttons right?
robin-sips said:
can't get into adb anymore so i think the phone is dead unless we repair the volume buttons right?
Click to expand...
Click to collapse
since you are dealing with a hardware problem then yes
but try this
boot normally(even on safe mode)
connect it to pc and type
adb reboot bootloader
it will take you directly into fastboot mode
then type fastboot reboot
see how it goes and check volume button from there(to confirm the hardware issue)
otherwise repeat the procedure but instead of fastboot reboot run the ruu.exe again

[fix] htc one s stuck in bootloop, volume down button not working [root][fix]

So here was my situation:
I was flashed the wrong piece of software (stupid me) and I was stuck in a boot loop. Unfortunately the volume down button on my HTC one S was not working so a simple boot into bootloader mode did not work!
Furthermore, I couldn't even get the phone OFF! Pressing the power button for minutes on end still ended up in the HTC constantly rebooting itself. (Worst thing ever!).
FIX:
Step 1: Power Off device
Although this may sound very easy to do, I could not get the device powered off via the power button(10-20 secs) so I had too do it the hard way.
Luckily, the One S being a sealed phone isn't actually hard to take apart. Its actually rather simple!
I used a video on youtube to disassemble then took out the battery for about 30 minutes. (Search "HTC ONE S fix" on Youtube and you'll find it. Sorry i can't post any links im a junior member!)
Step 2: Plug the USB cable into your PC
Put the battery in ( if you used the physical battery pull out of course)
With the device completely off plug the cable into the PC and run the command
Code:
adb devices
By doing this my device actually went straight to the recovery screen and the device was recognized on the computer.
Now the recovery screen i got wasnt very helpful as it continuously rebooted and eventually booted back to the white HTC screen.
HOWEVER, the fact that I could use ADB commands gave me hope.
Step 3: Reboot into bootloader using adb command
Code:
adb reboot bootloader
This is where I really saved myself i ran this command and got to the bootloader screen and I was able to actually work with that!
Step 4: Flash/ Restore Backup to your device and get it up and running!
Now there are a couple of ways you can choose to do this depending on your specific situation and resources available:
A) When in bootloader mode you can access the fastboot commands which will allow you to run any flashing commands that you need to rewrite whatever is corrupted (e.g boot.img)
B) If you have a working recovery simply select recovery and boot into recovery and flash either your nandroid backup or a new ROM as a whole
C) This is what i did, I ran a stock RUU which deteccted my phone and in 10 minutes my phone was up and running!!
Now I know this is a rather rare case, but I actually thought my phone was gone and the fact that I got it working really motivated me to put this out there so someone like me may be able to get their phone up and running again!
Forgive me this is probably my first real thread, Hopefully I continue to post how I fix some of the rarest occurrences I always seem to get myself into.
NO MORE BOOTLOOPS! Who says we need volume down buttons? LOL

Bootlop / cannot enter TWRP from Bootloader Menu / Power button stuck

Hi guys,
I currently have some issues with my beloved N5. I try to be as specific as I can (therefore the text will be a bit longer)
First things first: My device is experiencing the well known "stuck power button problem".
But I also do have problems which are not related to that one (at least thats what I believe).
Overview:
CM 13.1
ElementalX Kernel
TWRP on 3.0.20
Main issue: I can not start my phone regularly. When not plugged in, it just does not respond at all.
If it is plugged in I can get into the bootloader with only pressing Volume down (because the power button is stuck inside). Weird fact #1: in bootloader the power button should work to confirm a specific task like Start, or boot into recovery but it doesnt. Also: the phone is steady in the bootloader and does not keep rebooting.
Therefore I wanted to perform a backup (nandroid or at least all media) and reflash my ROM to see whether it is more of a software issue. I tried booting into TRWP which is not working (device shuts down after Google logo (might be because of the power button issue?).
I know that I can flash the recovery again through adb or the Nexus ToolKit but obviously I want to save my data first.
As far as I know there is no option as adb pull or through the recovery to save those only being in bootloader mode, am I right?
Question: Can I dirty flash without losing data? If thats not the cure, what else could help?
Other facts to know: while running
Code:
adb devices
I get that the
Code:
"adb server version (36) doesnt match this client (35): killing...
but then:
Code:
*daemon started successfully*
(same in Nexus Toolkit).
If I continue with
Code:
adb backup
it says: no devices / emulators found. Altough the nexus toolkit (and fastboot devices) say:
Code:
FASTBOOT: 03181238e07723e0 fastboot
If you made it until here thank you for reading :good: and I would be even more pleased if someone could help.
Best,
McRacoon
I have this problem to , i cant use my volume and power button in ROM / TWRP ,
I got lost, which data you want to save ?
fastboot flash boot recovery.img | fastboot reboot than gets you to recovery from where you can save data.
@Redchi: not really exactly my problem but if you can get into recovery you can use your touchscreen in TRWP?!
@icrunchbanger thanks for your reply.
I want to save all my data like videos, pictures, whatsapp chats etc.
I know how to flash the recovery (again). The question was whether I can save any data without a working recovery (just from the bootloader). Imo it is not possible but maybe you guys know how to do so.
If I reflash the recovery I still can not enter it as the phone reboots itself every 5 seconds due to the stuck power button. The reflashing operation is not finished (Nexus Toolkit says: "Waiting for your device" and times out after a while) and the battery icon pops up every 3 seconds.
Edit: and yes I tried several workarounds to unstuck the power button like flicking against the button, tapping on table, cleaning etc. The only thing I haven't done is tearing the motherboard apart and replacing the whole button itself.
I recommend removing the motherboard, applying pure alcohol around the area, and then quickly pressing and releasing the power button? If this doesn't work, I suggest replacing the power button.
i can use button to get bootloader + TWRP , but my Button volume up down and power cant use in Rom or TWRP, i do no this software or hardware ,? my nexus normaly use but not have button , I use mikey or double tab to wake get screen on , i use apk to get volume , sorry bad english

Categories

Resources