I just recently got myself the m8 and am having a little problem with it. I was able to root, s-off and unlock it with no problems. What I am having trouble with is when I try to RUU back to stock for the 6.0 upgrade it will not work. The issue I am having is that upon running the exe, it starts throwing a dialog box with "Click here to next dialog!" I tried running the VC 2008 and repair but it did not fix it. Curious if anyone has any ideas on how to fix this. Win10 64bit.
Edit: So I tried using my Win7 machine and it ran fine without the crazy dialog box. Seems Win10 doesn't like the RUU program?
Related
Has anybody upgraded their rom on Windows Vista RC2 yet? It syncs with no problem but I'm a bit leary about being the test user for rom upgrading (and subiquent bricking) of my TyTN. Unfortunatly I currently don't have a machine running XP in the house or i'd just do it on that. Do I need to reinstall XP on one of my machines or has anybody been successful with RC2?
I tried to upgrade my JJ using Vista RC2, it doesn't brick my device, but it doesn't upgrade it, a message of connection error appears after a whle.
chymmylt said:
Has anybody upgraded their rom on Windows Vista RC2 yet? It syncs with no problem but I'm a bit leary about being the test user for rom upgrading (and subiquent bricking) of my TyTN. Unfortunatly I currently don't have a machine running XP in the house or i'd just do it on that. Do I need to reinstall XP on one of my machines or has anybody been successful with RC2?
Click to expand...
Click to collapse
I have tried under vista rc1 with newest updates of mobility center (I think 28/10/2006) but during upgrade my qtek9000 went into bl mode and nothing helped only removing vista and reinstall xp.
Too bad to hear - time to wipe a machine and reinstall XP Oh well - could be worse things!
Ok I have trouble with every rom I have found...
Orbit O2 running the latest WM5.
I start the rom upgrade for B&B and as it starts to get into the strange splash screen (I assume its a bootloader type thing, multicloured), it disconnects from my pc (running vista and the new mobile device centre 6) of course, then reconnects (i hear the tone anyway) but then the rom upgrade program tells me that it cant connect.
Thus my device is stuck on the loading page.
Another attempt to use the UG program brings me further: to the loading % screen. it gets to 3% and then the device resets and loads fully.
This is where it ends. another attempt brings me back full circle...
I had a similar problem with the official o2 rom, but the second attempt didnt stop at 3% so it went all the way.
after upgrading, I cant progress from the above any better.
I want the B&B for its interface, 3d cube and touchflo. Is there a way to add these onto my existing rom?
Thanks guys.
Have you got another pc or laptop you can try this from?
If not try disabling all your firewall and anti virus whilst upgrading.
the real issue i think isthe sync disconnecting while transferring data.
either that or my phone doesnt like anything over the 3% mark on these rom builds.
no firewall, no antivirus.
i had the same problem. this is what i did.
i installed the original wm6 of htc and from there installed bb 4
thanks ill try that.
ive so far installed the o2 orbit rom and then tried the bb4 same problems.
but ill try the htc version now.
You MUST flash the USPL upgrade first. After this you can then flash to B&Bv4.
By the way. If you can get access to a Windows XP computer, use this to flash. Windows Vista as VERY picky when upgrading.
There is a problem with upgrading you're rom in combo with windows vista. I assume upgrading is only possible with active sync 4.5(XP).
USPL and vista give's a lot of problem's like the one you discribe. Try upgrading your rom from a PC with XP.
I had the same problem. I Could'nt upgrade my rom from a PC with VISTA. Xp was the sollution for me.
thanks guys.
im gonna look into upgrading the uspl, but i dont have an xp machine. only vistas and a mac
just tried the uspl....
dos counted up 0...10....20 etc up to 70, then skipped to 100 and the rom update program launched. it went into the multicoloured splash loader then stopped.
im gonna try on xp later if i can...
ok for anyone who has similar issues to me...
I just got a Hermes today (£60, tmob) and same upgrade problems.
XP machine isnt an option for me...
BUT i found this http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27 for anyone who needs advice on vista. its very simple and works a treat.
thanks
my experiences
I couldn't flash USPL on my IBM T40p(Win XP SP2). I use other PC with clean instalation of W2K(SP4) and AS4.5(nothing else instaled) and it work fine(flash USPL then B&B 3.7-to test it then B&B 4.0). I realize I'm using Kerio Firewall on my laptop, AS 4.5 don't connect to Artemis with Kerio Firewall instaled!
Advice for all:
1) try again to flash USPL
2) TRY AGAIN!!!
3) try other pc
4) try again
.....
5) once flashed UPSL(your SPL should be 1.11.0000) flash the B&B Rom(or any other you want) - do it on same pc which you use for succesfull flashing of USPL
running vista? upgrade issues?
XP machine isnt an option for me...
BUT i found this http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27 for anyone who needs advice on vista. its very simple and works a treat.
thanks
As long as you have updated to WMDC 6.1, flashing with Vista is a breeze. Just plug in the USB cable and flash like XP.
I can confirm that as well, as long as you update to Device Center version 6.1, the vista flashing guide is not needed. The RUU tools (including auto detect) will work fine when the device is plugged in and synced.
Im soooooooooooooooooooo glad I didnt "upgrade" to have vista on my pc
That is the rub...
millercentral said:
I can confirm that as well, as long as you update to Device Center version 6.1, the vista flashing guide is not needed. The RUU tools (including auto detect) will work fine when the device is plugged in and synced.
Click to expand...
Click to collapse
... I've followed MrVanx's instructions but, the issue for me is syncing. I can connect just fine but getting my 8525 to Sync is a no go.
It seems that my Vista machine consistently renames my device from *******_PC to HTCXX (Usually a number).
Weird.
I followed the instructions and successfully upgraded my ROM, but every time I installed SplashID, I could no longer Sync.
So I just downgraded WMDC to 6.0 (found here), and all my problems appear to be gone - I can sync with no problems.
--------
UPDATE
I still get the strange TCP/IP errors - bringing up Vista's task manager, killing WMDC and restarting it makes it go away. Gotta love Microsoft.
ive been running vista and flashing / cooking for 2 months now without any problems (using 6.1) however syncing is a completely different story! In fact I'm waiting for a copy of lastxp to finish downloading to reformat xp back
I have never had any problems with Vista and WMDC 6.1
No problems either, using WMDC 6.1 on 2 different Vista machines, and haven't had any problems flashing or synching.
Many thanks HunterST!
HunterST said:
I followed the instructions and successfully upgraded my ROM, but every time I installed SplashID, I could no longer Sync.
So I just downgraded WMDC to 6.0 (found here), and all my problems appear to be gone - I can sync with no problems.
--------
UPDATE
I still get the strange TCP/IP errors - bringing up Vista's task manager, killing WMDC and restarting it makes it go away. Gotta love Microsoft.
Click to expand...
Click to collapse
Thanks for the tip. I can finally sync again. It's not perfect but, I'm at least getting closer.
Peace.
ratcom said:
ive been running vista and flashing / cooking for 2 months now without any problems (using 6.1) however syncing is a completely different story!
Click to expand...
Click to collapse
I work in IT and am using my system to test Vista functionality within our company. So far it has worked like a charm, much better than the days of beta. I prefer XP still for functionality but I have enjoyed Vista and will probably continue to run it on both my work and home systems (Enterprise, Basic/Home is for the lose).
Flashing has been a cakewalk overall. Syncing isn't too bad however it does have it's hiccups. Two problems have surfaced so far, one is related to WMDC being flaky about picking up the phone (although better in 6.1 than 6.0) the other is related to wirelessly syncing to Exchange which has nothing to do with Vista at all and just my laziness to troubleshoot it. lol
Hey guys,
I have an unrooted HTC Desire that seems to have developed the dreaded motherboard issue.
Im trying to unroot in order to send it back in, but whenever I try installing an RUU (downloaded from shipped-roms.com) the Installshield gives me an error "-5001 : 0x80070002"
I can't seem to find out whats causing this error, but any help would be appreciated.
For what its worth, I'm running an MIUI ROM.
Downloaded another file and it worked. Unrooted and everything is working fine.
I've just rooted and installed Viper ROM on my ATT HTC m9 and everything works great except I can't receive phone calls. The phone never even rings. I've also flashed ICE and ARHD with no success receiving phone calls. If I restore to a TWRP backup of stock the phone works perfectly so it's obviously something to do with the ROM.
I've checked the other posts on here and none of the fixes have worked, yet. I wanted to try to RUU but whenever I run the RUU application (windows 8.1) the progress bar to initialize the setup completes and the program closes. It never does a flash. I've tried running as admin, disabling services, and running in Win7 compatibility mode to no success.
Do any of you have any ideas on either of these?
mdomino said:
I've just rooted and installed Viper ROM on my ATT HTC m9 and everything works great except I can't receive phone calls. The phone never even rings. I've also flashed ICE and ARHD with no success receiving phone calls. If I restore to a TWRP backup of stock the phone works perfectly so it's obviously something to do with the ROM.
I've checked the other posts on here and none of the fixes have worked, yet. I wanted to try to RUU but whenever I run the RUU application (windows 8.1) the progress bar to initialize the setup completes and the program closes. It never does a flash. I've tried running as admin, disabling services, and running in Win7 compatibility mode to no success.
Do any of you have any ideas on either of these?
Click to expand...
Click to collapse
I had this happen too and it's still kind of a mystery as to what causes it. Did you see this thread? My posts in there are everything I did to fix this, but I can't say exactly what step fixed it. http://forum.xda-developers.com/one-m9/help/unable-to-receive-phone-calls-t3137209
I haven't had the issue in about three weeks now, so whatever it was is apparently fixed. I'm on ICE 3.0.1 with no issue. A definite short-term fix is to do steps 2 or 3 of post #3 in the above link. I suspect it has something to do with either the radio not reading the default.xml file properly or the default.xml file not containing the correct voLte settings.
jollywhitefoot said:
I had this happen too and it's still kind of a mystery as to what causes it. Did you see this thread? My posts in there are everything I did to fix this, but I can't say exactly what step fixed it. http://forum.xda-developers.com/one-m9/help/unable-to-receive-phone-calls-t3137209
I haven't had the issue in about three weeks now, so whatever it was is apparently fixed. I'm on ICE 3.0.1 with no issue. A definite short-term fix is to do steps 2 or 3 of post #3 in the above link. I suspect it has something to do with either the radio not reading the default.xml file properly or the default.xml file not containing the correct voLte settings.
Click to expand...
Click to collapse
Thanks! I followed your steps and got it working. It seems from what you and Venom support said that the problem is with going directly from the ATT RUU (5.0.2) to a custom 5.1 ROM. Once I flashed the developer edition RUU and edited the default.xml I was able to flash ViperROM and have calls working without any further tinkering.
Thanks a ton!
mdomino said:
Thanks! I followed your steps and got it working. It seems from what you and Venom support said that the problem is with going directly from the ATT RUU (5.0.2) to a custom 5.1 ROM. Once I flashed the developer edition RUU and edited the default.xml I was able to flash ViperROM and have calls working without any further tinkering.
Thanks a ton!
Click to expand...
Click to collapse
Thanks for the feedback. That's weird though because I couldn't even receive calls on the developer edition.
I couldn't make calls until editing the default.XML in developer edition. I'm still not sure how it works but I'm happy either way!
Sent from my HTC One M9 using XDA Free mobile app