I've had the great misfortune of bricking my phone within the first few hours of owning it. I should have known something was up, it wouldn't reboot when I changed the language to English, and I'd have to hard reset it (delete everything) and then let it load in Chinese again. Well, in an attempt to fix what I thought was a rom issue, I went through the song and dance of trying to root my phone.
I'm still not fully clear on how to do it, as it seems there's more to it than just what the tutorials say.
Anyway, like the title of this thread says, there's a pretty good way to figure out if your phone is really bricked, no need to ask or wonder anymore.
If your phone only boots to the htc magic screen (and then stops), and is unable to load bootloader, fastboot, usb connections, or anything else, it's bricked. 100%. You have to take it back. Don't bother searching the forums for the answer, I've wasted hours going through every related thread and trying every possible solution. Without the ability to access the fastboot screen, you're out of possibilities. Untill someone comes out with an unbricker which goes deeper than fastboot, there is absolutely no way to fix it.
A semi brick is much better on the other hand. There are plenty of ways to fix your phone, provided you're only semi bricked. I would define semi bricked as being able to enter fastboot, but being unable to boot the phone as normal. This can happen with a bad flash, or a mis step during a tutorial. I'm not exactly sure how easy it is to change a semi brick to a full brick, but my full bricking happened after semi bricking it while loading a new rom on it.
So. to summarize, if your phone WON'T go into the boot menu by pressing vol-down+power, you're in need of a new phone.
If you can still get into the boot menu, and access your phone through usb, you're ok, just get help (via a tutorial) before going any further, unless you're completely certain of what to do next.
Tis a shame to send a device, which is physically undamaged, to the digital graveyard. But such is life.
Caid.
444.
EDIT
on a side note, before my phone reset itself into it's endless loop of unloading, I noticed the screen flash an image of a box with what looked like a red arrow coming out of it. It was right in the center of the screen. This was in the recovery-RAv1.0H.img menu. What's that all about?
Did you try other key combinations such as Home+Power, or Back+Power?
I'm sorry but I think you're misunderstanding it all a little bit...
Caid444 said:
I've had the great misfortune of bricking my phone within the first few hours of owning it. I should have known something was up, it wouldn't reboot when I changed the language to English, and I'd have to hard reset it (delete everything) and then let it load in Chinese again. Well, in an attempt to fix what I thought was a rom issue, I went through the song and dance of trying to root my phone.
I'm still not fully clear on how to do it, as it seems there's more to it than just what the tutorials say.
Anyway, like the title of this thread says, there's a pretty good way to figure out if your phone is really bricked, no need to ask or wonder anymore.
Click to expand...
Click to collapse
It's easy if you follow the guides... I did it in two different phones with no problem at all in any of them... Anyway, let's stay on topìc
Caid444 said:
If your phone only boots to the htc magic screen (and then stops), and is unable to load bootloader, fastboot, usb connections, or anything else, it's bricked. 100%. You have to take it back. Don't bother searching the forums for the answer, I've wasted hours going through every related thread and trying every possible solution. Without the ability to access the fastboot screen, you're out of possibilities. Untill someone comes out with an unbricker which goes deeper than fastboot, there is absolutely no way to fix it.
Click to expand...
Click to collapse
Wrong. If your phone boots to the HTC Magic screen, the bootloader is doing it's job. The bootloader just takes you there. The linux kernel and ramdisk takes you to the boot animation, and there is where android really starts.
If your phone shows the first htc logo, or the Vodafone branded screen, you can start in bootloader mode. To make that you just have to remove the battery, put it back, and press and hold BACK + END KEY. From that, you can fastboot.
Also, and unless you destroyed the recovery partition, you can also boot in recovery mode, by pressing END KEY while holding HOME (no need to keep them both hold, just home button)
Caid444 said:
A semi brick is much better on the other hand. There are plenty of ways to fix your phone, provided you're only semi bricked. I would define semi bricked as being able to enter fastboot, but being unable to boot the phone as normal. This can happen with a bad flash, or a mis step during a tutorial. I'm not exactly sure how easy it is to change a semi brick to a full brick, but my full bricking happened after semi bricking it while loading a new rom on it.
Click to expand...
Click to collapse
I would call a semi brick this:
Your phone goes into an endless loop while booting.
Your phone gets stucked on the first boot logo.
You can't get access to the recovery partition.
Your phone boots all the way but then gets stucked.
Your phone gone bad during a software update.
That, all, can be solved by reflashing the affected region. There are tutorials for everything but if you need I can write some hints on each case (I suffered them all ).
Caid444 said:
So. to summarize, if your phone WON'T go into the boot menu by pressing vol-down+power, you're in need of a new phone.
Click to expand...
Click to collapse
Actually, VOLDOWN+POWER starts in Hboot mode. From there you can go back to fastboot mode, but hboot is used to make a software upgrade using complete images or running htc diagnostic images (SAPPDIAG.IMG, SAPP*.IMG /NBH).
Caid444 said:
If you can still get into the boot menu, and access your phone through usb, you're ok, just get help (via a tutorial) before going any further, unless you're completely certain of what to do next.
Tis a shame to send a device, which is physically undamaged, to the digital graveyard. But such is life.
Click to expand...
Click to collapse
If you can't get USB working on fastboot mode, or on recovery mode, your phone has probably a hardware fault. It happened with some of the first revisions of the Vodafone branded magic, don't know about htc branded ones though..
NOTE: Not talking about missing drivers, if you don't have drivers, that's another problem, but the computer should at least detect the device. Also, if your phone is off, and you connect the charger (or usb) and the orange led lights up, the bootloader should be ok.
Caid444 said:
on a side note, before my phone reset itself into it's endless loop of unloading, I noticed the screen flash an image of a box with what looked like a red arrow coming out of it. It was right in the center of the screen. This was in the recovery-RAv1.0H.img menu. What's that all about?
Click to expand...
Click to collapse
That's the recovery mode. With that you can unbrick your phone
Also, as another hint, if you're new to linux OSes, you might want to take a look at some manual on terminal commands. If your main software is bricked, it's possible that your SDCard doesn't get mounted on recovery mode, depending on wich recovery image you're running. Provided you have an update.zip on the sdcard you need to run, you might have to mount it manually.
To do that, you have to start the phone in recovery mode, and run an "adb shell" on the PC.
When you have a shell opened, you'll have to mount the sdcard manually:
mount /dev/block/mmcblk0p1 /sdcard
Then, on the phone you can use the option to run sdcard update.zip to restart the software upgrade procedure.
Regards!
Before I reply, I'd just like to say thank you very much for your extremely in depth reply.
biktor_gj said:
I'm sorry but I think you're misunderstanding it all a little bit...
It's easy if you follow the guides... I did it in two different phones with no problem at all in any of them... Anyway, let's stay on topìc
Wrong. If your phone boots to the HTC Magic screen, the bootloader is doing it's job. The bootloader just takes you there. The linux kernel and ramdisk takes you to the boot animation, and there is where android really starts.
If your phone shows the first htc logo, or the Vodafone branded screen, you can start in bootloader mode. To make that you just have to remove the battery, put it back, and press and hold BACK + END KEY. From that, you can fastboot.
Also, and unless you destroyed the recovery partition, you can also boot in recovery mode, by pressing END KEY while holding HOME (no need to keep them both hold, just home button)
I would call a semi brick this:
Your phone goes into an endless loop while booting.
Your phone gets stucked on the first boot logo.
You can't get access to the recovery partition.
Your phone boots all the way but then gets stucked.
Your phone gone bad during a software update.
That, all, can be solved by reflashing the affected region. There are tutorials for everything but if you need I can write some hints on each case (I suffered them all ).
Actually, VOLDOWN+POWER starts in Hboot mode. From there you can go back to fastboot mode, but hboot is used to make a software upgrade using complete images or running htc diagnostic images (SAPPDIAG.IMG, SAPP*.IMG /NBH).
If you can't get USB working on fastboot mode, or on recovery mode, your phone has probably a hardware fault. It happened with some of the first revisions of the Vodafone branded magic, don't know about htc branded ones though..
NOTE: Not talking about missing drivers, if you don't have drivers, that's another problem, but the computer should at least detect the device. Also, if your phone is off, and you connect the charger (or usb) and the orange led lights up, the bootloader should be ok.
That's the recovery mode. With that you can unbrick your phone
Also, as another hint, if you're new to linux OSes, you might want to take a look at some manual on terminal commands. If your main software is bricked, it's possible that your SDCard doesn't get mounted on recovery mode, depending on wich recovery image you're running. Provided you have an update.zip on the sdcard you need to run, you might have to mount it manually.
To do that, you have to start the phone in recovery mode, and run an "adb shell" on the PC.
When you have a shell opened, you'll have to mount the sdcard manually:
mount /dev/block/mmcblk0p1 /sdcard
Then, on the phone you can use the option to run sdcard update.zip to restart the software upgrade procedure.
Regards!
Click to expand...
Click to collapse
To the first answer.
It's not THAT easy, the guides are kinda (you should already know what you're doing at this point) in nature. It's confusing for newcomers, as we've no idea what to expect, that and there are a multitude of variations. More specification as to which guide works with which model, and which updates would be nice.
As for the second part, I could not get the phone working with any button variation pressed. I'm sorry I was not more clear in my description, to begin with. I could press (and hold) any button (or buttons) + power (end key) and the phone would just vibrate (briefly) and then display the original screen "htc magic"(endlessly). The orange light does come on when plugged into the usb or computer, but only while it is off, as soon as the device turns on, the light turns off.
Another thing of note is that, after bricking it, I had to remove the battery to turn it off (every time if it was on), and if I put the battery back in while it's plugged into the usb port of the computer, the phone would turn back on without pressing any buttons. It's also completely unresponsive or detectable by my computer after bricking it. The only other thing I can get it to do is make the orange light blue by holding the action button and turning on the device. That way the light on top of the device is blue when it turns on. Still unresponsive at that point.
This is my first android device, but not my first htc device (I've had MANY MANY different ones.) so I'm a bit familiar with trying different combinations to get a response.
I am not the first person who's had this happen, unfortunately. There have been a couple others, who've described the exact same encounter. Perhaps it's a mistake that I made, and perhaps they also made it themselves. I would like to figure out how it's happening, though, and perhaps write a tutorial for people like us unlucky few.
Again, a really big thanks. I've sent my phone back and am getting a new one soon. I much appreciate your reply, however, as it's probably the most understanding and considerate reply I've seen on these forums.
Cheers.
Caid.
444
One more quick question out of curiosity, when you press and hold back and press end to turn on the device (it still goes to the htc magic screen) SHOULD it go to a different screen, other than the "htc magic" screen? Or is that a process that runs without some sort of visual notification on the device itself?
The usb was completely unresponsive after this happened, but in the event that bootloader may have been running, (only possible if it runs without any visual notification on the device itself), I'll go pick up the device and see if my usb drivers on my computer just became unresponsive after being accessed too many times. Sometimes windows does that, right? Perhaps a reboot would have allowed fastboot and the drivers to connect again, if the device was trying to talk to the computer, but I just didn't know on account of not having any notification.
So, again, should pressing back and power bring me to a different screen? or would it also look like it was hanging on htc magic screen?
Caid.
444
p.s. Sorry for the confusing wording, I'm tired and trying very hard to be as specific as possible.
back+end/power should lead you to the fastboot screen right after it shows the HTC Magic screen or whatever splash screen you have installed.
Home+end/power should lead you to the recovery screen.
ok, it was bricked. Thanks for the answer.
Caid.
444
Caid444 said:
Before I reply, I'd just like to say thank you very much for your extremely in depth reply.
To the first answer.
It's not THAT easy, the guides are kinda (you should already know what you're doing at this point) in nature. It's confusing for newcomers, as we've no idea what to expect, that and there are a multitude of variations. More specification as to which guide works with which model, and which updates would be nice.
Click to expand...
Click to collapse
No problem, we all should be here to learn, and to help (except for the trolls)
This is the guide I followed for both Vodafone branded Magics: http://android-dls.com/wiki/index.php?title=Magic_Rooting
Maybe not for now, but for the next magic you get it may come handy
Caid444 said:
As for the second part, I could not get the phone working with any button variation pressed. I'm sorry I was not more clear in my description, to begin with. I could press (and hold) any button (or buttons) + power (end key) and the phone would just vibrate (briefly) and then display the original screen "htc magic"(endlessly). The orange light does come on when plugged into the usb or computer, but only while it is off, as soon as the device turns on, the light turns off.
Click to expand...
Click to collapse
When the phone is off with the charger connected and you press the power button, the light goes off, as for the others, you really should be able to enter the SPL if it could the magic bootlogo and vibrated upon boot...
Maybe you didn't try enough or maybe your bootloader behaved differently than mine... I should be more clear anyway, to get to the bootloader, the best way to make it go to the bootloader is press and hold back key, then while holding it, hold the power button too. It should take about a second or two before showing the three skater droids.
Caid444 said:
Another thing of note is that, after bricking it, I had to remove the battery to turn it off (every time if it was on), and if I put the battery back in while it's plugged into the usb port of the computer, the phone would turn back on without pressing any buttons. It's also completely unresponsive or detectable by my computer after bricking it. The only other thing I can get it to do is make the orange light blue by holding the action button and turning on the device. That way the light on top of the device is blue when it turns on. Still unresponsive at that point.
Click to expand...
Click to collapse
When you put the battery while USB or charger is connected, the phone boots up, that's the normal behaviour. About the blue led, that's the Radio bootloader. That's quite dangerous to play with, but it gives a lot of other functions. Another sign that your phone wasn't completely dead Even if you wipe the SPL (the three skater droids), you may be able to boot into the Radio bootloader and write or boot another one to fix it. But that's waaaay harder
Caid444 said:
This is my first android device, but not my first htc device (I've had MANY MANY different ones.) so I'm a bit familiar with trying different combinations to get a response.
I am not the first person who's had this happen, unfortunately. There have been a couple others, who've described the exact same encounter. Perhaps it's a mistake that I made, and perhaps they also made it themselves. I would like to figure out how it's happening, though, and perhaps write a tutorial for people like us unlucky few.
Click to expand...
Click to collapse
I guess the first advice when you start tricking with a phone is be careful with what you're doing. That's the good thing of fastboot.
When booting on fastboot mode, you can pick, for example a recovery image, and boot it without overwriting the original rom:
Code:
fastboot boot [recovery_image]
Then, when you see it's working, you can flash it:
Code:
fastboot flash recovery [recovery_image]
fastboot flash boot [boot_image]
fastboot flash system [system_image]
fastboot flash data [data_image]
You can't do that with the system.img since it's too big, but you can do it also with a boot.img
About the key combinations on the phone, it goes like this:
Code:
BACK + END KEY -> Fastboot mode (you shouldn't see the boot logo)
VOLDOWN + END KEY -> Hboot mode (you shouldn't see the boot logo)
ACTION (trackball center) + END KEY -> Radio Bootloader (you shouldn't see the boot logo)
HOME + END KEY -> Recovery mode (you should see the boot logo, then get the recovery menu)
SEND + MENU + END -> Reboot the phone (while the phone is on)
Maybe there are more (android has kind of 'safe mode' but I don't know it it goes there automatically if there's a problem or if it has to be called manually)
Anyway, I hope these things will be useful for the next phone, and for anybody who's a bit lost on this
Regards!
Let us know where you live , so maybe one can help you , I live in Sweden and will be glad to help you if you are near ;-)
Hey! Thanks again for all the help, and the offer to come help. Unfortunately, I'm in China. Coming here from Sweden (although it's a single large landmass) would take quite a bit of time
I appreciate all the support, though. Very cool community we're building here for the magic.
Caid.
444
htc semi-brick?
Hi to all. I'm in the same condition described in this tread; after installing SPL i get the htc block in Vodafone brand red screen.
None keys combination bring me to the boot menù. Only Action(trackball) + power have effect, but with a black screen...
Any suggest?
What do you do if you can boot into fastboot but can't flash anything because absolutely everything gives the error "FAILED (remote: signature verify fail)"?
I have a card reader and have tried just about every sappimg.zip, every boot.img, every recovery.img i could find. I can't even boot a recovery img because the screen just hangs at the HTC Magic logo.
I don't know what kind of warranty i have on this thing, but i might take it in tomorrow and see if i can get it replaced. I've only had it for just under two weeks.
Newbie need help
ok so i can still go to recovery mode but everytime i reboot my phone the mytouch 3g logo never goes away im new to Android but not htc can somebody plz help me out.
gruppler said:
What do you do if you can boot into fastboot but can't flash anything because absolutely everything gives the error "FAILED (remote: signature verify fail)"?
I have a card reader and have tried just about every sappimg.zip, every boot.img, every recovery.img i could find. I can't even boot a recovery img because the screen just hangs at the HTC Magic logo.
I don't know what kind of warranty i have on this thing, but i might take it in tomorrow and see if i can get it replaced. I've only had it for just under two weeks.
Click to expand...
Click to collapse
Instead of flashing something, you boot a recovery image, and then, from there, you flash whatever you need (using adb & flash_image for example)
PS: Be a little patient, if fastboot is letting you boot a recovery image, the recovery needs to boot, and that takes a little while, and while it's booting, you see the bootlogo until the menu appears. Also, you can try running adb shell after boot process started to try to get an error message (or at least to know if the thing is booting in some way)
I couldn't boot any recovery images. I had tried a few different Hero ROMs but decided i wanted to use Cupcake again because i have a 32B board and it just doesn't have enough RAM, though Swapper makes it usable at least. I don't know what exactly i did, but i've learned a lot from my mistakes. Everything i tried failed the signature check because the hboot version didn't match. If i could just flash the 1.33.2005 hboot again, i would have been in business, but no matter which recovery image i tried, it just sat there doing nothing. And believe me, i waited.
Fortunately, T-Mobile gave me a new device after i took it in and played dumb. And I just rooted it =]
Caid444 said:
ok, it was bricked. Thanks for the answer.
Caid.
444
Click to expand...
Click to collapse
Why not flashing it with an RUU from HTC. Not sure that would work but it is worth trying.
Hi there, people!
First of all, thanks because while I was reading ur posts I realized that my phone had been bricked, 100 %
I tried official ROM upgrade to Android 1.6 using the folowing steps
1. Copied radio zip to my sd card by renaming it in update.zip
2. Recovery screen was started by pressing HOME+END key
3.Applied update.zip, process was going on: Opening package, verifing package, installing radio...and message about success was shown and phone restarted
4. Phone stucked on HTC Magic logo screen...15 minutes
5. I removed a battery, put it back and tried to reach recovery or boot mode again
6.Unsuccessfully! Phone vibrates and turns on...but always stucks on the HTC Magic screen
7. USB does not recognize my phone is connected (I tried any adb and fastboot commands)
8. So, I just pray to give me a new phone if my warranty will be accepted
iivanovic said:
Hi there, people!
First of all, thanks because while I was reading ur posts I realized that my phone had been bricked, 100 %
I tried official ROM upgrade to Android 1.6 using the folowing steps
1. Copied radio zip to my sd card by renaming it in update.zip
2. Recovery screen was started by pressing HOME+END key
3.Applied update.zip, process was going on: Opening package, verifing package, installing radio...and message about success was shown and phone restarted
4. Phone stucked on HTC Magic logo screen...15 minutes
5. I removed a battery, put it back and tried to reach recovery or boot mode again
6.Unsuccessfully! Phone vibrates and turns on...but always stucks on the HTC Magic screen
7. USB does not recognize my phone is connected (I tried any adb and fastboot commands)
8. So, I just pray to give me a new phone if my warranty will be accepted
Click to expand...
Click to collapse
I have the same problem. I get up hboot and fast boot menus can not get it in recovery. try to add in sappimg but no luck
I'm having the exact same problem...
Any solution yet?
Hello! I can assure you that your phone is not fully bricked! Awhile ago I flashed a new radio only to discover that I hadn't done my research and was a complete and total idiot. I flashed the 1.76.xxxx on a 32B. It didn't like it. I got a quick HTC logo that disappeared then the phone never responded again. When I say never responded it was dead. no combination of buttons would get any response. If you can get into fastboot you have options. All that's necessary is to make sure you have the appropriate sappimg file. Try the Unlockr's gold card method file. He has a .zip file that may work for you. Just make sure that you find an image that is compatible with your board (32A or 32B). Hope this helps!
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator
edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
Click to expand...
Click to collapse
wow so much information don't know where to start!!!
hard to say..someone managed to the the phone to respond to fastboot/adb by starting up ADB..
wait for the waiting for device msg, then connect the phone to usb and turn it on.
if all method fails, bring it back to claim for warranty.
edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator
Click to expand...
Click to collapse
What OS are you using on your computer?
zeroplace said:
What OS are you using on your computer?
Click to expand...
Click to collapse
I tested with Windows 7, Vista and XP and the same.
You know any way to flash as factory?
Will it actually turn on or does it just flash a red led when you press power?
bonesy said:
Will it actually turn on or does it just flash a red led when you press power?
Click to expand...
Click to collapse
Starts, appears the splash but only gets to that point
In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info
bonesy said:
In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info
Click to expand...
Click to collapse
I have tried many times to do this and nothing ever stays <waiting for device> and does nothing
Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.
daihiep said:
Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.
Click to expand...
Click to collapse
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
The magic will hang at the first splashscreen no matter which buttons are pushed during power up. If the track ball is pressed during power on, the led lights up blue (still hanging at first splash). All other combos of buttons during power on makes no difference at all.
I have tried keeping fastboot waiting while power cycling the device (as explained in another thread), but there are no reaction. I have tried in xp, vista and linux.
I have also tried with a gold card, but since the phone seems unable to get any further than the first splash, this will not work.
So unless someone has a _NEW_ method to actually enter fastboot/ADB mode, these devices are BRICKED!
People have been discussing what the criteria for calling a phone a brick, but as far as I have care my Magic can only function as a paper weight and can therefore be called bricked.
Help
I have the same problem , the fastboot can not acces, i stay at the vodafone logo.
Any ideas?
HHHHHHHHHHHEEEEEEEEEEEELLLLLLLLLLPPPPPPPPPP.
frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
Click to expand...
Click to collapse
take out the sd card, put it in a usb adaptor and copy them over.
Also search for a thread "how i unbricked my phone"
frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Click to expand...
Click to collapse
Think before answering.
Btw, question answered by htcmagic.
daihiep said:
Think before answering.
Btw, question answered by htcmagic.
Click to expand...
Click to collapse
I repeat: The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Having a recovery image and a custom rom on the SD card is useless if you are not able to get the phone accessing those files.
I have tried the "how I unbricked my phone" method (like I wrote in my first post) without any success. If you read the whole "how I unbricked my phone" thread you can see that there are several guys that did not have success with this method.
I have done a lot of thinking.... and searching...
Thanks
http://forum.xda-developers.com/showthread.php?t=571457 try there
Wrong HBOOT = real brick
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.
just curious.
superkikim said:
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.
Click to expand...
Click to collapse
How did you brick it?
Btw, have you tried to run any RUU update?
At least singapore one.
I have a Motorola CLIQ on the blue screen of death that reads BOOTLOADER USB INIT... and that's it.
Is there ANYWAY for me to fix this? re-flash the phone, re-load android OS, something....????
just try every possible thing you just said,
flash shx firmware
you'll have to flash an shx firmware. look at ModMyMoto - Motorola CLIQ/DEXT - CLIQ & DEXT firmwares Superthread (sticky)
flash this fw w/ rsd lite:
Branding: T-Mobile US
Version: 1.3.18
Bootloader Version: 05.15
Requires RSD Lite 4.5.7.
I have almost the same problem, but mine stays on White Motorola logo.
I wiped my cliq using adb shell wipe all command and now I can't re-flash on RSD Lite because it says "Please wait for all-TCI ready, and try again..."
When executing a adb shell command it returns this error: - exec '/system/bin/sh' failed: No such file or directory (2) -
running adb devices returns:
List of devices attached
0391255714 device
Is there any way to access its internal storage and reflash?
I have tried reflashing the phone several times, it says it completes successfully - but always reboots in to this blue screen with bootloader usb init at the bottom.
any other suggestions?
Latest update: (and it's a bad one)
I downloaded tmo-morrison-viper-1.1.31-P3-rootedbythedude.shx file, flashed it using usb drivers 4.20 and rsdlite 4.5.7
It claimed it flashed successfully, but the phone never rebooted... just stayed on the blue screen with the bootloaded usb init on the bottom.
Now, I've tried to re-flash with either that same .shx file and it error's out. Then I thought maybe unrooting it would work so I tried tmo-morrison-viper-1.1.31-P3-supermonster-customer.shx and it error's out.
I originally tried tmo-morrison-viper-1.1.4-20091012-2014-cprintf-appsbl-P3-secure-supermonster-customer.shx, and it worked and flashed BEFORE today and BEFORE tmo-morrison-viper-1.1.31-P3-rootedbythedude.shx
At this point, the only thing that has changed is now whatever I try to flash, fail's immediately. It only power's on when the usb cable is inserted. I goes straight to the bluescreen with bootloader usb init on the bottom in white characters.
I'm pretty much STUMPED at this point.
Here is a screen shot of what RSDLITE shows when this cliq is connected. Anyone got any suggestions?
Maturz i am having the EXACT same problem. RSD is saying TCI ****, phone boots to the white moto logo, adb won't work. i have NO idea where to take this. The only menu i've seen that looked promising was the recovery menu which you reach by holding camera during boot. By holding(no stickykeys) ALT and hitting L you can see its menu. The options are to run an update.zip( I can't find a single file it will accept as signed/not fail executing), wipe, or restart. The wipe does not fix this issue. PLEASE tell me if you fix your device, I've got a mirror with a keyboard and its a serious bummer. This problem occurred while flashing a rom. RSD ****ed up. Some claim they can get the charging firmware to mount something ADB can talk to by plugging the phone into the wall and then switching to the computer quickly..but i haven't been able to get this to work.
i had this very same problem and i fixed it through rsd flashing the latest firmware. i lost root in the process but i don't have a brick anymore
moxiot said:
i had this very same problem and i fixed it through rsd flashing the latest firmware. i lost root in the process but i don't have a brick anymore
Click to expand...
Click to collapse
Which file did you flash to it? I'm stuck now - where it won't seem to accept any flashing now ... PLEASE HELP
OMG I sumwhat did it!
Turn ur phone off, than at the same time press power, star button & pound button that reboots and start as usual HOWEVER when u turn off the phone it goes back to blue screen! I figured this much maybe now I can reinstall android 2.0 hmmm! Email me [email protected] if u figured it out from there hop'e this help' ;0)
Cordellnj said:
Turn ur phone off, than at the same time press power, star button & pound button that reboots and start as usual HOWEVER when u turn off the phone it goes back to blue screen! I figured this much maybe now I can reinstall android 2.0 hmmm! Email me [email protected] if u figured it out from there hop'e this help' ;0)
Click to expand...
Click to collapse
Can you post the solution here?
HELPPPP
Flashed the original firmware with red light and it failed now my phone stays with a black screen but the keys light up :'(
Bummer!
my phone only turns on when i connect it to the charger and it boots to a Black screen with a blue bar at the bottom that reads "Bootloader USB Init" no motorola logo.
has anyone else ran into this? i had the logo before i flashed "tmo-morrison-viper-1.1.31-P3-supermonster-customer.shx"
Someone help me! this was supposed to be a xmas gift for my sister but now it feels like paper weight.
buddie024 said:
my phone only turns on when i connect it to the charger and it boots to a Black screen with a blue bar at the bottom that reads "Bootloader USB Init" no motorola logo.
has anyone else ran into this? i had the logo before i flashed "tmo-morrison-viper-1.1.31-P3-supermonster-customer.shx"
Click to expand...
Click to collapse
what exactly happened? why did you have to flash?
Hey guys. I'm kinda desperated so let's see if there is anything else I can do.
I was playing a game on my phone and it started rebooting alone.
At this point, I long pressed the power button, don't ask me why, but I did it. and bang. it is dead. No boot, no loading, nothing. It still vibrates when I try to turn it on.
I had 30% Battery left.
I have root and my phone for 3 months.
I had Nandroid backup.
Long press power button, volume up + power, volume down + power doesn't work.
When connected to PC, I get the QHSUSB_BULK device on.
Tried to ColorOS Method but:
I cannot install ColorOS drivers cause it doesn't detect them.
I tried Qualcomm drivers and they worked, so then I used the program Msm8974DownloadTool to install ColorOS.
It went okay, all finished and I got the green letters in the end.
Still doesn't boot up, nothing changed.
I cannot detect my phone via ADB. Tried with the drivers and without the drivers and with clean drivers.
What can I do? I always had such care for my phone in case of an emergency, but for some weird reason this happened. I wasn't even messing up with the phone, it just died cause I turned it off while booting up?
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
cyldman said:
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
Click to expand...
Click to collapse
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
jukiewalsh said:
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
Click to expand...
Click to collapse
What do you mean I lost my adb access? I can still find my phone there and it's still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesn't boot back up.
cyldman said:
What do you mean I lost my adb access? I can still find my phone there and its still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesnt boot back up.
Click to expand...
Click to collapse
Disregard that then, when the phone is booted you have to manually give adb access but you're right when it's in recovery or other modes it's already there.
Does your screen power on at all? Do you think your LCD/digitizer could've somehow just died on you?
I highly doubt it, it happened when I shut off the phone when it was rebooting. I dont hear anything when I turn on the phone and i cant press anything or slide to unlock. nothing. so ....yeah. Weird stuff is that I did fastboot reboot and now i can't get to fastboot again. sigh.
Read this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
Somewhere within it is the solution to your QHSUSB_BULK problem.
Already did bro, and I fixed it, did you even read my full post? I managed to install colorOS, but it's still not booting up.
Hello guys! Last update! My phone was not even vibratting when i pressed power button. I put it to charge and finnaly I got a screen. its not what I wanted...but its a small step!
Its the Low battery charge icon! So...I've heard about this other issue about the phone not charging. Could this be it? I will be trying some techniques like https://forums.oneplus.net/threads/...een-opo-not-booting-due-over-discharge.88107/.
Hopefully it will help, but it may take some days.