Hi,
I had made a major mistake for being impatient. I tried to flash this radio: 32.56.00.32U_5.17.05.08 because im trying to use Leedroid HD V3.3.3 for the first time and it recommended that radio. I flashed the radio via recovery and it rebooted into a blank screen. From what i read from forums, it is supposed to reboot into a screen with an arrow to process the radio update and since that did not happen, i waited for a minute or two and popped out the battery.
Now what i got is vibrations 7 times and a blank screen every time i want to power on my phone. I tried every key combination; Vol- & Power, Back & Power, but it still gives me the the 7 times vibrations. ADB and Fastboot does not work via PC, does not detect phone at all.
I tried to do a blind flash using PB99IMG.ZIP method guided by youtube video but im not quite sure if it the bootloader actually loaded or not since it vibrates 7 times on everything i tried, but so far no success.
If the answer to my problem is my phone is bricked and nothing can be done, then i have a few questions:
1- I am still under warranty, but my phone is currently S-OFF by AlphaRev and using custom ROM (Leedroid HD).
What are the chances that the engineers over the customer service center can actually restore my radio via some techniques that i don't know of and found out that i actually S-OFF my phone and using custom ROM? because if they found out, my warranty will be void.
2- Is there any other method that can only used by official engineers to restore bricked phones? Methods using special hardware tools that are not made available to the public?
Hope somebody can help me soon.
Congrats! You have succesfully bricked your phone.
You should never pull out the battery when messing with radios... But its kinda late now...
...aes eht rednu
peed morf tneS
But in bricked state, does the engineer/technician for the official service center can do anything about it? Or atleast check if I S-OFF and use custom rom to invalidate my warranty?
tablighs said:
But in bricked state, does the engineer/technician for the official service center can do anything about it? Or atleast check if I S-OFF and use custom rom to invalidate my warranty?
Click to expand...
Click to collapse
Thats a bit difficult... Because radio is the essential part that communicates between the os and the hardware. When that is messed up, your phone is obviously dead, cause the hardware its self doesnt know what to do....In such occasions it might be difficult even for htc to revive it... But you could risk it and say to htc that you were applying an ota update when that happened. Dont mention that you pulled the battery and you might be lucky... But no word for root/s-off/custom rom
...aes eht rednu
peed morf tneS
Okay thanks!
Im sending it to htc in around 2 weeks time (currently in overseas). Hope the repair guy is lazy to try much and just give me a new phone , wish me luck!
Hi, Did you send your phone to HTC? I have the same problem, the phone is s-off but it does not boot so im unsure if HTC will notice this.
Thanks
A simple JTAG session would easily restore it.
Related
Ok, you can get into BL, flash roms, but no recovery and the phone doesnt boot, basicly a boot loop. Now if i RMA this phone and they go into bootloader and see the S-Off flag, will this more than likely void my warrenty or would they have any clue about this? If so, i guess i could flash a radio and pull the battery during the flash to ensure they cant read that lol.
Any help/info is appreciated, thanks
K, guess no one has a answer for wether or not HTC Service & Repair center will know what S-Off means if they put my phone in bootloader when i send them back a phone that wont boot so i cant reverse the unrevoked forever as far as i know, if im wrong, maybe someone can correct me. Would hate to have them not warrenty the phone due to being able to see the S-Off flag in bootloader.
I guess i could brick it bad enough they cant get into bootloader, just was hoping for some feedback so i didnt have to damage the phone more than it already is lol.
anderd said:
K, guess no one has a answer for wether or not HTC Service & Repair center will know what S-Off means if they put my phone in bootloader when i send them back a phone that wont boot so i cant reverse the unrevoked forever as far as i know, if im wrong, maybe someone can correct me. Would hate to have them not warrenty the phone due to being able to see the S-Off flag in bootloader.
I guess i could brick it bad enough they cant get into bootloader, just was hoping for some feedback so i didnt have to damage the phone more than it already is lol.
Click to expand...
Click to collapse
There is an S-ON tool on the Unrevoked Forever page. You can use that.
If you used Toast's method, all you have to do is get back to a SHIP bootloader. You can do that easily by running an RUU.
anderd said:
Ok, you can get into BL, flash roms, but no recovery and the phone doesnt boot, basicly a boot loop. Now if i RMA this phone and they go into bootloader and see the S-Off flag, will this more than likely void my warrenty or would they have any clue about this? If so, i guess i could flash a radio and pull the battery during the flash to ensure they cant read that lol.
Any help/info is appreciated, thanks
Click to expand...
Click to collapse
Your phone boots -> it is not bricked. Don't RMA it until you try to resolve the problem.
To answer your question.....yes if they figure out you put unapproved firmware on the phone they do have the right to void your warranty..yes its legal now but htc or sprint can choose to void..that being said like jerryparid mentioned if it boots its not bricked so try to fix, do some searching you might just find an answer that helps.....also I'd get your flame suit on because it might get hot in here.
jerryparid said:
Your phone boots -> it is not bricked. Don't RMA it until you try to resolve the problem.
Click to expand...
Click to collapse
He's right. If your phone boots at all, even if it's just into the bootloader then it is fixable.
There may be better ways of doing it but I would suggest you download the ENG HBOOT from toasts rooting part 2 thread, put it on the root of your sdcard and boot into your bootloader and just let it run. You'll have to set everything back up, including updating your recovery image but at this point there is no reason to have it replaced just yet.
Let us know how it goes, if you need any help bringing your phone back to life we're here for ya!
User Name
Ok let me try and clarify this...
I can get into bootloader, i can flash a rom, radio, hell even RUU from PC, all complete 100%, can not get into recovery, even if i flash a recovery image. The phone DOES NOT BOOT, starts at white HTC start up screen, stay on for about 4 seconds, reboots. You can clear storage, reload roms, radios, none of that gets the phone to boot or do anything other than reboot every 4 seconds.
So nothing i can think of will fix this, ive tried roms loaded via SD card, via RUU from PC when phones in bootloader, reflashing radios, reflashing recovery, nothing works. Phone continuesly reboots after first 4 seconds of being powered on. Never boots past HTC screen. I guess i should just try and brick it 100% so they cant get into boot loader and see the S-Off flag.
Damn phones.. lol...
** EDIT **
In short i guess basicly all im saying in the above, is ive tried everything already mentioned so far prior to my post and none of that did jack squat for me... lol.
How are you flashing roms from the bootloader?
And if you cant get into recovery how are you "clearing storage"?
No offense, I understand your frustration but I have to think you're not doing something right.. You'd be the first (not saying it's impossible) person to have a phone that gets into the bootloader but is not fixable..
nebenezer said:
How are you flashing roms from the bootloader?
And if you cant get into recovery how are you "clearing storage"?
No offense, I understand your frustration but I have to think you're not doing something right.. You'd be the first (not saying it's impossible) person to have a phone that gets into the bootloader but is not fixable..
Click to expand...
Click to collapse
Ok, yet again, a clarification, i cant get into a Custom Recovery, power+vol down, all that works fine, can flash rom (load the zip on the sd card, detects, lets you flash via zip) or via RUU in windows this method, now if you scroll down to "recovery" on the menu and click on it, it starts to load then phone reboots and back to square one. Sorry if my hboot/bootloader/recovery understandings are slightly off or differ from anyone elses.
** EDIT **
Ill see if i can make a youtube video with my crappy webcam here in a bit and upload it and maybe that will make it easier to understand whats going on. I had also taken it to a sprint repair center and they couldnt figure it out themselfs lol. So if i can fix it myself, im going to get it to HTC before i my luck runs out some how and they wont fix it lol. THanks for the help guys, i appreciate the replys and help so far!
I installed this update last night and it straight up bricked my phone. Starting with volume down and doing a hard factory reset leaves the phone hung on the white screen with HTC on it.
The phone is covered under warranty and I'll be getting a box shipped to me to send it in for repair. It is the 6-8 week turn around on the repair that troubles me.
The following briefly flashes on the screen when loading up that volume down / power screen:
SD Checking…
Loading…[PC10DIAG.zip]
No image!
Loading…[PC10DIAG.nbh]
No image or wrong image!
Loading…[PC10IMG.zip]
No image!
Loading…[PC10IMG.nbh]
No image or wrong image!
Knowing this, is there anywhere I can download these files and place them onto the SD card to see if I can't unbrick this thing myself? I am a technical person (java developer) and I have done BB development in the past but haven't done any android type work.
I just don't want to go without my phone for 8 weeks if this is a simple software restoration exercise.
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=842495&highlight=brick
If you cannot execute the suggested method, post exact details of what you did, and have experienced, in that thread. Hopefully someone will be able to assist you. That should be the best place to start.
Good Luck!
From the thread posted above I think I'm screwed. This phone was stock, I've never bothered doing anything with it.
Vision PVT SHIP S-ON
HBOOT-0.05.0009
MICROP-0425
RADIO-26.06.02.25_M2
eMMC-boot
Dec 13, 2010,14:30:18
Since I've never rooted the phone or enabled usb debugging adb is just saying "error: device not found"
I would post this in that thread but it won't let me.
Is there anything I can do? I'll continue reading the rest of that thread.
I would call customer support and demand a supplementary phone or threaten to cut your service. If they won't hook you up with a rental during the time you're apart from your phone that THEIR update broke, then IMO, they're not worth your business.
Try q&a in the android development section. Make sure to provide all info.
bagadonitz said:
From the thread posted above I think I'm screwed. This phone was stock, I've never bothered doing anything with it.
Vision PVT SHIP S-ON
HBOOT-0.05.0009
MICROP-0425
RADIO-26.06.02.25_M2
eMMC-boot
Dec 13, 2010,14:30:18
Since I've never rooted the phone or enabled usb debugging adb is just saying "error: device not found"
I would post this in that thread but it won't let me.
Is there anything I can do? I'll continue reading the rest of that thread.
Click to expand...
Click to collapse
Sent from my Synergy Rom using XDA App
bagadonitz said:
I installed this update last night and it straight up bricked my phone. Starting with volume down and doing a hard factory reset leaves the phone hung on the white screen with HTC on it.
The phone is covered under warranty and I'll be getting a box shipped to me to send it in for repair. It is the 6-8 week turn around on the repair that troubles me.
The following briefly flashes on the screen when loading up that volume down / power screen:
SD Checking…
Loading…[PC10DIAG.zip]
No image!
Loading…[PC10DIAG.nbh]
No image or wrong image!
Loading…[PC10IMG.zip]
No image!
Loading…[PC10IMG.nbh]
No image or wrong image!
Knowing this, is there anywhere I can download these files and place them onto the SD card to see if I can't unbrick this thing myself? I am a technical person (java developer) and I have done BB development in the past but haven't done any android type work.
I just don't want to go without my phone for 8 weeks if this is a simple software restoration exercise.
Click to expand...
Click to collapse
There is a pc10img of the gingerbread update that may unbrick your phone as long as it wasn't on it already, because this one's build number is lower and your bootloader wouldn't accept it being s-on
Sent from my HTC Vision using XDA App
If possible, try contacting HTC's support and see if they can send you a PC10IMG.zip file you can put on your SD card.
HTC support just defacto sent me to Bell Technical support.
Bell Technical support is supplying me with a replacement smart phone while mine is in for this warranty "repair". I was just hoping to avoid the process entirely.
Admittedly I'm very green when it comes to all the lingo (rooted/unrooted, etc) so I'm afraid I'll make things worse by attempting to fix this myself unless I can find a specific solution to my problem.
Any of the threads that have been recommended won't let me post until I have 10 posts but I'll get there eventually.
Thanks.
PaganAng3l said:
There is a pc10img of the gingerbread update that may unbrick your phone as long as it wasn't on it already, because this one's build number is lower and your bootloader wouldn't accept it being s-on
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Where would I go about getting it? How would I get it onto the phone seeing that it is s-on and doesn't seem to get picked up by adb? What about the rest of the files it is complaining are missing or wrong image?
bagadonitz said:
Where would I go about getting it? How would I get it onto the phone seeing that it is s-on and doesn't seem to get picked up by adb? What about the rest of the files it is complaining are missing or wrong image?
Click to expand...
Click to collapse
it should flash a proper pc10img, just pull your sdcard, pop it in a pc and copy the pc10img to the root and pop it back in. someone with a little more knowledge would have to point you towards the right pc10img tho. not my expertise there..
Sent from my HTC Vision using XDA Premium App
You're stock on bell canada right? What version of android did you have before the brick?
Sent from my HTC Vision using XDA App
Honestly, I don't know. It was stock as I have never tried to replace it but I believe there was a previous update of 2.2 sometime between when I bought it and when this latest update came down on Friday.
probably was the 1.34 version then, i don't recall bell ever pushing the 1.82(?) version of 2.2. i don't recall the exact version of 1.34 though =(
I'm having trouble finding a full bell canada ruu, I know I'm just not looking in the right place. Everything you've described can be fixed by reflashing the software.... if only you had s-off and supercid this would be a cakewalk
Sent from my HTC Vision using XDA App
Thanks for the effort. I'm such a newb that I'm really not much help.
Rots me that this happened. I've never messed with the phone so far as I'm concerned the update they pushed out should have worked flawlessly as it appears to have for many many other people.
I had to have my phone in for service to get the screen replaced back in December (that was my own fault). I wonder if they had to do anything with the software at that time that made it incompatible with this latest update.
PaganAng3l said:
I'm having trouble finding a full bell canada ruu, I know I'm just not looking in the right place. Everything you've described can be fixed by reflashing the software.... if only you had s-off and supercid this would be a cakewalk
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Bell pushed out a Froyo update on March 30. Here is the thread: http://forum.xda-developers.com/showthread.php?t=1145163&highlight=bell
Could this be the solution?
David Dee said:
Bell pushed out a Froyo update on March 30. Here is the thread: http://forum.xda-developers.com/showthread.php?t=1145163&highlight=bell
Could this be the solution?
Click to expand...
Click to collapse
I purchased my DZ the day it was launched by bell and it had 666.5 so I am assuming that is the version Bagadonitz has.
I got the phone a couple days after the bell launch and I've installed everything that came down since.
I'm real nervous about trying anything here unless I can get specific instructions. I'm a technical person but haven't done anything with phones before and I'm a little reluctant to jump in on my own
bagadonitz said:
I got the phone a couple days after the bell launch and I've installed everything that came down since.
I'm real nervous about trying anything here unless I can get specific instructions. I'm a technical person but haven't done anything with phones before and I'm a little reluctant to jump in on my own
Click to expand...
Click to collapse
It should be quite simple: Place the OTA on your SD card and launch it through the phone's bootloader. You enter bootloader by shutting down the phone, holding the volume down and power button at the same time. If you have "fast boot" enabled, then you have to do a battery pull and then turn on with the volume down.
I would wait for PaganAng3l to confirm that the OTA (that is associated with the thread I posted above) would work with s on and a non-rooted phone.
About "bootloader", here is an excerpt from gtrab's DZ easy rooting guide, located here http://forum.xda-developers.com/showthread.php?t=835777:
1.- What is "Bootloader" ??
The Bootloader is a firmware management tool included on every stock ROM, it lets you reset to factory default, use "Fastboot" to flash official images, or launch the Recovery utility.
From the Bootloader you can also check your S-ON or S-OFF state, your firmware and Radio version, etc.
You don't need root or S-OFF to enter the Bootloader because every HTC phone has it.
2.- How do I enter the Bootloader ??
Power off your phone, then, hold the volume down key and the power key.
(You need to disable "Fast boot" from Settings -> Applications, or remove the battery to really power off the Desire Z. Otherwise, power off will just hybernate the phone, and when restarting you will not be able to enter the Bootloader).
To exit Bootloader you have to remove the battery.
Hi all, had a search but nothing seems like my case, I'm writing because I think I've seriously bricked the phone.
Rom:LeeDrOiD HD V3.3.3-Port-R5
S-Off
Stock Hboot
Flashed a new radio, rebooted and nothing showed up for a long time, tried (stupid idea i know) to remove the battery then BAM! Phone dead, any button combination won't work, so no I don't have fastboot, and it doesen't even light up the led if connected it to the wall charger, also the pc doesen't see it.
It's better to bring it to HTC ? Could it be fixed by them ?
Many thanks
Regards
Emilio
I'll try to remove the battery for some hours, and also will try with another battery
Any suggestions?
I think you know the answer to this.. Never take out the battery when flashing radios, the radio gets properly flashed upon first boot. If its corrupted, its bricked. Did you check md5? Can you? Can you get into bootloader? Or connect fast boot? if you can't get into fast boot, its back to htc. How did you flash? Recovery? pb99img our fast boot is the best.
When you flash a new radio, the hardware gets updated. If there something goes wrong, you desire is completely hard-bricked (and so nothing more than an expensive paperweight). And I am pretty sure, even HTC cannot fix a radio damage. Even if they can, they won't do it because you lost your warranty.
MatDrOiD said:
When you flash a new radio, the hardware gets updated. If there something goes wrong, you desire is completely hard-bricked (and so nothing more than an expensive paperweight). And I am pretty sure, even HTC cannot fix a radio damage. Even if they can, they won't do it because you lost your warranty.
Click to expand...
Click to collapse
Well..im not completely sure..if u are still in warranty period, you can try say they that you was applying an ota (for example one about the froyo update) and it failed..the ota also contain radio updates sometimes..and as the phone is bricked they can't know if he is s-off etc..
andQlimax said:
Well..im not completely sure..if u are still in warranty period, you can try say they that you was applying an ota (for example one about the froyo update) and it failed..the ota also contain radio updates sometimes..and as the phone is bricked they can't know if he is s-off etc..
Click to expand...
Click to collapse
good plan, id go with this.
Hey people
I recently got a HTC Desire from ebay, and there was no rom on it - it was just stuck at the splash screen. The bootloader was working, so I just thought a reflash would do the trick. I therefore downloaded a few RUU's and was trying them out only to find that none of them worked, not even the 2.3 update. After some frantic googling, I discovered that the phone was branded to vodafone, so I tried to RUU that one, and now my phone is stuck at the black HTC logo with the four exclamation marks at the edges. I can't S-OFF or even make a goldcard, since I don't actually have a ROM on the phone. What have I done? I might of corrupted the radio by the sounds of it, but I'm really hoping I haven't.My phone won't go into the bootloader anymore, and I don't know what to do. Could someone help me?
Go read bortaks guide, first post in Desire Q&A (stickies) and go down to number [4]
Sent from my HTC Desire
I have tried that. I have not been able to make a goldcard - none of the sdcards I have are working. I did try searching and reading around before I posted
Have u got another phone, r can u borrow 1? u can put ur sdcard in that to make a gold card
Sent from my HTC Desire
I have tried to make a goldcard using my xperia x8, but the two cards I have aren't being recognised after using the hex editor. It keeps saying they are not formatted.
Then first look for an usb unbrick guide, it should be easy.
Or -
send the phone back. You are supposed to get a phone in working condition, not some overpriced paperweight. Unless you deliberately bought the phone in such condition which is imho extremely foolish. To sell a phone in non working condition is outrageous! I hope you haven't left positive feedback.
erklat said:
not some overpriced paperweight.
Click to expand...
Click to collapse
Lol
Sent from my HTC Desire
The thing is, I think it's my own fault. When I got the phone, at least it went into the bootloader when you held the down volume button and pressed power on, but now it won't even do that. It's stuck at the black screen with the four exclamation marks at the corners. Is there anything I can do in fastboot, since that is what it's stuck it? The USB unbrick guide doesn't help because I can't get past fastboot mode...
Can anyone help?
Hi all,
I have a big problem
I think that my HTC Wildfire got hardbricked, My friend was trying to install custom rom but it went wrong
My wildfire doesnt turn on and my battery is working I tried my battery with a other wildfire so its not the battery..
Is there a way to unbrick my wildfire ??
Wildfire64 said:
Hi all,
I have a big problem
I think that my HTC Wildfire got hardbricked, My friend was trying to install custom rom but it went wrong
My wildfire doesnt turn on and my battery is working I tried my battery with a other wildfire so its not the battery..
Is there a way to unbrick my wildfire ??
Click to expand...
Click to collapse
OK let's figure this out. Gonna need specific information from you.
Is the phone s-on or s-off? If s-off how was this done?
What procedure was used to flash the ROM?
What state is the phone in now? Won't turn on at all, or sits on the HTC screen, or only vibrates?
And has your friend done this before?
Sent from my HTC Desire S using Tapatalk
heavy_metal_man said:
OK let's figure this out. Gonna need specific information from you.
Is the phone s-on or s-off? If s-off how was this done?
What procedure was used to flash the ROM?
What state is the phone in now? Won't turn on at all, or sits on the HTC screen, or only vibrates?
And has your friend done this before?
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
I think the phone was s-on
the phone doesnt turn on , no vibrate , no led by charging just nothing..
my friend has flashed many roms but this time it went wrong and he tryed to fix it but i think he hardbricked it now..
Wildfire64 said:
I think the phone was s-on
the phone doesnt turn on , no vibrate , no led by charging just nothing..
my friend has flashed many roms but this time it went wrong and he tryed to fix it but i think he hardbricked it now..
Click to expand...
Click to collapse
Hmmmm. If it was s-on then HTC safeguards would have prevented a hard brick. Is it possible the hardware has been damaged?
Sent from my HTC Desire S using Tapatalk
Try hard reset through youtube
Sent from my GT-S5570 using xda app-developers app
My advice is to flash an RUU and revert back to stock.
This is only because it's hard bricked, plus it happened to me before. I thought to give it a go, and it worked.
After that I just re root my phone, and install CWM recovery, and then flash a new ROM. It's simple
Just follow my leads and it'll work.
P.S Your hardware hasn't damaged at all. Why do users say these things?
1. Download an RUU from the buzz forums
2. Install and revert back to stock with RUU
3. After the process is done, enable adb in settings [Applications]
4. re root your device, and install CWM
5. Flash any custom ROM and follow the instructions 'fully'.
I had to rush this, I hope you understand what i'm saying.
Users if you think i'm wrong then correct me as you wish.
But this all managed to work for me, when my device was hard bricked xD
Stone. Cold said:
My advice is to flash an RUU and revert back to stock.
This is only because it's hard bricked, plus it happened to me before. I thought to give it a go, and it worked.
After that I just re root my phone, and install CWM recovery, and then flash a new ROM. It's simple
Just follow my leads and it'll work.
P.S Your hardware hasn't damaged at all. Why do users say these things?
1. Download an RUU from the buzz forums
2. Install and revert back to stock with RUU
3. After the process is done, enable adb in settings [Applications]
4. re root your device, and install CWM
5. Flash any custom ROM and follow the instructions 'fully'.
I had to rush this, I hope you understand what i'm saying.
Users if you think i'm wrong then correct me as you wish.
But this all managed to work for me, when my device was hard bricked xD
Click to expand...
Click to collapse
Hey @Stone Cold, the confusion people are having here is between hard bricked and soft bricked. A "hard brick" can only occur in 2 situations which are
1: the bootloader is corrupted/damaged/deleted and the device cannot boot. This can Only be fixed by using a JTAG. A ruu will not work as the ruu is flashed by the hboot(bootloader) and if it won't function then its dead.
2: that hardware has been damaged so much that the device cannot physically boot.
Depending on the damage this can sometimes be fixed.
All other forms of "bricking" are "soft bricks" or software bricks. These include bootlooping, trapped at the splash screen etc. These can be fixed as the bootloader and or custom recovery still function. If either of these still function you are not hard bricked. If a ruu worked then you were soft bricked.
Now this user states that his device was s-on so bootloader corruption is massively unlikely as nand protection is still active. This coupled with the owner stating that the device will not boot and shows no signs of life a hardware failure is the most likely option.
Sent from my HTC Desire S using Tapatalk
heavy_metal_man said:
Hey @Stone Cold, the confusion people are having here is between hard bricked and soft bricked. A "hard brick" can only occur in 2 situations which are
1: the bootloader is corrupted/damaged/deleted and the device cannot boot. This can Only be fixed by using a JTAG. A ruu will not work as the ruu is flashed by the hboot(bootloader) and if it won't function then its dead.
2: that hardware has been damaged so much that the device cannot physically boot.
Depending on the damage this can sometimes be fixed.
All other forms of "bricking" are "soft bricks" or software bricks. These include bootlooping, trapped at the splash screen etc. These can be fixed as the bootloader and or custom recovery still function. If either of these still function you are not hard bricked. If a ruu worked then you were soft bricked.
Now this user states that his device was s-on so bootloader corruption is massively unlikely as nand protection is still active. This coupled with the owner stating that the device will not boot and shows no signs of life a hardware failure is the most likely option.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Oh, so I was wrong.
Thought it was that way though, anyway thanks. This makes more sense now
Cheers
Stone. Cold said:
Oh, so I was wrong.
Thought it was that way though, anyway thanks. This makes more sense now
Cheers
Click to expand...
Click to collapse
That's no problem pal it's good to keep these terms clear, so many people have misinterpreted them in the past. That being said thank you for reminding me of the black screen hboot issue. It's been ages since I've heard of that happening. Its good to keep notes
But back on topic, OP do you or your friend have a working fastboot path? If so try to boot into hboot with volume down and power, wait 30 seconds then push power. Then on the PC issue the command
Fastboot devices
If nothing happens its toast :/
Sent from my HTC Desire S using Tapatalk