I am not sure this is the place to post this but I certainly hope so.
I have researched the matter a little before posting.
I got my Desire from a friend. He has been using it for over a year.
Seems he didn't modify anything and it still has the original system but am not sure. If someone can tell me where to find this info...
If I leave the phone on without using it it stays on but if I use it, like browsing or gps or any other program, even just downloading stuff from MArket, the phone restarts after 15 minutes and if I don't take out the battery for a few minutes it loops restarts.
Once the battery is removed for a few minutes the phone restarts normally.
from what I read it may be a problem with the board heating?
Is there a way to test that? to diagnose a phone?
Thanks for any help
Hey mate,
If you're running on a stock rom there's something wrong with the hardware. Unless you've got all the spare parts you can fix the phone yourself, otherwise it has to be repaired. Soz
How do I know if it is a stock Rom
ymkx said:
How do I know if it is a stock Rom
Click to expand...
Click to collapse
-___- How do you not know if you've rooted the phone and flashed custom software?
You should ask your friend if he has bought the phone from a store or if he has rooted it before. Otherwise you have to hand it in to the repair centre
ymkx said:
How do I know if it is a stock Rom
Click to expand...
Click to collapse
Generally you can tell by going to settings/about phone and looking at the software number and kernel version. If you see any strange names in these areas, like Nova-lite, Grim Reaper ver 1, etc, it is generally a modified rom.
Also, you can look in your apps for an app called Superuser. This is a sign of a rooted phone.
Additionally, if you power down the device, you should be able to boot into Recovery (if it is installed), by holding Vol- and Pwr. If you get into the boot, and select the "recovery" option, and you get a display with options like Install zip from SD, Wipes, Formats, etc, then this is a custom recovery.
My guess, would be, if the device is stock, Run an RUU Rom, and see if it will install a fresh OS. This may fix your issue. Corruption in the OS can definately cause the issue you describe.
The best sign should actually be to boot into bootloader (power off - HOLD volume down + power until white screen pops up) In the left upper corner it should say like:
"BRAVO PVT1 SHIP S-ON". If it says "S-OFF" your phone has probably been rooted before
chippey5 said:
The best sign should actually be to boot into bootloader (power off - HOLD volume down + power until white screen pops up) In the left upper corner it should say like:
"BRAVO PVT1 SHIP S-ON". If it says "S-OFF" your phone has probably been rooted before
Click to expand...
Click to collapse
I'd bet money that most Rooted Bravo's are still S-On...not reliable.
OP, do you have the "Super User" or "SU" app installed? If yes your phone is rooted and likely running a custom ROM.
Sent from my GT-I9100 using xda premium
rete said:
I'd bet money that most Rooted Bravo's are still S-On...not reliable.
OP, do you have the "Super User" or "SU" app installed? If yes your phone is rooted and likely running a custom ROM.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
True true, back to S-ON is possible. If the phone has been rooted or not before can be hard. Anyone can tidy up a phone but I suggest he roots his phone, flashes gingerbread RUU and then try again. One moment, I'm going to find a link for you m8
Sent from my HTC Desire
rete said:
I'd bet money that most Rooted Bravo's are still S-On...not reliable.
OP, do you have the "Super User" or "SU" app installed? If yes your phone is rooted and likely running a custom ROM.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Also, don't throw your money away, alpharev are one of the first bravo HBOOT flashers. This is taken from their site: [/QUOTE] HTC implemented security on their newer generation phones. This flag, called @secuflag, controls whether your phone has it's NAND or flash unlocked. Most noticeably, S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, secuflag controls whether zip files being flashed through recovery or fastboot, are signed by HTC.
The now notorious S-OFF (security off) will disable this NAND security. Since we are unable to access the Radio NVRAM itself (where secuflag is stored), we turned our attention to HBOOT.
AlphaRev has patched HBOOT images for several phones, whereas the HTC Desire (GSM) was our first victim. [/QUOTE]
I recommend he flashes through HTC themselves
Sent from my HTC Desire using xda premium
ymkx said:
I am not sure this is the place to post this but I certainly hope so.
I have researched the matter a little before posting.
I got my Desire from a friend. He has been using it for over a year.
Seems he didn't modify anything and it still has the original system but am not sure. If someone can tell me where to find this info...
If I leave the phone on without using it it stays on but if I use it, like browsing or gps or any other program, even just downloading stuff from MArket, the phone restarts after 15 minutes and if I don't take out the battery for a few minutes it loops restarts.
Once the battery is removed for a few minutes the phone restarts normally.
from what I read it may be a problem with the board heating?
Is there a way to test that? to diagnose a phone?
Thanks for any help
Click to expand...
Click to collapse
Go to settings -> about phone and tell me what android version you have ( 2.1 / 2.2 / 2.3 ). I will give you a link as soon as the HTC developer site is back online. The tool I will get for you will flash your phone with Gingerbread (2.3) legit
Sent from my HTC Desire
chippey5 said:
I recommend he flashes through HTC themselves
Click to expand...
Click to collapse
NEVER do that, or you'll have to downgrade later.
I had similar problems with my stock desire, update fixed it. So it might not be hardware related. Try rooting and using a custom rom and see if it persists. If so, it ist hardware related and you'll have to send it in (unroot before), if not, it's software and you can just keep your custom rom.
And, before you ask, there are ca. 100 threads on what the best rom might be. Just try any one from the Desire Index (sticky in dev section).
As you said, it might not be hardware related but what does it matter? If the official update doesnt help and he has to root it, it won't matter since he's able to flash stock roms then...
Sent from my HTC Desire
He will certainly not brick it with the official update and it's a lot easier to skip the rooting part if you're not common with it
Sent from my HTC Desire
If you want to flash the official gingerbread rom from HTC click here: http://www.htcdev.com/process/legal_download/152 . This will surely NOT brick your phone. It's the latest official for desire too.
Sure it's not a particular app that's causing it? Also, perhaps underclock the CPU and see if that improves stability. If it's anything like desktop processors, they can degrade over time and cause instability (usually more noticable when the CPU is heavily overclocked, but it still happens regardless)
Ah well,i thought you meant unlocking the bootloader through the htc tool. For that is definitely not recommended. RUU should be no problem.
Btw, there is a reason for an edit function.
Gesendet von meinem HTC Desire
muellersmattes said:
Ah well,i thought you meant unlocking the bootloader through the htc tool. For that is definitely not recommended. RUU should be no problem.
Btw, there is a reason for an edit function.
Gesendet von meinem HTC Desire
Click to expand...
Click to collapse
I agree with you about that. I would use unrevoked in that case
Related
Hello,
i flashed my hboot back from ogxygen to default hboot, after
reboot i just saw a black screen. The leds are blinking green and orange if i put out the battery and if i insert it, the leds are orange.
If i start the desire the leds are not showing something and its still blackscreen.How i can repair it? =(
sry for bad english
i'm no expert but have you tried going in to the Bootload menu (power off phone, hold down the back button and power on holding both button down unlit phone starts up)?
Then if you can get in to the Bootloader screen you can then try to go to Recovery option or flash from your PC using ADB.
Have you made a NAND back up before you flashed your Hboot?
Yes i already did, but always blackscreen not vibrating or something like that
no i dont have a nand backup, why i need 1? someone could give me a link?
or make a backup and upload it?
if you connect phone to pc , is it recognized by PC?
if yes try to run an official RUU from shipped roms.
alekshuso said:
Yes i already did, but always blackscreen not vibrating or something like that
no i dont have a nand backup, why i need 1? someone could give me a link?
or make a backup and upload it?
Click to expand...
Click to collapse
no my pc isnt showing something up
It is a bit late but check the md5 of the hboot you flashed, if it does not match I think you are pretty screwed otherwise it probably is still fixable.
how i can fix? damned thats my dads desire he will kill me :/
i don't think you can, you have to take it back for repair.
or you can find someone with jtagbox.http://www.jtagbox.com/jtag-news/riff-jtag-htc-desire-unlock-unbrick-imei-repair-supported/
will they repair my desire if i send it back? cause its flashed
It depends on how much they can see from it.
Sent from my LeeDroided Desire HD
ähm... what they will do after repair when they see thats my desire is flashed?
If they find out that it was a rooted desire or that you caused the fault, they are happy to repair it but they will charge you big time. Somewhere around here someone named 200 euro i think. But you might get lucky and they repair it cost free, has also happened before.
What you have is the slcd desire brick. Follow the thread in my signature with the ruu for your region- how to unroot the desire.
Sent from my HTC Desire using XDA App
no, it dont make vibration... or its cause i had gingerbread rom
alekshuso said:
no, it dont make vibration... or its cause i had gingerbread rom
Click to expand...
Click to collapse
push
read my post ... : HTC Desire doesn't start up. maybe it helps. had the same exact problem.
spd00 said:
read my post ... : HTC Desire doesn't start up. maybe it helps. had the same exact problem.
Click to expand...
Click to collapse
nope, my pc dont show something up about usb but my desire is
charging :/ and it dont vibrate!!!
It should in fastboot. See my signature for the thread on unbricking
Sent from my HTC Desire using Tapatalk
nope your thread is for slcd bricked desire, but my one is hboot bricked :/
push, what i must write to htc and can i use jtagsoftware without box`?
and how i can root my radio`?
Hi folks,
i´ve a problem with a Desire Z from a friend.
Every time when the phone boots, it stops at the HTC Logo.
I think it´s bricked
Is there any possible to flash the Rom (like Odin on Samsung Android Phones)
Thanks
If you power the phone off, then holding down the volume button, press the power button. Does the Hboot screen come up?
Also, you don't give a heck of a lot of info. Is the phone rooted, and/or S-Off? If not, then no, you can't flash a custom ROM.
But you may be able to flash the official ROM from Hboot.
the H Boot screen is this with "bootloader, reboot" and something with the 3 androids ?
when its that, i come into the hboot screen .. i did try the "factory reset" but it hangs on the 3 androids at the middle of the screen
EDIT: The Phone is not rooted, S-on stands there
but how can i flash a official ROM ?
i found one, but it recognize the phone
Since you are not rooted and S-On, you need to use the official ROM that matches your carrier ID (CID).
What ROM did you try?
If you want help, you need to supply as much information as possible. Not just "I tried a ROM".
Seeing as the phone is unrooted, it's unlikely that it's bricked from a user error.
At a guess, it's a Hardware issue, there's a thread here about it.
I had this same issue with my phone, it started freezing completely, and I had to do a battery pull to restart and it would just hang at the htc logo.
Seeing as you don't have clockwork mod though, you won't be able to see the Cache mounting errors, though you should be able to run the adb commands to find the name of your eMMC card if you have adb installed.
-Nipqer
redpoint73 said:
Since you are not rooted and S-On, you need to use the official ROM that matches your carrier ID (CID).
What ROM did you try?
If you want help, you need to supply as much information as possible. Not just "I tried a ROM".
Click to expand...
Click to collapse
okay, it´s a free phone without branding.
where can i read the CID !?
Nipqer said:
Seeing as the phone is unrooted, it's unlikely that it's bricked from a user error.
At a guess, it's a Hardware issue, there's a thread here about it.
I had this same issue with my phone, it started freezing completely, and I had to do a battery pull to restart and it would just hang at the htc logo.
Seeing as you don't have clockwork mod though, you won't be able to see the Cache mounting errors, though you should be able to run the adb commands to find the name of your eMMC card if you have adb installed.
-Nipqer
Click to expand...
Click to collapse
Where can i get adb mode ? the hboot or at the HTC LOGO !?
I have this problem too but i rooted and s-offed. What should i do now. Same things as him.
Nipqer said:
At a guess, it's a Hardware issue, there's a thread here about it.
Click to expand...
Click to collapse
Its possible, but also highly speculative. Damage to the ROM, or the ROM missing may also cause the same issue (stuck on boot splash).
bboy2000 said:
I have this problem too but i rooted and s-offed. What should i do now. Same things as him.
Click to expand...
Click to collapse
You're in (possibly) better shape then the OP. Try flashing any known good ROM from Hboot/recovery. Preferably a rooted ROM, if you want to stay rooted.
But its possible you may have something more going on than a bad ROM file, like mentioned in post #5 above.
i couldn´t find a tutorial how to flash the desire Z im H-Boot mode ?
can u give me a tutorial !?
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.
Hello fellow hox xda people... I am very stuck in this situation, gutted because I love my hox.
It started when I lost my phone signal for a few hours.. stupidly in a panic I tried to flash stock recovery to try and fix it.. then I noticed my imei and baseband showing as "unknown".. I have relocked and run the ruu but the problem still remains.. I fear u have somehow corrupted the radio partition...
It isn't the sim because that works in another phone, I have tried another sim but still no signal.
I sent it to HTC to repair under warranty but because it had been relocked the won't touch it without me paying £150 to replace main board..
Does anyone have any ideas or thoughts?
I am waiting for the next official update to come and see if writing the new radio will fix it...
Sent from my HTC One X using xda app-developers app
Seems like you've screwed your IMEI. This happened to me on the SGS2 where my EFS got corrupted luckily I had saved my EFS and managed to flash it back.
Not sure if this method also applies to HTC products, or it could be your phone has a hardware fault. If they are trying to charge you then nothing you can do I'm afraid then just cough up especially if it is a corrupted EFS.
Edit : EFS only applies to the Samsung phones, seems like your radio is screwed, if you still have your phone there is a radio thread on the development section, flash a radio again and it might just restore it back.
Sent from my HTC One X using Tapatalk 2
Thank-you for your reply... I did notice similar problems with gs2 when doing research on Google. I have looked at the radio which leads me to think I may be up the proverbial creak... I did try flashing the new leaked radio but with no luck... I do have quite a bit of blind faith in the up coming official update... is there a way of formatting the radio partition and the ruu re-writing it?
Sent from my HTC Wildfire using xda app-developers app
stout0_0 said:
Thank-you for your reply... I did notice similar problems with gs2 when doing research on Google. I have looked at the radio which leads me to think I may be up the proverbial creak... I did try flashing the new leaked radio but with no luck... I do have quite a bit of blind faith in the up coming official update... is there a way of formatting the radio partition and the ruu re-writing it?
Sent from my HTC Wildfire using xda app-developers app
Click to expand...
Click to collapse
We can't really do anything in regards to that as we have no S-OFF. Where we can flash radios and rils. Still clueless how it would have damaged it as we don't have S-OFF.
Sent from my HTC One X using Tapatalk 2
It does seem to be a bit of a mystery!... the imei is still there when I check the barcode in hboot screen... does that indicate anything do u think?
Sent from my HTC Wildfire using xda app-developers app
stout0_0 said:
It does seem to be a bit of a mystery!... the imei is still there when I check the barcode in hboot screen... does that indicate anything do u think?
Sent from my HTC Wildfire using xda app-developers app
Click to expand...
Click to collapse
Just relock your bootloader, flash with an RUU (branded or unbranded) and everything should be fine. This kind of thing happens once in a while. It happened with my S II and Sensation back in the day
Hi, and thank-you for your response. I have tried that numerous time but still have the same problem, I have flashed the leaked radio too on various roms to no avail..
Sent from my HTC Wildfire using xda app-developers app
stout0_0 said:
Hi, and thank-you for your response. I have tried that numerous time but still have the same problem, I have flashed the leaked radio too on various roms to no avail..
Sent from my HTC Wildfire using xda app-developers app
Click to expand...
Click to collapse
That's very odd. That's what I've always done when my IMEI or baseband goes missing. Flashing the official OEM ROM usually writes the ROM, kernel and the baseband if I'm not mistaken. Kinda like when you flash a OEM firmware to the iPhone. It writes over everything hence why you have to use a custom ROM that doesn't update the baseband if you want to preserve your SIM unlock.
I installed Android Revolution HD 7.2.1 the other day (nice ROM by the way). Decided I wanted the benfits of Francos r12 kernel. Flashed it and then had no GSM signal. Baseband and IMEI were both unknown. Thought to myself "f*^k here we go again".
Downloaded this. Went back into the bootloader. Relocked it via adb. Then whilst still in the bootloader, I clicked on the RUU that I downloaded from here.
Once everything booted back up, had GSM, IMEI and baseband back. Proceeded to unlock the bootloader and flash ARDH 7.2.1 again but left out Francos kernel for the time being lol.
More for the legal heads etc. here, but HTC-Dev's website states:
Why is my security still on (S-On) after I have unlocked my bootloader?
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. You can easily see that you have successfully unlocked the bootloader by looking at the top of the screen when entering the bootloader screen. Security is left on to protect things like the radio, and SIM lock.
If you should require support, please feel free to contact us via the support section of our website, http://www.htc.com
Click to expand...
Click to collapse
It specifically says security is left on to protect the radio etc. - surely this should then be covered by HTC as, according to them, there's no way we could break it. The way I see it, either their 'security' didn't work, or the problem isn't caused by a bootloader unlock?
Hahaha! I couldn't help it. I just had to flash Francos r12 kernel again and what do you know? No IMEI and baseband. All good though. Restored from a nand backup I did earlier this evening and all is well again. Downloaded the kernel again just to make sure the md5 wasn't bung, flashed and same thing happened again. So when you get your HOX working again, don't flash Francos r12 kernel lol.
Eambo said:
More for the legal heads etc. here, but HTC-Dev's website states:
It specifically says security is left on to protect the radio etc. - surely this should then be covered by HTC as, according to them, there's no way we could break it. The way I see it, either their 'security' didn't work, or the problem isn't caused by a bootloader unlock?
Click to expand...
Click to collapse
That applies to every device apart from, maybe, Tegra3. The radio might be accessible.
have the same insuee... yesterday i pick my phone and it has no signal...i think no problem reboot the phone...and no changes.. after i see that imei is unknown and baseband too... the phone with or without sim when i open sim slot says that has a problem to see the sim.. root relock flash stock and other roms is not helped -.-
sorry for my english guys.. but seriosly i tryed a lot of things nothing to do -.-
now i'm downloading an old RUU for flash it to change the radio...
If I'm not mistaken you can't roll back the radio using an old ruu.. I think I tried but it failed. I have also flashed the latest ota update but that didn't work either.. beginning to think its hardware as the weekend before it first happen it was dropped onto its screen from chair height with no immediate problems or damage... really struggling with this..
Sent from my HTC Wildfire using xda app-developers app
stout0_0 said:
If I'm not mistaken you can't roll back the radio using an old ruu.. I think I tried but it failed. I have also flashed the latest ota update but that didn't work either.. beginning to think its hardware as the weekend before it first happen it was dropped onto its screen from chair height with no immediate problems or damage... really struggling with this..
Sent from my HTC Wildfire using xda app-developers app
Click to expand...
Click to collapse
No way...no changes...but my HTC are never dropped down..I have no idea why it's doesn't work..some one can help us?
AlexVendettA said:
No way...no changes...but my HTC are never dropped down..I have no idea why it's doesn't work..some one can help us?
Click to expand...
Click to collapse
Check out GetRIL app free in playstore. Bu also see xmoo's radio collection thread under and. dev. section. There are instructions
Sent from my HTC One X using xda premium
eyosen said:
Check out GetRIL app free in playstore. Bu also see xmoo's radio collection thread under and. dev. section. There are instructions
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
thank you.. but..it's the same -.-'' i think i'll pay htc for repair..
p.s. think that it's hard problems..
i'm just trying to... open an old ruu take the boot_signed.img from rom.zip(windows/temp) and flash it in fastboot then i relock my device and flash ruu.. hope that it will work
Fingers crossed bud!.....
Sent from my HTC Wildfire using xda app-developers app
Not trying to start a flame war or anything, but this is why I stopped buying HTC phones and went with the S3. Because ever since they started with this HTCDev garbage, modding your phone became ridiculously difficult.
no way need s-off to downgrade hboot... s-off is not possible for now.. w/o javacard......i don't have idea what to do.. then f-.ck all.. drop my hand down and monday send my phone to htc and cross the fingers for free repair...
p.s. i think..to go to an phone store and say that i wanna see an one x white/grey and change it accendentely.. (stupid and illegal but can work )
edit: it's hardware fault i think..
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