Hi All
Ive read the HTC Magic Hacking Wiki Page Thats very informative and a great help. Although i cant seem to find my particular answer, I have previous got to the root/restore screen via the 1click unlockr method although now i cannot get back there i get the exclamation mark and a phone icon. But my phone works fine, Is this normal.. Do i have to root?
Im a big messer and since moving to my last phone (Omnia) i love custom roms but have a habit of diving in head first, Bricked my first omnia and hate to do it to this Hagic as i love it.
Im after a good rom, Either with extensive apps** or Full Exchange support
Really appreciate any response
Can you get into the recovery screen? power off>>>>> hold home and power.
No? i just get the exclamation mark and a phone icon>?
Anyone? I would really like a answer?
can you get in fastboot? power off >>>> back+power on
if so, you can get AMON RAs recovery 1.2.1
then fastboot boot the recovery
then fastboot flash_recovery the recovery from there
phone is fine but if you want to put another rom you need a proper recovery
Related
Hey people greeting first of all by stupidity i flashed a new radio 32a radio on my 32b mytouch by accident now my phone its bricked it just stay stuck on the first splash scree i cant fastboot or recovery mode my pc dosnt reconize my phone ether what can i do??? Help please
mytouch 3g
32b s on g
slp 1.33.2010
if you cant fastboot/recovery/anything, it's pretty much bricked. If you get some blue LED, there isnt much hope for that either.
i got no blue led it just stay on the first splash screen no recovery mode or fastboot
morepr said:
i got no blue led it just stay on the first splash screen no recovery mode or fastboot
Click to expand...
Click to collapse
Then you're bricked. Means you need a new phone.
no ooo
people there is a solution via the usb when it is stuck at the first splash screen just search
mine is totally bricked and still no solution !!!
call tmobile.
I did the same thing yesterday and I told them that My phone updated itself then wouldnt turn back on.
my new one is in the mail and will be here in 2 days
just act naive and clueless.
as long as your still under warranty, your all good.
thanks ppl i try everything but this its not going no where the pc dosnt want to recognize my phone and i try everything just gonna throug it in the toilet and call the insurence
At least sell it for parts, you can probably squeeze 40 bucks out of it or similar. Check the going rates on eBay for non-functional handsets.
I know its a bit late....but I fixed my 'bricked' MT3G
I was searching around the web for a solution to my problem, and needless to say, there wasn't much out there for me besides the typical... "it's bricked, buy a new phone."
So here's my story:
Earlier today I decided to upgrade my MT3G to Cyanogen's 5.0.7 Android 2.1 rom. I had used the experimental 5.0.6 rom, and found it to be a bit more "glitchy" than I was comfortable with. So, I went online for what I figured to be a very simple upgrade...and downloaded both the rom and a kernel (which was 32A not 32B).
Needless to say, after installing the rom, the kernel, my gapps update, and resetting my phone... it did nothing but hang on the MT3G screen. After about 30-45 min...I knew something was wrong and I freaked. It was unresponsive to multiple attempts to reboot, and was not being seen by my computer.
That's when the online search began... I looked for other individuals who've suffered the same fate and kept coming up with the same "you're screwed" response. Having recovered more "bricked" iPhones in the past than I can count, I knew this could not be the case. For me, as long as the phone turned on and flashed some sort of screen, there's still hope.
So what did I do...
Well, I first attempted to boot the phone into recovery mode...but it would not work. Next, i figured I would try doing a fastboot... and what do ya know... it worked!
From there I used multiple combinations of plugging in the phone via usb and resetting and putting into recovery mode until I found one that worked.
So here's my steps:
(Note: this has only been tested if you accidentally installed the 32A kernel on your 32B device)
1. Power on the phone... If you continuously sit at the green MT3G screen, take off the back and take out the battery.
2. Plug in your USB cable (VERY IMPORTANT, will explain later)
3. Next, replace the battery and hold down both the [home] and [power] buttons, if it merely turns on to the green screen, and you get no response from your computer's usb notification window...take out the battery again
4. Fastboot your phone (hold down [back] and [power] arrows) While your phone in connected to your computer, it should make a notification sound.
5. Restart your phone from Fastboot, AS SOON as it shuts off, hold down the [home] and [power] keys.
6. Continue holding until you hear a notification sound from your computer...at that point it should boot into recovery mode.
7. Wipe your handset (just for good measure) and reinstall your update package...DELETE that wrong kernel from your sd card so you dont make the same mistake again.
Summary:
I have no clue as to why it works, but I've done this 3 times now just to verify, and each time it has worked. For some reason, the USB connection to the handset acts as a precursor to the phone booting. I will stress that without plugging in the USB, my phone did not boot into recovery mode. However, after I did plug it in...Fastbooted....Reset....and Booted into Recovery it worked perfectly.
I am still suffering lags on my device (more so than before) and this could be a product of my stupidity, or this rom being laggy. Either way it works, and I don't have to purchase a new phone!!!
Mod. edit: not dev related, moved to general
I experienced the same problem which can not boot recovery.
I've tried your way above but no luck.
Is there another way?
HTC MAGIC MY TOUCH
SAPPHIRE PVT 32B ENG S-OFF H
radio-2_22_23_02
cm-5.0.7-DS-signed
T-Mobile myTouch 3G - stuck on splash
Today I probably flashed my phone with a wrong (32A) SPL. I can't access fastboot, recovery mode or anything, including access from PC (either Linux or Window$). But it's stuck on splash - if it was totally bricked, would it still load a splash screen? Is there any hope?
Sigh.. I have the same problem.. Blue LED If I hold down the track ball but can't get to fastboot or recovery..
My problem started after I flash the HTC rom from the website.. Sigh.. I think it was the radio that did it..
Anyone found a way to get around this (w/o jtag)?
I am also experiencing the same problems. Blue LED works, cannot get into fastboot, bootloader, or recovery. It just sits on the opening splash screen.
Any other ideas?
Looks like I will just sell mine as a "bricked" device and hope to salvage a few bucks. Sigh
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU. I would keep going but you get the point. I downloaded ROM Manager, and I flashed a Cyanogen Nightly ROM from 11-5-2010 and I got nothing but a Green spalsh screen and a reboot cycle. You instructions ROCK!!!
I went crazy and prayed a few times to unbrick my phone. I tried different things and then nothing worked. So I had the phone on for a bit and it restarted twice and then ran. Just let in sit for a while. Give it time. Maybe itll work for u too. goodluck
have a mytouch 3g 1.2 with the old radio and SPL, i acidently bricked it trying to flash the new radio and SPL and now i cant get into recovery or fastboot and the flash screen is frozen, pleassssssee help me get this fixed it has been completel useless for the last week or so
Succesfully unbrick with wiggler Mytouch 3G 1.2
as Ezterry instruction i follow his guide, and build my own JTAG.
My God its working 100%..
awebagar said:
as Ezterry instruction i follow his guide, and build my own JTAG.
My God its working 100%..
Click to expand...
Click to collapse
Can I ship you my bricked device so you can practice unbricking? I can pay you in random electronics
I flashed a non-US rom on my Vibrant and now my volume buttons are backwards and my power button isn't recognized in recovery mode. The funny thing is, I am stuck in recovery mode. I can't get out of it. I pulled the battery and turn on the phone and it automatically goes to the recovery. I tried to go into download mode as well, but no luck. Hmmmm what to do now? Any advice would be appreciated!
i hope someone helps you out. If someone else was in trouble with their phone, they would want help. Wish I could help. Im sure someone will get to U
this just did it to me i need help also anyone got any idea how to fix it
Wow, that really sux. I honestly do not know what to do at this point, I am only replying to give my sympathy and a bump.
I am quite experienced in AmonRa Recovery, but new to clockwork (I am assuming that you are using clockwork). Is it possible to connect to adb while in clockwork, without the use of an "action" key?
Very sorry this happened to you guys, hope someone figures it out soon!
I would read this thread and follow it:
http://forum.xda-developers.com/showthread.php?t=738085
It looks as though others are in the same boat as you are after flashing non US roms.
If you have ADB working I typed "adb reboot clockwork recover" and it rebooted me back up $hit scared the hell out of me now im scared to flash my nandroid
Don't know if this helps, but eugene373 said he used the back soft-key to act as an action key in clockwork recovery
http://forum.xda-developers.com/showthread.php?t=740077
Okay, so I think this topic has been talked about a few times already. But I didn't manage to find a proper solution, maybe my situation is not as desperate as the others I read about.
A friend of mine gave me his Hero for me to repair. It just would not boot up after last official HTC update. Just gets stuck at the first "Hero" screen. Should I precise, he did not do anything to his phone (no rooting, no alternate bootloader, no nothing).
Official RUUs can't manage to detect the phone via USB (whatever the boot mode is), it can't boot, so I can't turn USB debugging on, or install flashrec to set up a custom ROM.
Power + Menu takes me to a waiting screen with a phone and an exclamation mark.
Power + Back takes me to fastboot, from which I can get into HBoot mode.
From these, flashing a new recovery via fastboot doesn't work (remote: not allow), which is to be expected.
Is there any other solution except sending the phone back to manufacturer. We'll do that in the end if no other solution happens to work, but I'd prefer to fix it myself.
Thanks for your help.
Tell me if you need any other details.
A.
Use this http://forum.xda-developers.com/showthread.php?t=776056
Follow the whole of the 1st post from start to finish, the bootloader stuff is crucial.
Then put phone into hboot and try running an RUU.
Found this n all pal,...
http://forum.xda-developers.com/showthread.php?t=714519
Hey you guys
I recently installed amon ra's recovery v. 1.7 on my magic 32a (radio 6.3.5 something) after I rooted my phone, of course.
Now, I thought that with the new recovery I would be easily able to flash a custom rom onto my magic. This was however not so easy, because the recovery behaves in a very weird way. Whenever I tell it to flash a new rom from a .zip image, or wipe the phone, or anything, it just reboots my magic and thats it. Also, the recovery happens to freeze quite regularly when I don't act very quickly. E.g. when I boot into recovery mode and don't touch the phone for the first 5 seconds, it wont respond any longer.
So, I'm probably doing something wrong here. I would appreciate any help from anyone. (and btw, i have the official android 1.5 sense rom installed on my magic, os I cant use rom manager either, since it only supports android 1.6 upwards.)
Look at the root guide in my signature..
Do step 0, 1, 2, 5 and 7 only.
It should flash the recovery partition one more time.
Hopefully it will fix your problem :0)
mumilover said:
Look at the root guide in my signature..
Do step 0, 1, 2, 5 and 7 only.
It should flash the recovery partition one more time.
Hopefully it will fix your problem :0)
Click to expand...
Click to collapse
hey, thanks for the quick response. I still have a few questions though, since I am quite a newb. So when I type all of those commands into cmd, doesnt my device need to be connected to the computer somehow? I read somewhere earlier that I simply connect it using the "mount" funtion, the problem is that that doesnt seem to work anymore for my magic, because after I hit "mount" it simply goes back to "usb connected" without acutally mounting. So ..how do I connect the device to the PC while entering the commands?
ok... my bad..
Try to read the ENTIRE guide... then do the steps i mentioned above :0)
Don't mount it... just connected... but again.. read the guide.
thanks a lot
I didnt use your method to flash the image, but the hero recovery works way better than the one I had before. I managed to flash a rom now. So happy ;D
ok i think i just did a bad mistake
i installed rom manager after i had flashed an android 2.1 rom on my magic. THen i told it to flash some rom from my sd card and also wipe some data, or something. Now my magic gets stuck on the magic bootscreen, like it keeps looping. Did i brick my phone ..or is there a way to fix this? please help me, (
most likely is that the rom you flashed doesn't have a compatible kernel for your phone.
Just boot into recovery and flash a rom that is compatible.
cant boot into recovery ..it just keeps looping
Then you will need to boot into fastboot and reflash a working recovery.
Clockwork has issues flashing the clockwork recovery sometimes.
to boot into fastboot i need to hold power and back, right? ..that doesnt work either. again, it just keeps looping.
so, guys ..did i brick my phonne..?? :S
da robat said:
to boot into fastboot i need to hold power and back, right? ..that doesnt work either. again, it just keeps looping.
Click to expand...
Click to collapse
you're probably not doing it right. you should still be able to get into recovery or fastboot and install a different recovery. i'm using RA-magic+v1.7.0.1 recovery it has bugs but pretty stable.
so what am i doing wrong??
just realized when i connect the phone to my pc over usb and then boot it, it connects to the pc for a second or less and then disconnects again. Dont know if this helps anyhow.
pull battery, put battery back in. hold back and push power.
Should be good.
tried that like 50 times. phone just keeps looping ..like, it restart over and over again.
What you have is what hundreds before you had when they used Rom manager.
The system will not boot into anything.
My advice is to never use Rom manager for 32A device.
The fix:
Keep pushing the back button while the system reboots... just mash the **** out of it..
I helped out someone before you, and he did it for over an hour or so...
It's a timing issue...
Good luck
haha ..so is there still hope?
cheers for all the answers ;D
i do have one question though, actually.
Shall i just press the back button continuously ...while it keeps looping, or should i rather restart the device after each loop and hold the back button?
just mash the back button.
First of all appologies if I started another thread on this topic. I am very green with Android and am now unable to get past my latest screwup! I had CMod 10 on my device but it kept freezing in the browser. I also had Skrillax recovery on it. I wanted to revert back to OTA stock Rom so got the following ROM from this Forum Post:
http://forum.xda-developers.com/showthread.php?t=1816560
Acer_A500_0.000.00_041.121.01_COM_GEN1: ftp://94.23.233.147/Tablets/A500/Ace...5_78277167.zip
I decrypted it, extracted the update.zip and applied it to my tablet as instructed in the post. Upon completion it restarts and goes into this loop at the Silver android screen! I tried to go into Recovery and get the dead Android with the red Exclamation mark. I can reapply the same update.zip file and it seems to go through things again but every time I get the same end result looping silver android loop. HELP! please! If I try to use another stock update file it only get me to the dead android guy with red exclamation mark. I have tried to put this into APX mode but it does not want to go there at all.
Is there anybody out there that can take a little pity on a fool like me to get this thing back up again?
I don't care about the data at this point and which version I get back to. I also do not have my CPUID and can't seem to get to it. Thanks in advance to anyone who could point me in the right direction or better yet walk me through this.
Dead android guy is what I get after root the tab and try to get to stock recovery WITHOUT unlocking the bootloader
DId you try the manual way to go APX, push the reset button with a paper clip and hold power button? If you can get to APX you can use A500 manager tool from this
http://forum.xda-developers.com/showpost.php?p=25891744&postcount=44
you can try unlocking the bootloader which then result in bootable recovery
or check out this guy
http://forum.xda-developers.com/showthread.php?t=1874345
similar problem trying to get stock ROM back
pinmemo said:
Dead android guy is what I get after root the tab and try to get to stock recovery WITHOUT unlocking the bootloader
DId you try the manual way to go APX, push the reset button with a paper clip and hold power button? If you can get to APX you can use A500 manager tool from this
http://forum.xda-developers.com/showpost.php?p=25891744&postcount=44
you can try unlocking the bootloader which then result in bootable recovery
or check out this guy
http://forum.xda-developers.com/showthread.php?t=1874345
similar problem trying to get stock ROM back
Click to expand...
Click to collapse
Ok so now can get in APX mode but it says debugging is not on, I can't get in to turn it on? Is there a way to get the bootloader back to the Skrillax version via update.zip file? I will keep reading these posts but still can't seem to get APX mode right.
mdlevesque said:
Ok so now can get in APX mode but it says debugging is not on, I can't get in to turn it on? Is there a way to get the bootloader back to the Skrillax version via update.zip file? I will keep reading these posts but still can't seem to get APX mode right.
Click to expand...
Click to collapse
First of all a million thanks to Happy who pointed me in the right direction! I appreciate the help buddy! I was finally able to get my device working by following the first post by manually installing Thors v1.7.3 bootloader. Once I got the bootloader back I just reinstalled one of the custom ROMS and voila! back in operation. Most appreciative...
The link again is the following and you do not have to have debug mode on to do the manual flash.
http://forum.xda-developers.com/showpost.php?p=25891744&postcount=44
Mike:victory:
mdlevesque said:
First of all a million thanks to Happy who pointed me in the right direction! I appreciate the help buddy! I was finally able to get my device working by following the first post by manually installing Thors v1.7.3 bootloader. Once I got the bootloader back I just reinstalled one of the custom ROMS and voila! back in operation. Most appreciative...
The link again is the following and you do not have to have debug mode on to do the manual flash.
http://forum.xda-developers.com/showpost.php?p=25891744&postcount=44
Mike:victory:
Click to expand...
Click to collapse
Congratulations! you successfully resurrected a dead droid!