myTouch 1.2 stuck on splash, no recovery or hboot - myTouch 3G, Magic General

My myTouch won't boot into recovery, fastboot, hboot, nothing. Just shows a splash screen and nothing else happens. I can't get the SDK to recognize that the phone is plugged into USB and load recovery that way, either. I've tried damn near everything I could find on these forums, with still no dice. Someone suggested I reflash the sappimg, but how can I, when I can't even load recovery or fastboot in the first place?

sorry but you've bricked your phone once you can't get into fastboot your phone is good as dead. happened to me as well but I was lucky get a new phone after warranty.

They've already sent out a replacement, but when they get my old one, can they charge me for the replacement if they find out what I did?

they wont be able to tell, unless you tell them. I did the same thing to my G1, and it just stayed at the "Tmobile G1" screen, nothing else. I told them it happened while doing the OTA software update.. no questions asked.

Awesome. I kinda figured that if they couldn't get past the splash screen, there was no way they could tell. Good to know, since I added the extra $2/month for extended warranty, so if I ever brick it again like this I can exchange it again. Ha HA!

Related

How I un-bricked my bricked phone.

A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Very nice..
wow seriously, didnt expected that..
good job mate!
btw wat did u do to cause the brick?
Just read the very first line of his post...
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
[...]
Click to expand...
Click to collapse
mgear356 said:
btw wat did u do to cause the brick
Click to expand...
Click to collapse
As I said above, I had been flashing the SPL, and when I rebooted following the flash it was bricked (stuck at first splash screen).
It's weird, because once I managed to get back into fastboot, I simply flashed the same SPL again and it worked fine.
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Never seen someone say the splash screen isn't coming up without blaming the hardware. I didn't think that flashing the wrong SPL would case the splash to not come up. I bricked my first phone by stupidly flashing the wrong SPL first before loading an OS. I thought the whole point of using the word 'brick' was when referring to the phone failing to enter 'fastboot' and 'recovery mode'. At that point, the phone would technically be a 'brick'. This has to be the first post I've seen with a possible fix but I could be wrong since I gave up on fixing that phone awhile ago.
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
bricking means you can't get to fastboot or recovery no matter what you do.
so he counts as bricking.
this might be a fix for the haykuro spl bricked users..
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
No, You can still get to your splashscreen when the phone is bricked, If you cant turn on the phone then thats called the phone is dead not bricked. As stated already if you can't fastboot, or get to recovery then thats a brick.
Just tried it does not work and I was flash the death spl from haykuro,I am getting a new one but wanted to see if this works and I did not think it would which it didnt.
imfloflo said:
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
Click to expand...
Click to collapse
Posted the fix on the android community forums. I have none person in mind, bricked it applying a spl, but he hasn't relied yet. Keep you informed if he does.
Did you reflash ROM after applying spl..? If you did and it still didn't boot then that should most likely be a brick. Can you boot into recovery right now and tell us your SPL version and radio?
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
A bit of a personal opinion here:
"Dead" is when the phone doesn't respond to anything, at all.
The charging light does not come on, the power button does nothing, and there is not so much as a flicker in the screen. Also, it is completely inaccessible for hardware debugging (JTAG, serial, USB or otherwise). This usually happens from a hardware problem, or doing something stupid like zero'ing the IPL.
Examples:
- My brother dropped his Nokia N75 in water. It's dead.
- I dropped my Cingular 8125 (HTC Wizard) on the ground. It doesn't power on any more, and plugging it into the charger does nothing. Voltmeter shows a charge running through some areas of the device's motherboard once disassembled. It's dead.
Solutions: Replace, recycle or sell for parts.
"Bricked" is when a purely software problem causes the device to no longer respond.
This may happen on many levels, but usually results in the OS not booting, or booting and being completely unusable (e.g. stopped with kernel panic at OS splash). It may light up and/or show a splash screen, but it fails to enter the bootloader or recovery menus. Its recoverability may vary, but will usually involve a debugging tool and a computer, and likely a copmlete wipe of everything on the device. Even if it's heavily bricked, if it can be recovered via JTAG or similar, it's not "dead".
Examples:
- HTC Dream only goes as far as splash screen, and freezes there. Does not respond to ADB. Does not enter recovery, or bootloader, however fastboot responds.
- HTC Dream shows blank screen, but lights up as if it were powering on. Fastboot does not respond. I connect my HTC ExtUSB Serial dongle to it though, and I'm able to get a response to some commands.
- Western Digital MyBook World Edition NAS powers on, and spins up hard drive, but does not go any farther than that. Front lights do not light up, and no hard disk activity is heard. Networking is not yet enabled. Hard drive can, however, manually be connected to a PC with SATA, and the firmware image re-written to its partitions.
- XBOX (the original) was softmodded, but the dashboard.xbe (the OS shell) was overwritten. It now just stays at the Microsoft logo.
- iPhone was recently jailbroken and SIM unlocked, then Apple pushed an update on me, and my iPhone is in a state where it doesn't enter DFU/Recovery, and when it boots, it says "Emergency calls only."
Solutions: Be very careful not to further brick the device, but use any methods available. Be sure to check documentations, search forums, and then ask questions if unsure. Make sure you finish every process you start.
After this, might just be hardware "damage" (like a power button not working right) or software "errors", like the home screen failing to load because of "Process com.google.android.gapps quit unexpectedly." These are usually relatively easy to fix, or have fixed.
Again, this is just an opinion.
Back on topic though, I seriously wouldn't have probably thought of using fastboot while it's stuck at the G1 screen, unless mine were bricked. Kudos to you, and I hope this works on some other bricked G1's out there (At least ones with the Engineering/Hard/DangerSPL, the stock SPL doesn't support fastboot as far as I know.)
bonesy said:
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
Click to expand...
Click to collapse
Won't agree with that, what you describe as a brick is a DEAD mobile. A brick is a useless piece which wont get into any state of recovery. The only thing i will agree with is that if it'll turn on there is a way to get it fixed that's why we even got the word unbricking which is done with many other pieces than Android mobiles.
Hope this will get us closer to a unbricking method which works on all the BRICKED pieces out there.
Good job dude!
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
wow sweet news
fishman0919 said:
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
Click to expand...
Click to collapse
Very glad to hear that your dead or bricked or whatever-you-may-call phone is back to LIVE!!!
So I think this solution works for some certain people. So i think rather than arguing on terminology, better spread this good trick to people who had dead/bricked/whatevery-you-may-call phone. IMHO
Thanks for the solution.
Best,
Thihaz
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Click to expand...
Click to collapse
where were you 2 months ago dude? I paid 270€ to change the board on my magic
Good Job! Thanks for the info

stuck at splash screen, have tried all the solutions.

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.

My tmobile mytouch 3g is bricked how can unbrick it??

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

Another, "Is my phone bricked?" THREAD!!

I was rooting my phone last night and was successful. When trying to load a Cayanogen rom, it wouldn't get past the "Vodafone" splash screen. I noticed I did not have the proper radio installed, so, I installed the radio for Android 1.5 from the website.
Now, it is stuck in the red vodafone splash screen, and won't let me enter fastboot, bootloader, or recovery.
So, am I screwed, or is there a way I can fix this? I honestly searched for a VERY long time, and could not come up with much help.
Thanks. Also, I am using this on AT&T and it is unlocked.
if you can enter fastboot or recovery or anything than its not looking good, have you taken the battery out for a while and tried fastboot again?
I'll try leaving the battery out for a little while and try again. I just let it sit on the splash screen for about 15 minutes with no luck.
Left the battery out for 20 minutes, put it back in, tried to enter bootloader/fastboot/recovery, still with no luck.
Any other suggestions? I literally just bought this phone last week!
Also, since I am on at&t and this is a T-Mobile phone, and it is bricked, is there any way I would be able to send it in for a warranty replacement? I have no receipt of the original purchase, but still have the original packaging.

[Q] Nexus one modem seems busted, bricked?

Hi all,
I've bought a Nexus One from a friend that went to US a while ago (I live in Brazil). My N1 was exhibiting an overheating & reboot issue whenever I used the 3g connection.
2 weeks ago, just after a phone call, it rebooted and did not come back. I took the battery out for the night, but still did not come back.
The bootloader is unlocked, but I was using stock gingerbread. I can get into fastboot, but not recovery. I tried the PASSIMG method a couple of times, and tough the flashing did succeed, the phone keeps stuck at the X logo.
The last radio flash was 5.08, when ginger came. Does this means my device is bricked? To make matters worse, it seems I'm out of warranty...any of you guys have any clue to help me? Or is it all lost and I should get a new phone??
Thanks!
If you're booting - you're not bricked. Brick = NOTHING on the phone, no reaction whatsoever to anything, won't turn on.
Anyway, since you have your bootloader unlocked - fastboot flash recovery recovery.img, and then try to boot into recovery, see if it works. Read the Wiki to help yourself.
Hi Jack, thx for the reply!
I already tried that; the flash succeeds, but I cannot get into recovery. If I try to reboot into recovery, it still gets stuck at the X logo.
I understand that brick == nothing at all; but I suspecting that the GSM modem is history. I was already having rebooting problems with it, and now it seems that it's dead and the phone will not boot because of it. Does this makes sense?
Have you tried "fastboot boot recovery.img"?
danger-rat said:
Have you tried "fastboot boot recovery.img"?
Click to expand...
Click to collapse
Just tried it, the phone reboots, but vibrates 7 times and does not boot, still in the X logo...
7 vibrations - means you have some HW problem, and the phone won't boot. Yes, I guess that even though you're not bricked, the phone isn't usable and needs to be fixed/replaced. Sorry.
That was what I was afraid....I had this "7 vibration" stuff happen before, but I was able to get it back on track...
Thx all for the help, time to get a new gadget

Categories

Resources