Related
Hello
Today I woke up at 02:00am first - My phone started vibrating all over the time, from hard to low. (hard vibrate, low vibrate, medium, short pause, low vibrate...) So my phone acted really strange. I just pull out the battery because it didn't react to any button and continued with sleeping.
Today I tried to start it. I've heard a short vibrate, and that was it. I even can't see any charging light when I plug my cellphone in. But then I connected my phone to my computer, and tada, adb works. So i've installed a VNC app over adb and then I've connected to my phone, and I've seen that Sense and everything works. So the handy itself is still working, but the screen is just black and all the touch buttons don't react. Also the charging light is "dead". What happened? It didn't fell or something like that.
Also my phone is rooted, with custom recovery and custom ROM. I've got still garantuee - So what should I do now?
Greetings
PMTheQuick
Hmm...it doesnt look good.
Did you have your CPU overclocked?
EDIT: It seems like the LCD screen and the digitizer have broke. Unless you want to try to replace them yourself which is possible but very fiddly, you may have to send it back. First though lets see what others say.
raze599 said:
Hmm...it doesnt look good.
Did you have your CPU overclocked?
EDIT: It seems like the LCD screen and the digitizer have broke. Unless you want to try to replace them yourself which is possible but very fiddly, you may have to send it back. First though lets see what others say.
Click to expand...
Click to collapse
No, it was always at 998Mhz, which is the standard clockrate. I'm not a fan of overclocking - I really loved this smartphone and I didn't risk things like overclocking
I also thought about sending it back, but the question is what should I do before sending it back? And how? (Deflashing, S-ON...?)
Greetings
PMTheQuick
Sending it back in its current state may be a problem because your mods will have voided the warranty.
A possible solution is to use the s-off tool to revert back to s-on and standard cid . Then using adb, push pd98img.zip onto the sdcard. Then "adb reboot bootloader" and I believe it will flash the stock rom (pd98img) automatically.
Then you'll be unrooted and free .
HOWEVER DON'T TAKE THIS AT FACE VALUE, WAIT FOR OTHERS TO CONFIRM FIRST .
Sent from my Desire HD using XDA App
a33a said:
A possible solution is to use the s-off tool to revert back to s-on and standard cid . Then using adb, push pd198.zip onto the sdcard. Then "adb reboot bootloader" and I believe it will flash the stock rom (pd198) automatically.
Then you'll be unrooted and free .
HOWEVER DON'T TAKE THIS AT FACE VALUE, WAIT FOR OTHERS TO CONFIRM FIRST .
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Really good idea so far. The only problem is, the pd198.zip would be read and after that you must press a few keystrokes. Power off/on and the volume keys are still working, so that isn't a problem. I just need a friendly guy who can tell me when I must press which key
Greetings
PMTheQuick
You can try to flash an original RUU. As far as i know there is no need to press a button on the phone.
You said adb works?
Try:
Adb reboot bootloader. Then wait a bit.
Run an official RUU and follow the steps. You should be good to go then.
But there is one thing: do you had radio s-off and super cid before? If so, you should run jkoljos radio tool and revert to stock cid and s-off again.
Then reboot to bootloader and continue with the steps i mentioned above
Sent from my HTC Desire HD using Tapatalk
Flussen said:
You can try to flash an original RUU. As far as i know there is no need to press a button on the phone.
You said adb works?
Try:
Adb reboot bootloader. Then wait a bit.
Run an official RUU and follow the steps. You should be good to go then.
But there is one thing: do you had radio s-off and super cid before? If so, you should run jkoljos radio tool and revert to stock cid and s-off again.
Then reboot to bootloader and continue with the steps i mentioned above
Sent from my HTC Desire HD using Tapatalk
Click to expand...
Click to collapse
Does a RUU replace my custom recovery (ClockWorkMod) with the original HTC one? And is the RUU with the .exe right for that time? Or must I have an PD98.img? Which one should I take, I bought it unbranded: http://www.iloveabath.co.uk/index.php?dir=RUUs/
Greetings
PMTheQuick
Yes, recovery should be replaced.
I'd say take the 1.32.405.6 wwe. This is the last rootable OTA and your DHD probably came with it.
Sent from my HTC Desire HD using Tapatalk
Flussen said:
Yes, recovery should be replaced.
I'd say take the 1.32.405.6 wwe. This is the last rootable OTA and your DHD probably came with it.
Sent from my HTC Desire HD using Tapatalk
Click to expand...
Click to collapse
The radio S-OFF tool didn't work. Always unknown error - And i've found the reason, before I can S-ON it, I have to do this:
"Flash stock ROM (RUU, not over 1.7)"
And that will be... amazingly hard. I've got all these mods:
SuperCID
Radio S-OFF
Engineering S-OFF
Custom Recovery
Custom ROM
My actual idea, it would be great if someone can confirm me it is in the right order:
Changing CID & Radio S-ON
Thats my big problem! It doesn't work with my actual ROM. I need to downgrade - But how? Clockwork Mod has annoying "Are you sure" selections like: "Flash? No, No, No, Yes, No, No" - Impossible to find that out without a display. And I can't flash any ROM, because I need adb checked by default - Otherwise I won't have access again to shell, and without shell I can't start my VNC Server, and without all that I can't do anything more and must send it like that to the garantuee. I've found an http://forum.xda-developers.com/showthread.php?t=939982 Raidroid ROM, with standard ADB if I understand that right. But how should I flash it?
Restoring H-Boot and Recovery
Code:
adb shell
su (if you get permission denied, you have to do Visionary temproot)
getprop ro.cid (this will tell you your stock CID, we will use that later, so write it down. It has eight digits.)
busybox dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21 (it will replace clockworkmod with original recovery)
busybox dd if=/sdcard/hboot_original.bin of=/dev/block/mmcblk0p18 (ONLY if you had ENG S-OFF, it will give you back SHIP bootloader)
sync (wait 10 secs after that, then you can close the adb shell window)
Flashing RUU
Everything should be away now... After all that everything should be allright and I can give my phone to guarantee.
Greetings
PMTheQuick
PMTheQuick said:
The radio S-OFF tool didn't work. Always unknown error - And i've found the reason, before I can S-ON it, I have to do this:
"Flash stock ROM (RUU, not over 1.7)"
And that will be... amazingly hard. I've got all these mods:
SuperCID
Radio S-OFF
Engineering S-OFF
Custom Recovery
Custom ROM
My actual idea, it would be great if someone can confirm me it is in the right order:
Changing CID & Radio S-ON
Thats my big problem! It doesn't work with my actual ROM. I need to downgrade - But how? Clockwork Mod has annoying "Are you sure" selections like: "Flash? No, No, No, Yes, No, No" - Impossible to find that out without a display. And I can't flash any ROM, because I need adb checked by default - Otherwise I won't have access again to shell, and without shell I can't start my VNC Server, and without all that I can't do anything more and must send it like that to the garantuee. I've found an http://forum.xda-developers.com/showthread.php?t=939982 Raidroid ROM, with standard ADB if I understand that right. But how should I flash it?
Restoring H-Boot and Recovery
Code:
adb shell
su (if you get permission denied, you have to do Visionary temproot)
getprop ro.cid (this will tell you your stock CID, we will use that later, so write it down. It has eight digits.)
busybox dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21 (it will replace clockworkmod with original recovery)
busybox dd if=/sdcard/hboot_original.bin of=/dev/block/mmcblk0p18 (ONLY if you had ENG S-OFF, it will give you back SHIP bootloader)
sync (wait 10 secs after that, then you can close the adb shell window)
Flashing RUU
Everything should be away now... After all that everything should be allright and I can give my phone to guarantee.
Greetings
PMTheQuick
Click to expand...
Click to collapse
Anyone who knows an solution for the first problem?
Greetings
PMTheQuick
Hi, I have exactly the same problem. Did you find this out?
Did not notice any vibration, but otherwise I have the same problem. able only to see the screen image in daylight. When I tilt it.
Only volume and on / off button that works.
If this is a hardware problem, it will not mean anything to the warranty if it is rooted or not. In order for HTC to say it it must be a connection between the problem and the reason for it.
if you can see screen i day light then your backlight and digitizer is broken also rooting your phone void the warranty no matter what..... if you can see the screen in light you should be able to restore its original rom, and send it back to htc.
rakinisbat said:
if you can see screen i day light then your backlight and digitizer is broken also rooting your phone void the warranty no matter what..... if you can see the screen in light you should be able to restore its original rom, and send it back to htc.
Click to expand...
Click to collapse
Thank you for your response. You've probably absolutely right.
The screen is so weak that I hardly see anything.
Is there anything I can do to be able to see more, for example to connect to my PC?
Hi All,
I've been searching for days without luck. I'm trying to Unlock, Root, S-OFF, CWM my GSM Evo 3D, currently running HBOOT 1.49.0018
I'm following one of the many guides but get stuck at an early point. I'm trying to pull mmcblk0p31.img, so I can put it in the Hex editor and carry on the procedure, but every time I get permission denied:
Code:
/dev/block/mmcblk0p31: cannot open for read: Permission denied
Can anyone help?
After hours of searching these forums and going through google and translating loads of chinese, I'm none the wiser and thoroughly confused :S ...
Help would be appreciated.
Many thanks for your time.
In and type adb shell, then Su what u get?
Sent from my HTC EVO 3D X515m using xda premium
Superuser gets permission denied ...
Forgot to say I used the HTC Dev to unlock the bootloader to.
Btw, many thanks for an uber quick reply! Quicker than I got back to the general page!
alien.46.uk said:
Superuser gets permission denied ...
Forgot to say I used the HTC Dev to unlock the bootloader to.
Btw, many thanks for an uber quick reply! Quicker than I got back to the general page!
Click to expand...
Click to collapse
Have you tried this it worked for me http://forum.xda-developers.com/showthread.php?p=18694589
Sent from my HTC EVO 3D X515m using xda premium
Certainly have. Cant change the CID, though being Euro, it should be ok anyway.
And the IMG.zip seems to read (Blue bar on right side) but HBOOT always stays and 1.49.0018 .. and I dont get the update menu ... Sits reading the zip for a few mins then goes to normal menu still stating same HBOOT ...
alien.46.uk said:
Certainly have. Cant change the CID, though being Euro, it should be ok anyway.
And the IMG.zip seems to read (Blue bar on right side) but HBOOT always stays and 1.49.0018 .. and I dont get the update menu ... Sits reading the zip for a few mins then goes to normal menu still stating same HBOOT ...
Click to expand...
Click to collapse
Took me 5 attempts to get it working but finally got there
Sent from my HTC EVO 3D X515m using xda premium
When you say took 5 attempts is this with it reading the ZIP?
So if I sit there nd keep flicking in and out of Fastboot it should eventually read it?
On a side note, I notice you're UK to, did you have to change CID? Or was yours ok to? Cant find where to find out CID version.
Thanks.
alien.46.uk said:
When you say took 5 attempts is this with it reading the ZIP?
So if I sit there nd keep flicking in and out of Fastboot it should eventually read it?
On a side note, I notice you're UK to, did you have to change CID? Or was yours ok to? Cant find where to find out CID version.
Thanks.
Click to expand...
Click to collapse
Download cid getter from the market to get your cid
Did you relock your bootloader after changing cid? That's what caused most problems for me once it was relocked it was a doddle
Sent from my HTC EVO 3D X515m using xda premium
Handy tool! Looks naff on the higher res screen of the evo though! Like the photobucket app ... Bleh!
And no, bootloader remains unlocked! I will lock it again and give it a whirl!
alien.46.uk said:
Handy tool! Looks naff on the higher res screen of the evo though! Like the photobucket app ... Bleh!
And no, bootloader remains unlocked! I will lock it again and give it a whirl!
Click to expand...
Click to collapse
Lol bootloader needs to be locked to work you should find it a breeze after that
Sent from my HTC EVO 3D X515m using xda premium
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Hi guys I'm facing d same problems when I use adb command mmcblk0p31...... it says Permission Denied . I even tried that superuser command starting with Su and $ sign it copies the file which is of jst 16kb 'm literally stuck on this. I'm using stock Rom its unlocked rooted n hboot version is 1.53 m gsm and from india plz help I eagerly want 2 have s-off
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
Hi guys,
This is my first thread here in XDA, so, forgive me by a possible mistake.
I recently bought a HOX, the seller said that is the international version.
I'm in 4.0.3, with software version 1.29.707.11 (already checked for updates, but phone says its up to date)
So, sometimes when i turn my wifi on, he doesn't connect in my network (already saved), i go to wifi settings, put to scan, and, aparently, the phone don't scan the networks and doesn't found my network too.
Obviously, im on the range of the network, and don't have that factory problem with bad wifi signal.
And, sometimes too, phone takes a lot of time to get carrier signal, so i turn on plane mode, then turn off, and finally get carrier signal.
My question is: is this normal? What can i try to fix it? (Thinked on a factory reset)
I don't tried anything yet.
If anyone could help, i'll appreciate and if the thread is on the wrong place, please move it
Just try flashing the RUU, which will delete everything and return it to stock.
BenPope said:
Just try flashing the RUU, which will delete everything and return it to stock.
Click to expand...
Click to collapse
Thanks for the help Pope!
I am VERY noob in HTC tools, can you say me what exactly is this "RUU", and where i can get it?
Its basically, a factory reset right? What is the difference from normal FR to this RUU tool?
lock! said:
Thanks for the help Pope!
I am VERY noob in HTC tools, can you say me what exactly is this "RUU", and where i can get it?
Its basically, a factory reset right? What is the difference from normal FR to this RUU tool?
Click to expand...
Click to collapse
The difference is that it will reflash the ROM from scratch, it's the first thing HTC do when you take your phone for repair. It's very safe (when flashed with decent remaining battery) and very thorough.
Check the Shipped ROM sticky in the development section.
I am searching about the Rom Update Utility, but i'm not finding a good tutorial to follow, explaining the whole process.
If anyone could help me in the process :laugh:
Edit:
Thanks again Pope! I'll look in dev section
You just have to charge the phone, put the phone in fastboot mode (hold down the volume down key when switching on the phone, then navigate from there), plug phone into Windows PC and double click RUU.
You may want to do an "adb backup" (you'll have search for this) beforehand, flash RUU, test and then restore.
BenPope said:
You just have to charge the phone, put the phone in fastboot mode (hold down the volume down key when switching on the phone, then navigate from there), plug phone into Windows PC and double click RUU.
You may want to do an "adb backup" (you'll have search for this) beforehand, flash RUU, test and then restore.
Click to expand...
Click to collapse
I'm not finding the correct RUU file for the One X, can you help me? Or just show me a place to search... (Some links here at job are blocked --') Basically finding the correct RUU file i'll do the rest without problem...
This "restore" you mean in the end, its the factory reset in the phone? Or another restore?
Don't need a backup, i got the phone 2 days ago hehehe
My HOX is totally clean.
No unlocked bootloader, no root.
This will not be a problem doing the flash with the stock RUU right?
lock! said:
My HOX is totally clean.
No unlocked bootloader, no root.
This will not be a problem doing the flash with the stock RUU right?
Click to expand...
Click to collapse
No, that's perfect, you don't need anything other than stock, and it will remain stock.
http://www.filefactory.com/file/5c0...Radio_1.1204.105.14_release_260743_signed.exe
BenPope said:
No, that's perfect, you don't need anything other than stock, and it will remain stock.
http://www.filefactory.com/file/5c0...Radio_1.1204.105.14_release_260743_signed.exe
Click to expand...
Click to collapse
Ben sorry for tons of questions hehe
I'm reading a tutorial, and on it said that i need my CID number, in order to download the correct RUU file for the correct region of my HOX. How can i know if this RUU you posted is the correct for my HOX?
I've tried to get my CID number (downloaded the fastboot flasher tool) but when i put the cid command he returns: CID > None lol
I Know that my HOX is from Shangai (has a SH in serial number) and got my MID number.
So, i just need to know which file i need to download, the right one of course hehehe
If i will need the CID to know, i'll ask for the files for fastboot commands (i don't found them)
If not, just confirm the link you posted ealier if its the correct RUU for my case.
PS.: This link posted is only for premium users, and i don't have a premium acc, can you provide in another mirror?
You can't flash the wrong RUU, the phone won't let you.
You don't need your CID as you are not unlocked, knowing that you are 1.29.707.x is enough. It's the right RUU.
I'm sure you don't need me to hold your hand whilst you use google to find that file somewhere else. The sticky dev thread I previously mentioned will likely have a ton of mirrors for the file.
So.. i'll look fot the file in other places.
Today, i've connected in my wifi network, and the phone says there's an update...
It's the same update announced days ago, but in my case with a different update number...
Phone has been upgraded to ICS 4.0.4 and Sense 4.1.
If the problems persist, i will flash the RUU anyway, but, because of this update, nothing changes right? The RUU file you posted still valid for my HOX?
Not any more, you've updated your hboot, so you'll need an updated RUU (you can't install on older hboot, packaged with an older RUU).
You're lucky:
http://www.filefactory.com/file/3rc...Radio_2.1204.135.20_release_278245_signed.exe
and
http://forum.xda-developers.com/showpost.php?p=30273253&postcount=1724
BenPope said:
Not any more, you've updated your hboot, so you'll need an updated RUU (you can't install on older hboot, packaged with an older RUU).
You're lucky:
http://www.filefactory.com/file/3rc...Radio_2.1204.135.20_release_278245_signed.exe
and
http://forum.xda-developers.com/showpost.php?p=30273253&postcount=1724
Click to expand...
Click to collapse
HELL YEAH!
I'll test for 2 ~ 3 days, if i note the same problem i'll flash it!
Thanks for all the help Pope!
With this 707 update I got better WiFi ..smooth, fast...amazing
Sent from my HTC One X using XDA Premium HD app
dragonesdenano said:
With this 707 update I got better WiFi ..smooth, fast...amazing
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Same here man...
In a network that once stood in 40% signal, now i'm getting almost 100%!
Apparently, carrier signal is working fine too.. i'll test for more 3 days...
I have just been given an old Wildfire that is unrooted, s-on and network locked that has somehow managed to get itself into Qualcomm diagnostic mode. I am unable to get anywhere, adb - device offline. Is there anyway to force on USB debugging so that I am able to use a goldcard?
Dav1_d said:
I have just been given an old Wildfire that is unrooted, s-on and network locked that has somehow managed to get itself into Qualcomm diagnostic mode. I am unable to get anywhere, adb - device offline. Is there anyway to force on USB debugging so that I am able to use a goldcard?
Click to expand...
Click to collapse
bottom line is nope. how is the device reacting? is it just black screening with vibrations?
totally of topic but 1000 posts XD
I'm a bit confused with this diagnostic mode?
If i remember correctly i was able to go into it with vol up + power but then after a battery pull it would reboot just fine........
Maybe as Lesicnik mentioned not so long back the volume button might be stuck or faulty hence pressing the power button will equal vol up+power and start diag mode.
Sent from my GT-I9100 using Tapatalk 2
Scratch0805 said:
I'm a bit confused with this diagnostic mode?
If i remember correctly i was able to go into it with vol up + power but then after a battery pull it would reboot just fine........
Maybe as Lesicnik mentioned not so long back the volume button might be stuck or faulty hence pressing the power button will equal vol up+power and start diag mode.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
qualcomm diagnostic mode happens when you f**k up the phone so bad that it doesnt know what else to do, and reverts to what i think is the backup firmware on the nand chip? not 100% sure. it usually results in the phone powering on but not showing anything on screen. but vibrates a few times depending on what the issue is. sometimes you can "blindboot" which is where you take a stock rom.zip from a ruu and place it on the sdcard and boot to bootloader. then by using time (ie waiting) and logic (when to try push volume up to update the rom+reboot) you can sometimes manage to restore the phone. as far as i am aware the guys over at the evo 3d forum are very advanced in how this mode actually functions. the htc sensation unbricking project, which helps people fix their phones after an attempt to s-on kills it was made with the help of the evo 3d guys knowledge. also i think jupuntobear s-off puts the phone into download mode before you do the "wire trick" to drop write security. so it is possible to fix this issue but it is quite a hard nut to crack.
Scratch0805 said:
I'm a bit confused with this diagnostic mode?
If i remember correctly i was able to go into it with vol up + power but then after a battery pull it would reboot just fine........
Maybe as Lesicnik mentioned not so long back the volume button might be stuck or faulty hence pressing the power button will equal vol up+power and start diag mode.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Have already taken phone apart and checked all connections as my first thought was that something may have worked itself loose after being dropped or something.
Vol up + power and the phone buzzes/vibrates 3 times.
Managed to do a blind factory reset - vol down + power wait for a bit, then vol down etc, etc. After about 3-4 minutes I was able to push the soft buttons which light and vibrate. I am unable to do anymore than this due to usb debugging being off as I need to use adb to make a gold card and run a ruu. Thanks anyway.
heavy_metal_man said:
qualcomm diagnostic mode happens when you f**k up the phone so bad that it doesnt know what else to do, and reverts to what i think is the backup firmware on the nand chip? not 100% sure. it usually results in the phone powering on but not showing anything on screen. but vibrates a few times depending on what the issue is. sometimes you can "blindboot" which is where you take a stock rom.zip from a ruu and place it on the sdcard and boot to bootloader. then by using time (ie waiting) and logic (when to try push volume up to update the rom+reboot) you can sometimes manage to restore the phone. as far as i am aware the guys over at the evo 3d forum are very advanced in how this mode actually functions. the htc sensation unbricking project, which helps people fix their phones after an attempt to s-on kills it was made with the help of the evo 3d guys knowledge. also i think jupuntobear s-off puts the phone into download mode before you do the "wire trick" to drop write security. so it is possible to fix this issue but it is quite a hard nut to crack.
Click to expand...
Click to collapse
Thanks, will check out Evo3D forum tomorrow, hopefully someone over there will be able to help.:fingers-crossed: Btw you need to have USB debugging enabled to run jupuntobear s-off.
Dav1_d said:
Thanks, will check out Evo3D forum tomorrow, hopefully someone over there will be able to help.:fingers-crossed: Btw you need to have USB debugging enabled to run jupuntobear s-off.
Click to expand...
Click to collapse
do you know what network the phone was locked too? you could hunt for the offical ruu from that network with the 1.01.0002 hboot and try to blind boot that to restore the phone. if you can tell me the network its on i will help you hunt for the ruu 3 vibes is better than 5 as far i know. ive heard of people recovering from 3 vibes.
also, if you have access to another wildfire you can use that to make the goldcard and then use that on the damaged phone then it should run any ruu that has an equal or higher hboot ^^
heavy_metal_man said:
do you know what network the phone was locked too? you could hunt for the offical ruu from that network with the 1.01.0002 hboot and try to blind boot that to restore the phone. if you can tell me the network its on i will help you hunt for the ruu 3 vibes is better than 5 as far i know. ive heard of people recovering from 3 vibes.
also, if you have access to another wildfire you can use that to make the goldcard and then use that on the damaged phone then it should run any ruu that has an equal or higher hboot ^^
Click to expand...
Click to collapse
The phone is locked to Vodafone UK. I've just spoken to my sister whose phone it was (she's not the most technically clued up of people) and she can't remember whether she upgraded to froyo or not. She's now got a GS2 and hasn't even done the official OTA update to ICS (and Touchwizzed Jellybean is on the horizon). So I'm betting its still on Eclair, but I can't be 100% sure. I've looked on the Vodafone UK site and the latest Wildfire software version is '2.24.161.2', which they are only giving out through an OTA. I'm not having much luck googling it either.
I don't have any access to another Wildfire, so the only thing I can think of is if I can find someone else who would be so kind as to make and upload a goldcard for me :fingers-crossed: (highly unlikely), otherwise I think the phone may be taking a trip to environphone (they give £20 for a working wildfire). I'll spend another couple of hours on it, seeing what I can come up with, but it's looking bleak at the moment .
Dav1_d said:
The phone is locked to Vodafone UK. I've just spoken to my sister whose phone it was (she's not the most technically clued up of people) and she can't remember whether she upgraded to froyo or not. She's now got a GS2 and hasn't even done the official OTA update to ICS (and Touchwizzed Jellybean is on the horizon). So I'm betting its still on Eclair, but I can't be 100% sure. I've looked on the Vodafone UK site and the latest Wildfire software version is '2.24.161.2', which they are only giving out through an OTA. I'm not having much luck googling it either.
I don't have any access to another Wildfire, so the only thing I can think of is if I can find someone else who would be so kind as to make and upload a goldcard for me :fingers-crossed: (highly unlikely), otherwise I think the phone may be taking a trip to environphone (they give £20 for a working wildfire). I'll spend another couple of hours on it, seeing what I can come up with, but it's looking bleak at the moment .
Click to expand...
Click to collapse
ok i have found a vodaphone rom that is from denmark, or germany it may be enough to do it. also, the goldcard is specific to the sdcard that is used to make it buddy :/ but! although i may not have a wildfire i do have the xtc clip so i can make a goldcard for the wildfire. so if you were willing to post a small micro-sdcard to me i could make it for you i am currently uploading the rom to mediafire now. will edit this with a link asap
EDIT: ok here is the rom.zip i was talking about, rename it to pc49img.zip and try do a cold boot up to fix it.
heavy_metal_man said:
ok i have found a vodaphone rom that is from denmark, or germany it may be enough to do it. also, the goldcard is specific to the sdcard that is used to make it buddy :/ but! although i may not have a wildfire i do have the xtc clip so i can make a goldcard for the wildfire. so if you were willing to post a small micro-sdcard to me i could make it for you i am currently uploading the rom to mediafire now. will edit this with a link asap
EDIT: ok here is the rom.zip i was talking about, rename it to pc49img.zip and try do a cold boot up to fix it.
Click to expand...
Click to collapse
Nice one :good: Just about to have something to eat then I'll give it a shot. Will post how I get on in a couple of hours. Thanks again.:fingers-crossed:
Dav1_d said:
Nice one :good: Just about to have something to eat then I'll give it a shot. Will post how I get on in a couple of hours. Thanks again.:fingers-crossed:
Click to expand...
Click to collapse
no bother man, i will be in work all night so keep me posted
heavy_metal_man said:
no bother man, i will be in work all night so keep me posted
Click to expand...
Click to collapse
No joy , My girlfriend is going mad at me to get off the computer, will try again tomorrow.
Dav1_d said:
No joy , My girlfriend is going mad at me to get off the computer, will try again tomorrow.
Click to expand...
Click to collapse
OK man, looks like your going to need a gold card like.
Sent from my HTC Sensation using xda premium