Related
Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Difinitus said:
Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Click to expand...
Click to collapse
What do you mean by safe mode? Which donut ROM are you trying to flash? Which recovery image do you have? How long was it stuck on the splash screen. You need to give more details for us to be able to help out. What radio and spl do you have?
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Difinitus said:
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Click to expand...
Click to collapse
I'm not sure what you mean by extract update.zip. I think you are talking about fastboot there. Have you tried to flash the rom in the recovery image? you know, by pressing power and home to get to the recovery, then flashing it through there. go into fastboot by pressing power and back and it will tell you what radio and spl you have. once you have that, write that so we can further get a grasp as to your problem. if in fact you still have the 32A configuration, you might want to flash over the 32B radio and and try to flash a 32B rom.
That is my problem, I can't get past the "MyTouch 3G" green screen. I've tried the Home button, Back button, Vol Down button and holding them for several minutes with no result, it stays at the very first screen when it turns on.
I've tried flashbooting from adb but it says "waiting for devices" and my computer isn't picking up any kind of device.
I'm having the exact same problem except im stuck on the vodafone screen. I also tried flashboot form adb but "waiting for devices" is shown and pc wont detect the device.
Did this before.
If you can get into recovery mode, Hold Home button while powering on, you can restore a nandroid backup, if you took one, or put the sappimg.nbh file or the correct items to flash whatever rom.
I had a stock 1.5 Mytouch. I wanted to root and get the 1.6 version of cyanogen, forgot to flash the HTC_ADP_1.6_DRC83_rooted_base as part of the process and had got stuck in the neverending mytouch logo.
If you can get into recovery:
wipe, then put the update.zip files directly on the card.(use a SD adapter, ...)
Choose apply any update from SD
Choose the base files, then the rom if its a newer version
Once those two updates run, reboot the phone.
My never ending logo disappeared, and the phone booted. Newb mistake on my part.
Wait at least a minute or two once this is done.
since the phone is stuck on the original logo and isnt responding to buttons when loading up... do we manually remove and reinsert the battery while holding the home button?
I have tried getting into recovery mode, but it doesn't do anything past the splash screen. Holding the home button while trying to power on the device won't do much.
hey difinitus keep me updated if u somehow get it to work
Even when you take the battery out for a significant time it turns on immediately to the logo screen. Whats the longest you have left the phone sitting at the logo screen.
A small thought, since it was trying to load a rom you had on your memory card, try taking the battery out, and removing the memory card, and then turn it on and wait a bit and see if you get a different result. Its a thought.
If that doesnt work put the memory card back in and turn it on and once its on remove the memory card.
Perhaps the rom on your memory card is corrupt and it is unable to continue to load it, you could even try putting the rom on again using your memory card reader and your computer, thus erasing the existing one.
try plug usb in to phone
take battery out
prees and hold home button
re-insert battery while still holding button
let go after about 3-5 sec
have you tried getting into fastboot by holding back and powering on the phone once you took out the battery? cuz fastboot doesn't initialize after the splash screen, it just pops up as soon as you hit back and power
@Tech no boy; I have tried using several different update.zip and a .nbh and also tried reformatting.
@sitimber; have tried that before, the splash screen still pops up. It just vibrates once and goes to the logo, with any combination of buttons and steps.
@tazz9690; Yes, no matter what I do it still goes to the splash screen. I've been saying that for several posts now.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.
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
Hi there. I would appreciate your help here. I am a rookie with android software as I own an HTC Magic almost 3 weeks from now. My phone has the above characteristics:
SAPPHIRE PVT32A SHIP S-ON H
HBOOT-1.76.0009 (SAPP10000)
CPLD-12
RADIO-6.35.08.29
Dec 8 2009, 17:38:48
The software I had was Android 1.5 and it was rooted with RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver ROM. I was watching on Youtube some videos about CyanogenMod 6 at HTC phones and I decided to try to put this software to my phone via ROM Manager. The result is a major disaster (or not?). Specifically, from my phone I opened ROM Manager, download rom, CyanogenMod nightlies , CM6 XXXXXXXX (can’t remember which one) EBI1 Kernel… So I had successfully downloaded it and followed the instructions while installing. After installation completed it automatically rebooted and started loop again and again. All it gets to is the "HTC MAGIC" screen and then reboots every 5 seconds. At the begging I thought that this is the installation process. 30 minutes later I had a doubt for this. I pulled out the battery cause pressing the Power on/off button nothing happened. I tried everything… nothing at all. I pressed the Power on/off button again it continued looping. After I pulled out and inserted the battery I pressed the Home and Power on/off button (Android recovery) it still continued looping. Removed again the battery and inserting again while pressing Back and Power on/off button (fastboot ) it still continued looping. I pressed Home and Back buttons and tapped Power on/off button… the same issue (continued looping). Down volume and Power on/off button… nothing. Up volume and Power on/off button… nada. Pulled out the battery for 30 minutes and tried again… nothing again. Tried again and again with the USB connected and disconnected… nothing. Still looping. I tried to install the previous Rom I had via PC but I couldn’t cause USB was connecting and disconnecting because of the rapid (5 second) boot loop. The only button which seems to work is the trackball which freezes everything with the blue led on and a black screen between the loops. I pressed all the buttons together wishing something to happen… unfortunately nothing happened. I backup my SD card and tried with an older backup I had… nothing… boot loop remains. I am despaired and tired (almost 18 hours online searching some help or solution). The only thing I want is to make fastboot work and install my old ROM via my PC… nothing else.
Please, please, please…. HELP ME!!!
well this is a pain. Your fastboot is also locked. You should read instructions and learn a bit before just flashing whatever you please. CM6 requires old radio and a different SPL. The one you're using isn't compatible, hence the reboots. You also can't get into recovery because your radio and recovery are also not compatible. I'm assuming that rom manager did that? I'm not sure, all you new people are just running that thing and flashing away without any knowledge behind it.
I don't think you're bricked but I'm not 100% sure what to do since I've kept my bootloader unlocked to run fastboot commands (which would easily solve this situation). My suggestion is to get an RUU for your phone, update and then reroot it. Maybe someone else has a better solution but right now you don't have the right recovery and fastboot is locked. At the moment, I can't think of a better solution.
edit: ugh it's late and im sleepy! i just reread what you said, you can't get into fastboot either? If not you're probably bricked
yup, I totally agree: I remember the first time I flashed a rom over the stock version which was installed. I read every sticky thread, the whole wiki page and lots of xda threads before giving flashing a try. It's just too risky to mess up an expensive phone. Just look at all the "bricked my phone, please help" threads, that alone should make one think twice (and read, read, read) before flashing...
I hope someone can still help you. But not getting into fastboot anymore?! :-(
Sorry and good luck,
V.
Sent from my HTC Magic using Tapatalk
Thanks gyes for your replies. Still I can't find a solution. The only thing I can barelly see before it boots again by pressing Back button and On/Off button is ClockworkMod Recovery v2.5.0.1.
As about the mistakes I admit that this is my fault but also I have to say that before I root my HTC I couldn't download anything from ROM Manager. After I had succesfully rooted my phone and downloaded the ROM update from my phone there was no mention about radio issues or conflicts in the installtion proccess. Even though it is my fault and I admit it. I don't mind if I loose my data (I made an SD buck up). I just want to find a way to stop this stuppid loop, make a USB connection with my PC and install my previous ROM even if I have to screw out my phone.
as I'm not able to help you myself (I'm just a user not a developer) I can only recommend checking the "bricked phone" threads for solutions. I think I saw an "how to unbrick phone" thread somewhere. Never read it though. Probably there are many others who messed up their phone somehow and lots of solutions in all those threads. Just use the search feature and look for brick threads, solutions, help, etc. Maybe you'll find something.
Sry that I can't offer more,
Greetz,
V.
It's ok my friend... Thanx 4 replying
i don't know if it's related but a guy had a bad flash and had a blue trackball toom, which you mention in first post, here is his thread on what he did to fix his phone http://forum.xda-developers.com/showthread.php?t=649689&highlight=unbrick
Nope... Nothing helpfull unfortunately! Thanx anyway
A new clue is that I left my HTC magic to boot loop while the usb cable was connected with my PC dinging in and out while rebooting and after 10 minutes it stoped rebooting (it happened one's more yesterday). No button combination is responding (the trackball also) even if I keep pressing them over a minute continuesly. Also no led is lighting even if it is on USB connection. I ashume that if I remove and putt back the battery it will start again the boot loop as it happened yesterday. So I will leave it as it is and try later to restart...
Nothing... Started boot loop again
Today I gave my Magic to HTC Service. It was confirmed that the electronic circuit was "dead" and it had to be replaced. If I'm lucky maybe I wont pay a dime. It depends if the software I had on was Android compadible or not. If not then... better not think about it!
Hello,
I come here and make a new thread after I spent the day inside various forums to solve my problem but wasn't able to.
Here is the thing I tried to install the cyanogenmod earlier today. I unlocked my N1 properly and think I rooted it properly as well. But I was unable to install the custom rom. Actually my N1 won't even boot, it's stuck on the cross image with the unlocked lock and I can't boot the recovery either. I tried to install a custom recovery, the amon ra thing, but it still freezes on the cross screen.
I assume my N1 isn't completely bricked since I can still power it up, start the fastboot mode and my computer recognize de USB connection (however ADB won't find the phone even after I re-installed the drivers).
So here I come for help to either bring back my N1 to its former stock rom or any functionning rom.
Thanks.
Try the unroot/restore guide with PASSIMG of FRG33. Look at my signature.
oh thank you !!! It worked perfectly !
EDIT : Well spoke too soon I rebooted the N1 after its apparent recover and it froze again, so I started the operation once more and while updating the files ravio_v2 was checked "fail-pu" instead of "ok"
EDIT 2 : Well I rebooted after the update and the N1 never powered up again ... I guess now it is really bricked... though I can't figure why
olicyr said:
EDIT 2 : Well I rebooted after the update and the N1 never powered up again ... I guess now it is really bricked... though I can't figure why
Click to expand...
Click to collapse
You can't even get into fastboot any more?
Also, you say you followed the right steps to unlock the device and the right steps to root the device... What steps did you take exactly?
Hi,
to unlock the phone I used the oem command in the fastboot mode. Then I tried to install the amon ra custom recovery and I think that is what brought all this trouble.
Can you still see your device through fastboot? If so you should be able to flash a recovery image and a ROM of your choosing.
It should boot up fastboot like Dirk said. You can not brick the phone by flashing a recovery.
Sent from my Nexus One using XDA App
I guess there is some HW fault - might be a recent bad sector in one of the system critical areas. It's not something you can cause with SW - unless you're flashing hboot or radio, which should have been covered in the first restore attempt, which worked.
Anyway, if it doesn't power up at all - and doesn't react to charging - try pulling out the battery for several hours, and then put it back and try again. If it doesn't work - then you're up for a warranty repair...
DirkGently1 said:
Can you still see your device through fastboot? If so you should be able to flash a recovery image and a ROM of your choosing.
Click to expand...
Click to collapse
No the phone doesn't boot anything. I'll try to remove the battery and wait a few hours like said above, if it doesn't work I'm still under warranty I think
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.