I am having trouble flashing my diamond,
everytime I try, it would be at 0%, nothing happens,
then after a while it goes into the recovery mode.
What am I doing wrong? I tried the HTC Official Update, and it works,
however, not Dutty's one....any help?
Make sure that if you are using Vista or WDMC, you are using the latest driver version (2007) when in bootloader mode.
Change to bootloader mode, go to windows update, search, and install the newest driver.
It will work then.
Cya,
Viper BJK
yes, i am using vista and wmdc, i am a newbie at this,
how and where do i change to bootloader mode?
details would help, thanks.
Just search this forum
As for bootloader, if the phone is on, turn it off.
For that, press power button long, confirm.
Once it is off, first press and hold volume down + press the power button, hold both until you see the tricolor bootloader screen.
Cya,
Viper BJK
You need to flash Unsigned-HardSPL before flashing Dutty's ROM. It will work then.
I am having problem updating the HTC USB Sync driver,
it says that "Windows found driver software for your device but encountered an error while attempting to install it. Access is denied"
I tried updating manually but it says I have the best one available, but it is the 2006 one....HELP
read the tutorial Complete upgrading guide (HardSPL+Radio+ROM) NOT FOR CDMA USERS!!!
ztealth said:
I am having problem updating the HTC USB Sync driver,
it says that "Windows found driver software for your device but encountered an error while attempting to install it. Access is denied"
I tried updating manually but it says I have the best one available, but it is the 2006 one....HELP
Click to expand...
Click to collapse
Go into bootloader. Search for update in windows update. Once it tries to install it, disconnect the phone. That should work. But your phone has to be in bootloader mode, otherwise the driver cannot be installed.
Cya,
Viper BJK
ztealth said:
I am having trouble flashing my diamond,
everytime I try, it would be at 0%, nothing happens,
then after a while it goes into the recovery mode.
What am I doing wrong? I tried the HTC Official Update, and it works,
however, not Dutty's one....any help?
Click to expand...
Click to collapse
you need to unlock your phone first
Related
I download the RUU Rom link and ran it. I have the phone connected, but when I try to do the update it says my phone is not connected. Anyone have any ideas?
First suggestion would be not to use the RUU as from what I've seen it updates HBOOT which seems to restrict things going forward .
modaco's 2.2 rom is basically a rooted rom from the RUU you can also get the updated radio from his site too without updating HBOOT.
Both the radio and the rom are in a nice update.zip format which is easy to use but you do need to backup contacts stored on the phone and sms etc as it does require a wipe. (the again I believe the RUU dies this too anyway).
Breakthecycle2 said:
I download the RUU Rom link and ran it. I have the phone connected, but when I try to do the update it says my phone is not connected. Anyone have any ideas?
Click to expand...
Click to collapse
Try to start it from the fastboot. Switch of the phone. Turn it on again holding the back, and on/off button till you see the 'fastboot' screen. Then connect the phone with the PC and wait till the drivers are loaded and you see in the screen 'fastboot usb'. Then run RUU****.exe again.
That worked on my Vista Ultimate 64bits machine.
Heppieboeddah said:
Try to start it from the fastboot. Switch of the phone. Turn it on again holding the back, and on/off button till you see the 'fastboot' screen. Then connect the phone with the PC and wait till the drivers are loaded and you see in the screen 'fastboot usb'. Then run RUU****.exe again.
That worked on my Vista Ultimate 64bits machine.
Click to expand...
Click to collapse
I actually got it. I didn't need fastboot. Im such a dumb ass. I never installed HTC sync.
Breakthecycle2 said:
I actually got it. I didn't need fastboot. Im such a dumb ass. I never installed HTC sync.
Click to expand...
Click to collapse
Djeez! What is the rtfm for? Even basics are to difficult for some..
Currently using the Dinc with stock. Unfortunately, I can not root because of business.
I'm having a problem installing the RUU. I connect the Dinc to my computer (W7 64bit) and run the RUU. (I have HTC Sync installed).
When I run the RUU, it will see the phone and it will begin updating. At the point where it restarts the bootloader, the screen on my Dinc will turn black and restart and then appear with HTC.
At this point it will hang and the computer attempts a driver search causing the error 171 - Not able to connect with USB cable.
Can anyone provide any assistance with this? Greatly appreciated!
Sorry if this is confusing but i couldn't find the thread on XDA on the alternate method.
http://www.techpetals.com/how-to-ro...ible-leaked-version-froyo-manual-install-1937
Step 6 is the end for installing just the update and no root.
Viralwhite said:
Currently using the Dinc with stock. Unfortunately, I can not root because of business.
I'm having a problem installing the RUU. I connect the Dinc to my computer (W7 64bit) and run the RUU. (I have HTC Sync installed).
When I run the RUU, it will see the phone and it will begin updating. At the point where it restarts the bootloader, the screen on my Dinc will turn black and restart and then appear with HTC.
At this point it will hang and the computer attempts a driver search causing the error 171 - Not able to connect with USB cable.
Can anyone provide any assistance with this? Greatly appreciated!
Click to expand...
Click to collapse
this happened to me. windows 7x64 did not like the driver switching mid process from android to bootloader, so basically here is what i did.
leave the phone connected (it should have black screen with htc logo). once u get the 171, exit the RUU (if u havent restarted the pc ever, now is a good time - if u restart pc, disconnect phone, battery pop it to get it to boot)
now run the RUU, again u will get the 171 and the phone will be black with htc on it. just exit the RUU and re run the RUU, this time it will run the full process.
Tired of scouring through help videos and google searches... I hope someone on here can help me.
Rooted my HTC Desire via the unrevoked 3.2 method and used for a few days before deciding to S-OFF. Well i made a mistake and got stuck in a boot loop. Reflashed the RUU and i am back in business.
The issue is that i had to reinstall HTC Sync to reflash the RUU and then uninstall again so i could re-root, leaving the drivers in of course. I noticed that when i connect phone to PC via the same method as before, it should have had 'ANDROID 1.0' in device manager but this time it says MY HTC.
Can anyone explain what to do?
1) I can go ahead and root as before, this is just the new version of HTC Sync drivers.
2) Stay clear, the new drivers mean the bootloader is locked.
Which is it?????
I am a noob and although some members on here instructed me to use adb, i am out of my depth with that, even the guides available aren't simple enough for me.
Surely there must be an easy way out of this?
Any help would be much appreciated!
u can try uninstall the drivers and reinstall them back to be safe. also install the modified hboot drivers from unrevoked.
Thanks for your reply. Already tried to uninstall then reinstall the drivers. The issue is happening when I try to install the modified hboot driver, it says the driver is up to date but doesn't show as 'Android Bootloader Interface'.
Sent from my HTC Desire using XDA Premium App
When your Mobile is fully booted it will show My HTC.. and when you will boot into fastboot.. by volume down and power.. you will see 'Android Bootloader Interface'.
So that mean, YES you can root with unrevoked while you have 'MY HTC' in device manager with USB Debugging On.
jhonybravo4u said:
When your Mobile is fully booted it will show My HTC.. and when you will boot into fastboot.. by volume down and power.. you will see 'Android Bootloader Interface'.
So that mean, YES you can root with unrevoked while you have 'MY HTC' in device manager with USB Debugging On.
Click to expand...
Click to collapse
Thanks!!!!!
Didnt realise i had to choose fastboot to see which drivers i had installed. Issue resolved. Many thanks!!
I told you XDA was awesome!
OriginalThinking said:
I told you XDA was awesome!
Click to expand...
Click to collapse
Important correction: IS(!!!!), not was.
hey guys, I'm a real noob when it comes to adb(med student here, so have very little info). I was flashing jellytime R30 and rebooted , when the phone got stuck at a black screen after the HTC logo. I would have used the volume down key to boot into hboot/bootloader but my volume down key isn't working.
I installed the SDK and tried to run a command to reboot but clearly I did something wrong as nothing happened. It said "error:device not found".
Would really appreciate some assistance here.:crying:
Are your drivers installed properly?
bananagranola said:
Are your drivers installed properly?
Click to expand...
Click to collapse
I was just checking and it seems I don't have the required driver. I understand I'll have to install HTC sync to have the drivers?
Yes, you need the HTC Sync drivers. Make sure your phone is unplugged from the computer when you install them. I believe that's important.
Thanks guys..installed the drivers and managed to boot into recovery. :good:
Hi Guys,
Yesterday during an official update of my oneplus 5t (using the update manager from the phone itself), the phone got bricked and i dont know why....
So after some research i found it is hard bricked ( basically i cant do nothing, power on i cant, power +volume UP/DOWN too, and even when i plug the charge cable i have neither vibrations nor LED on)
So i follow this tutorial to unbrick the phone:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
I could get the phone recognize by the PC by pressing UP to see the phone as QUSB-BULK and then QUALCOMM QD LOADER after driver's update.
But when i run MSMDownloadTool ( V4.0.27 dumpling 43_0.36_180613) as administrator and click on start, the process get stuck in "waiting for device"
the status of connection before click on start was "connected" and after click and some process it turn to N/A
the status of communication is "memory size....."
status of last communication is "waiting for device"
I have tried several time and always the same result..... stuck in the waiting device
does someone have an idea on how to solve this? because i really need to unbrick the phone....
thank you in advance
EDIT:
I tried another version of MsmDownloadTool (dumpling_43_O.06_171206) and this time, the downloading of cache image failed....
I dont know what to do
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
DaRk-L0rD said:
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
Click to expand...
Click to collapse
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
rokusho32 said:
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
Click to expand...
Click to collapse
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
DaRk-L0rD said:
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
Click to expand...
Click to collapse
I have installed the ADB drivers
which version of MSMDownloadTool should i use?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
rcbjr2 said:
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
Click to expand...
Click to collapse
I have same situation.. did you resolve this problem?
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
I contacted OnePlus and I sent them the phone and they reinstalled the operating system. I was never able to fix it myself. I even had an online session with OnePlus and they couldn't get the MSM software to recognize the phone (even though it was truly connected to my laptop). I also had an issue with my OnePlus 8T that got messed up doing something with Magisk, and OnePlus reinstalled the operating system as well. I still can't boot from the A partition though; just the B partition.
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
At first, I chose WWAN-DHCP - which caused problem with connection
piechu11 said:
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
View attachment 5511425
At first, I chose WWAN-DHCP - which caused problem with connection
Click to expand...
Click to collapse
Thank you this solved my problem exactly.
i was restoring my metro by tmobile oneplus nord n10 BE2025 model with build tag BE88CF