I tried this a bunch of times and mine just comes up with a blinking green light. Nothing ever comes onto the screen Even when i tried booting up holding the power and volume down key.
Basically this is what happened to me...
My evo would come up as s-on and wouldnt hold any RUU that i installed on it. For example after it installs, and if i turn it off and turn it back on, it would go back to the supersonice s-on screen. So i read that it had to be on s-off in order to hold a RUU. So i used unrevoked and and tried doing that, but unrevoked stayed on waiting for phone to turn on and my phone never turned back on i unplugged it and tried turning it back on but it only vibrates and stays on a black screen. I plugged it in after i doing that and it shows up as missing a Qualcomm CDMA Technologies MSM driver and it doesnt install it even when i try using windows mobile device. Installation keeps failing.
I would appreciate any help. Thanks!
so if i am understanding this correctly:
-your phone was hanging at a splash screen
-you ran ruus,wich installed without error,but still did not boot
-you ran unrevoked,wich started to work?
what mode was the phone in when you first ran it? and what firmware/build number were you on? had the phone actually booted when you ran it,and you started from the booted OS?
this leaves you in the following predicament(with addition of 3 vibes when you ry and power on,correct?):
o.k...so I put out a call for help from some friends and so to bring them up to speed, the following is true:
1. Black screen.
2. Cannot boot into bootloader (via holding volume down/holding power button)
3. usb debugging enabled...we think?
4. "adb devices" in adb brings up nothing
5. computer device manager says you need Qualcomm drivers.
I hope that I wrong but it sounds like you are stuck in Qualcomm download mode.
Contact the unrevoked guys to confirm and see if they have a fix.
i think early is correct,you are stuck in "qualcom
diagnostic mode" wich is different than download,or QHUSB_download mode,wich is what they are utilizing for the newer emmc phones. you could certaily attempt some of the tricks with linux described in the 4gLTE threads,but i do not believe you will have the same results,at least not withthe same tools,with an older mtd device.
unfortunately,i believe your phone has moved on to a better place.
i assume that your references to "not being able to hold an ruu" were implying that they were installing,and not fixing the issue,wich indicates a greater prollem back at the beginning,asthe information that you recieved about beind s off for ruus to hold or stick,was false. ruus are run on phones quite a bit to fix/restore/update,the radio secure flag has noting to do with their abilitys to hold the update,it just dictates wether certain criteria must be met(correct modle,cid,main version,etc). s off phones are simply not doing security checks.
combination of whatever was wrong prior,and unrevokeds exploit may have finished it off,as the radio secureflag does live in a very important part of the phone(Radio nv ram),where damage could certainly cause the phone to panic,and not boot.
in my searching,i was unable to come up with any instances where qualcom diagnostics mode was used to unbrick or resurect and older device. the most common issue is folks entering it accidentally(via vol up,not down + power),wich is easily fixed with a battery pull when the rest of the phone is functioning properly. i found some references to unplugging the usb and removing the battery at the same time to get out,and also one situation with an incredible that was similar,and would enter diagnositc mode when you tried to boot it unplugged,but would boot up if you powered it on with it pluged in.
its a long shot,but worth a try,you might leave it plugged in several hours,unplug,pull batter,plug back in and power on,or just power it on after several hours(use a wall charger,not a usb in a pc)
at this point,it wont really matter if usb debug was on,as adb is only used within the booted OS,or in most custom recoveries.
if youve installed the entire sdk,might cahge to the directory containing fsatboot(usually tools) and then try:
fastboot devices
if you did happen to get a response back(serial number) then try
fastboot reboot-bootloader and see what heppens.
wish i could be of more help. i dont believe finding drivers will help much... with the lack of info on what you can really do with this mode.
i tried to find the quALcom technologies drivers one afternoon,and had not any luck.
if you do happen to find some,make sure you post the link
we can certaily see what we can do with them
