I know there is a post from duanes that supposedly walks you through changing drivers in vista to the earlier "xp" drivers. first of all it says "follow steps 3 and 4." THERE ARE NOT ANY STEPS 3 OR 4!!! also the attached file from rapidshare is not correct. in his instructions he says to extract the files. there is nothing to extract after the file is downloaded. any help on this would be so much appreciated. i am getting tired of my vogue and need a change. Thanks in advance!!!
would someone be willing to walk me through these steps in an easier way to understand??? i am running 32 bit vista
the link to duanes instructions are here: http://forum.xda-developers.com/showthread.php?t=313001
I'm having no problems. Make sure you're using WinRAR (rarlabs.com , IIRC) to extract the file. If you want, I can re-archive the files into a ZIP file for you.
oh man that would be awesome. thanks so much!
ok so i got the files to extract using winrar or what not. now i can't seem to get my phone into bootloader mode. i'm holding camera+power+reset and nothing happens. am i doing something wrong? also when i go to computer manager and get into device manager "mobile devices" is not there. any help would be awesome, thanks
Make sure you are hitting all the buttons, maybe your finger is slipping off one. Also, be sure you're pushing the stylus in the right hole for the reset button. One time I accidentally let customizations run because I was trying to poke the stylus in the microphone hole.
As for device manager, make sure the phone is plugged in when you look, and make sure it connected. Stuff only shows up when it's plugged in. Also, go to 'view','show hidden devices'. Something might have set the device to hidden.
I have flashed several of NFSFAN's ROM with Vista with no issues. It shouldn't be any differnet that using XP. As long as you are connected to WMDC.
wait, so you have flashed roms without changing anything in vista? i tried to flash the 6.1 stock sprint rom back in the day and it locked up my vogue. thats why i am very weary of even messin with vista. so should the phone be on or off when i attempt to put the phone in bootloader mode? aaaaaaaaaaaahhh!!! i would like to think i'm not a noob but everything i try to do is actin different than all other posts that are reporting. HELP PLEASE!!! you all have been great so far!
jlip5617 said:
so should the phone be on or off when i attempt to put the phone in bootloader mode?
Click to expand...
Click to collapse
Yep. otherwise, it just restarts; at least on mine.
jlip5617 said:
you all have been great so far!
Click to expand...
Click to collapse
Aw, shucks.
jlip5617 said:
wait, so you have flashed roms without changing anything in vista? i tried to flash the 6.1 stock sprint rom back in the day and it locked up my vogue. thats why i am very weary of even messin with vista. so should the phone be on or off when i attempt to put the phone in bootloader mode? aaaaaaaaaaaahhh!!! i would like to think i'm not a noob but everything i try to do is actin different than all other posts that are reporting. HELP PLEASE!!! you all have been great so far!
Click to expand...
Click to collapse
All I do is simply let WMDC recognize my phone & run the ROM Update Utility. It is either going to work or not. When your phone goes to the boot loader mode from running the Rom Update Utility WMDC disconnects & other drivers take over.
If you are that paranoid than flash your Rom via the SD card.
ok so i am gonna give up on flashing from vista i guess. i have attempted to flash from the sd card. i'm using a 512mb card that is formatted to FAT32. i have read that you can use imcokeman's unlocker to unlock through the sd card. have extracted the files and renamed the .nbh file to VOGUIMG.nbh and put the phone in bootloader. it is getting stuck at the grey loading screen. does anybody have suggestions for what to do now? has this happened to anybody else? PLEASE HELP!!
jlip5617 said:
ok so i am gonna give up on flashing from vista i guess. i have attempted to flash from the sd card. i'm using a 512mb card that is formatted to FAT32. i have read that you can use imcokeman's unlocker to unlock through the sd card. have extracted the files and renamed the .nbh file to VOGUIMG.nbh and put the phone in bootloader. it is getting stuck at the grey loading screen. does anybody have suggestions for what to do now? has this happened to anybody else? PLEASE HELP!!
Click to expand...
Click to collapse
I run Vista as well and always use the ROM Update Utility. It forces my phone into bootloader mode and everything else is pretty much automatic.
i have always flashed my phone from vista, never used any other version of windows, just started cooking my own roms a few weeks ago and no problem at all.
I'm on Win 7 Ultimate (Tech Beta tester, just got our copies on the 6th) and it works nice and smooth here.
I used to do some minor ROM work on my old i730 and i760 from Samsung under Vista though and it always went smooth.
Related
Hey guys I know this is not the unlocking thread but I tried posting on the thread made by "coke" with no response. So I thought I'd do it here. So here's the story
I have a Sprint Vogue and I was really getting tired of the slow HTC WM 6.1 and all the buttons that I could not modify on the cube (which is useless cuz I dont use any of the them). So I decided to try out a new rom with 6.1 and touchflo 2D.
I went to the ppcgeeks forum to unlock the phone, followed the instructions, read and reread the posts. Finally decided to give it a go. Everything went smoothly until the last step (exitbl) of coke 2.31. It kept telling me to disable USB on activesync and then the program would just shut down! ?? And yes I did disable the USB option for the activesync before that step. I looked under the device information and realized that nothing has changed interms of the ROM. So I tried it again and again (4 times). Then I just reinstalled the HTC 6.1 rom with the 3.42.30 radio... So any ideas on why this may be happening? I promise I followed all the steps
My second question is, in your opinions, what is the most reliable, stable and fast Touch 6.1 rom? Let me know if you have an opinion.
Thanks so much in advance, any help would be appreciated.
I had what sound like the same problem yesterday.
my post is over at ppcgeeks.
"I disconnected but I did not see the phone exit bootloader mode and reset itself.
....
What should I do from here?
Reboot phone, soft reset, hard reset? - go have fun?
....
I did a couple soft resets and have been playing around with it,
I guess I upgraded right... but it was weird there at the end, instructions not the clearest to me, i guess."
mine seems to be working fine, except the weather thing.
shows
in the About section my phone reads
WM 6.1 Pro
CE OS 5.2.21041
Device Information reads
ROM version 1.05.Alltel
Radio version 3.42.30
PRL Version 30008
PRI version 2.02_011
I was kinda scared to do another hard reset b/c I had already changed a bunch of settings.
Sorry if this doesn't help you too much,
but it is nice to know I'm not the only one with this issue
.
Hmm sounds like a similar problem. But I thought it wasn't unlocked unless we saw 2.31.coke somewhere in the device information.
As far as I know, hard reset did not hurt the phone. I tried installing that unlocker 4 times then went with the original HTC rom and it still turned out just like before. It installed the rom fine
Yeah I am still concerned about how it wont go through the exitbl step...
moonwoo said:
Hey guys I know this is not the unlocking thread but I tried posting on the thread made by "coke" with no response. So I thought I'd do it here. So here's the story
I have a Sprint Vogue and I was really getting tired of the slow HTC WM 6.1 and all the buttons that I could not modify on the cube (which is useless cuz I dont use any of the them). So I decided to try out a new rom with 6.1 and touchflo 2D.
I went to the ppcgeeks forum to unlock the phone, followed the instructions, read and reread the posts. Finally decided to give it a go. Everything went smoothly until the last step (exitbl) of coke 2.31. It kept telling me to disable USB on activesync and then the program would just shut down! ?? And yes I did disable the USB option for the activesync before that step. I looked under the device information and realized that nothing has changed interms of the ROM. So I tried it again and again (4 times). Then I just reinstalled the HTC 6.1 rom with the 3.42.30 radio... So any ideas on why this may be happening? I promise I followed all the steps
My second question is, in your opinions, what is the most reliable, stable and fast Touch 6.1 rom? Let me know if you have an opinion.
Thanks so much in advance, any help would be appreciated.
Click to expand...
Click to collapse
Yeah, the directions can be a bit confusing over there on that thread
Basically here are the steps
Download the 2.31 unlocker
Download the ROM you want to use (my personal preference is this one for a TF2D style or this one for a WinMO 6.5 style interface that has TF2D included to switch back and for - both very stable, fast and clean and the thread is very active for help (especially if your on Verizon or Bell which can have issues)
from there, use WinRAR to extract each file into separate folders
then Put your phone in bootloader mode (press and hold power+camera+stylus in reset until 3-color screen comes up)
At this point at the bottom of the screen it will say Serial, plug it into the USB cable or cradle and it should change to USB
Start the exe in the 2.31 and follow the directions (you may get some errors about sleep4.exe just click on OK as it keeps occuring its a XP/Windows7 64 bit issue if that is what your using)
At the point where it tell you to disconect, unplug the phone from the USB cable and wait (count to 10 or something) then plug it back in, it should have went from USB to SERIAL and now back to USB at that point go ahead and hit any key on your PC and it should continue along
once complete, reboot, allow it to do its thing then reboot and go back into bootloader again during reboot you should see coke 2.31 in the upper left if so your ready to go
plug it into your USB/Cradle again and then go into the ROM folder you extracted the ROM into
Once the screen on your phone says USB again go to the folder and double click on the RomUpdateUtility.exe file and follow the directions again, it may take some time so be paitent
once the phone flashes and reboots, let it run and do its thing to the and reboot itself then (and here is an important step for stability) once it starts up do a hard reset (red+green+stylus in reset hole) hit the enter button (center of D-Pad) it will reflash the phone and then red key (send) when prompted
then go thought the setup again, this time you can actually set things up as your keeping them this time and once things are done and your at the start screen on your phone power off (not reset) the phone and then start it up again - seems doing it this way takes care of alot of little issues that will come up before they can happen
Depending on your carrier be sure to have one of the DCD Carrier Cabs as well especially for the 6.5 ROM as it is a generic ROM and some have reported needing to run the DCD Carrier Cab for the service they use to get on the internet and use GPS and the like
Hope that clears up things a bit LOL
Detroit Doug
Doug, when I go into the bootloader it DOES say SPL-2.31.Coke. Does that mean that it is all set? Also this time, it still asked me to disable active sync at this time (at the exitbl step) do you have to run that step to complete the unlock?
This is what my bootloader image says
VOGU100 NFG
SPL-2.31.CoKe
CPLD-3
Let me know if I need to run the exitbl or if I am set to load the rom. Thanks so much for your help!
moonwoo said:
Doug, when I go into the bootloader it DOES say SPL-2.31.Coke. Does that mean that it is all set? Also this time, it still asked me to disable active sync at this time (at the exitbl step) do you have to run that step to complete the unlock?
This is what my bootloader image says
VOGU100 NFG
SPL-2.31.CoKe
CPLD-3
Let me know if I need to run the exitbl or if I am set to load the rom. Thanks so much for your help!
Click to expand...
Click to collapse
Your all set to flash if in bootloader it says as your phone does SPL-2.31.CoKe
you all unlocked and ready to go ... just put your phone in bootloader mode then connect the phone to your PC "serial" will change to "USB" and then run the RomUpdateUtility.exe file and follow along with the bouncing ball, do the watusi, wipe hands on pants - whatever helps you pass the time
but follow the steps as outlined above with the hard-resets and power-offs and the like, believe me its better to solve the issues before they occur than wait and have to start over
Detroit Doug
Doug, it worked like a charm. I did not know that the last step of the unlocker was not required. I installed 6.1 with Touchflo 2D. Looks and feels .. wow. it's the coolest thing I've seen. I've followed all your step including a hard reset before I started using it. So far the speed is impressive.
Couple more questions for you since you are an expert at this.
1. If I reload the factory default ROM, will it reset everything back to normal and can I keep reverting back and forth between different ROMs without any consequences?
2. It (the NFSFAN's 6.1 rom) seems to use less Storage memory (137 free vs HTC's ~100 free) but much more Program memory (59 free vs. ~80 in HTC's) than the HTC default. Any ideas or concerns about this?
All in all thanks so much! Hopefully as I learn more and more I will be able to contribute things too. You are right. This is so cool and highly addictive!!
Take care~ BTW I am in Lansing Go State!
moonwoo said:
Doug, it worked like a charm. I did not know that the last step of the unlocker was not required. I installed 6.1 with Touchflo 2D. Looks and feels .. wow. it's the coolest thing I've seen. I've followed all your step including a hard reset before I started using it. So far the speed is impressive.
Couple more questions for you since you are an expert at this.
1. If I reload the factory default ROM, will it reset everything back to normal and can I keep reverting back and forth between different ROMs without any consequences?
2. It (the NFSFAN's 6.1 rom) seems to use less Storage memory (137 free vs HTC's ~100 free) but much more Program memory (59 free vs. ~80 in HTC's) than the HTC default. Any ideas or concerns about this?
All in all thanks so much! Hopefully as I learn more and more I will be able to contribute things too. You are right. This is so cool and highly addictive!!
Take care~ BTW I am in Lansing Go State!
Click to expand...
Click to collapse
Glad it worked, and Ill try to answer you concerns
1 -Now that it is unlocked go ahead and swap ROMs all you want to, the tricky part is the stock ROM, flashing back to stock can and will revert your radio (if youve upgraded it) and ca cause issues with the unlocker, but a simple run of the unlocker 2.31 again can correct it
2 - NFSFAN like other Chefs have ways of moving data/programs around when they cook up these ROMs utilizing whatever kitchen program they personally prefer that being the case how they data/programs get pushed about can create the speediness you now see in your phone by freeing up the RAM for apps and the like and pushing programs off to the side optimizing how the device should have been setup from the start
As for that, Ive been using his ROMs as well as some others for quite some time and have had little to no issues with how he places the progs and data so I wouldnt worry about it
Yeah, Live in Las Vegas now - but Michigan will ALWAYS be home Go Red Wings !!!!
Detroit Doug
Thanks Doug, for all your information. Your answers were great! Hopefully I wont need too much more help in the future. i'm learning~
Don't mean to go off on a little tangent, but I find this post really helpful and was wondering if you, Doug, or someone else could provide a link to this 2.31 unlocker or whatever it is. Thanks in advance.
hibbiejibbie3 said:
Don't mean to go off on a little tangent, but I find this post really helpful and was wondering if you, Doug, or someone else could provide a link to this 2.31 unlocker or whatever it is. Thanks in advance.
Click to expand...
Click to collapse
http://forum.ppcgeeks.com/showthread.php?t=20370
Detroit Doug
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Reddog80p said:
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Click to expand...
Click to collapse
Check your PM over at PPCGeeks
Detroit Doug
Reddog80p said:
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Click to expand...
Click to collapse
From Detroit_Doug
At the point where it tell you to disconnect, unplug the phone from the USB cable and wait (count to 10 or something) then plug it back in, it should have went from USB to SERIAL and now back to USB at that point go ahead and hit any key on your PC and it should continue along
Maybe wait longer if you can,
I reckon some pc take longer to fully recognize[process] the disconnect and reconnect procedure.
example: disconnect > wait 20-30 seconds > reconnect > wait 20-30 seconds > then continue
I had that same issue and waiting longer during this process helped
.
I can't even get to that point. With active sync on as soon as I start the unlocker RUU it gets the info from my phone and shows the current rom 3.14.605.1 ....I click update and it shows 2.31 unlocker I hit next and then the install status bar comes up on my desktop and my phone goes into bootloader mode and the active sync connection drops and I get the 262 connection error. If I start the RUU with my phone in bootloader usb mode already it does not detect my current rom and I click next. click next to 2.31 unlocker, and it goes through the same steps and I get the same error. Is there anything I have to do to my phone prior to running the RUU. My phone is a verizon xv6900 running wm 6.1 rom 3.14.605.1 with radio 3.37.78
I have the same problem with my new sprint touch. I get error 262 at 0%, did they change something in these new phone that won't allow us to unlock?
Rom is 3.03.651.4
radio 3.42.30
I think I got it, what I did was not to extract the vogue_unlocker_MFG_2.31.exe file but to run it. I had activesync set up and connected, then just ran the unlocker, don't extract it. It will shut off activesnyc and put my phone in to the 3 color screen, form there, just follow the directions. Also I didn't have to run the exitbl step as my phone auttomatically exit and restarted.
I ended up having to re-run the .041 unlocker and then the 2.31 unlocker and it ended up working for me. I'm not sure why I had to because I Had the same bootloader info prior to running the 2.31 unlocker in the first place. The 6.5 rom and gps rom has been working flawlessly for a week now, the only thing I had to do was call up VZW (*8889) the guy answered "account investigations" LOL I told him I had to hard reset and my phone wouldn't authenticate and he asked me to call back from another line. I told him that I had no landline and he said thats fine I can override it just call back right away whenever you get to another phone. That was on friday and I have not called back but I've been able to text, make and receive calls so I don't think I will unless I have to.
gooney said:
I think I got it, what I did was not to extract the vogue_unlocker_MFG_2.31.exe file but to run it. I had activesync set up and connected, then just ran the unlocker, don't extract it. It will shut off activesnyc and put my phone in to the 3 color screen, form there, just follow the directions. Also I didn't have to run the exitbl step as my phone auttomatically exit and restarted.
Click to expand...
Click to collapse
thank you! i did that and it worked for me.
yeah, it says right in the directions over there to just run the exe it will create a temp folder and run the RUU itself from there
Extracting it and running it will always cause issues
also - Ignore the sleep4.exe or whatever if you encounter it - it is a legacy exe that is called that isnt used anymore, wont affect the unlocking just hit OK through it
Detroit Doug
Hi all, for all the people like me who do not have the patience or knowledge do adventure themselves in the mitty thread.
This program already exists for X1, HD2, TP2 (for what I know) and I have tested it and it works.
After some search on this forum I have talked to agent_47, who was kind enough to make a task29 program for our HTC Diamonds (GSM version).
Agent_47 or me do not take any responsibility for ay damage done to your device. Use it at your own risk, and only after you have HSPL already installed on your device.
Do not know what a HSPL is, check here:
http://forum.xda-developers.com/showthread.php?t=415191
agent_47 said:
it will flash radio 1.09.25.23
replace the radio if u want to use other version
Click to expand...
Click to collapse
agent_47 said:
now we can mtty our "HTC Diamond" without having the need of MTTY and its drivers
INSTRUCTIONS:
- download and unzip
- run then ROMUpdateUtility.exe and wait for it to finish.....
- device will reboot but will neva go past the bootscreen coz there is no OS to boot
- take our batti and then flash a rom using mSD card or by taking device into bootloader and using customRUU to load ur favorite ROM
DOWNLOAD:
http://rs604.rapidshare.com/files/407049148/task29-diamond.7z
WHATS TASK29\MTTY
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
but the thing is, mtty is and can be hard to use for new users. ... for me,, i was having the worst time installin the drivers needed to run mtty on win7 x64. so u i made this tool for me and for all
CREDIT:
all credit goes to doloop for coming up with the idea
Click to expand...
Click to collapse
and I would add to agent_47, as he adapted this tool for the HTC Diamond
Did anyone tried this?
What's the verdict?
mmm. interesting.
Thanks for the share and all your hard work but this is actually harder than mitty for me and i am a windows 7 user also
wapvirus said:
Thanks for the share and all your hard work but this is actually harder than mitty for me and i am a windows 7 user also
Click to expand...
Click to collapse
I do not understand how this is possible, I am using Vista and this is as easy as flashing a ROM with a computer. You just connect the device via USB to the Diamond, let active sync finish. Then you just need to run "ROMUpdateUtility.exe" and follow the instructions.
I have tested this, and I can confirm this is working for the European HTC Diamond (bought in Portugal).
This was not made by me, but I do think that more people will benefit with this program. Hopefully people will overcome the initial resistance to change.
Great idea!
I used to MTTY through VMWare Windows XP x86 within my host Windows 7 x64. It was a pain in the ass to get though but it always worked for me. This is a great time saver!
Regards to both of you Johev and agent_47!
Willing to test on my next flash.
Best regards,
Cina.
INSTRUCTIONS:
- take our batti and then flash a rom using mSD cardor by taking device into bootloader and using customRUU to load ur favorite ROM
Click to expand...
Click to collapse
What do you mean? take out battery?
Gonna try this with my next flash
Yeah, the sentence is a bit odd to me to
i asume it means take out battery but still..
i'm not gonna try it until i know it for sure!
--edit--
i couldn't help it and used it anyway..
i assumed "take our batti" means take out battery cuz it worked for me!
my diamond was clean (i guess) and i'm now enjoying a new rom!
Thanx guys!!
I would never post something that I did not test first.
I am glad that you liked it, and I really think it is much simpler then the mitty thread.
Good luck flashing.
rapidshare
first would like to give thanks for sharing this one but some people cannot use rapidshare links and unluckily I am those few
can you give alternative link like mediafire ????
character said:
first would like to give thanks for sharing this one but some people cannot use rapidshare links and unluckily I am those few
can you give alternative link like mediafire ????
Click to expand...
Click to collapse
http://www.mediafire.com/?jabdu2n968xa9uk here you are
I LOVE THIS TOOL
this isn't good for my ORD.. i'm flashing the hell out of my diamond now!
Getting a HD2 in about a month.. can't wait for it ;D
I tried it, but I only get the start screen with "Touch diamond", no bootloader.
But I´ve installed HARDSPL Olinex, because I already flashed other ROM´s.
How can I solve this problem?
What about battery? When I have to get it out, when I can put it in again...?
fibula
to get into bootloader you have to reset your device while holding the volume down button!
then you will get the tri-color screen,
connect your diamond to your pc and flash a rom with a RUU!
fibula said:
I tried it, but I only get the start screen with "Touch diamond", no bootloader.
But I´ve installed HARDSPL Olinex, because I already flashed other ROM´s.
How can I solve this problem?
What about battery? When I have to get it out, when I can put it in again...?
fibula
Click to expand...
Click to collapse
To get into bootloader with my diamond:
1) Turn Diamond off, take out battery for 5 seconds.
2) Put battery back inside, and press and hold the centre button (circle) and turn ON the device (hold both buttons) until you see a 3 colour screen
If step 2 does not work, try pressing holding volume down while turning the device on (hold the ON button too). Remember to take out the battery before you do this.
Hope this helps.
Hi!
Does this work by simply copying any ROM's nbh file (instead of radio*.nbg) to folder and executing ROMUpdateUtility.exe? Will it MTTY before flashing the ROM?
Currently I'm trying this method out. It is around at 50% of flashing progress.
I'll report back.
Cina.
thanks a ton dude.... magnificent work...
Now if there were only a way to do it directly from Internal Storage, without RUU...
It does not work the way I described. It hangs on HTC Diamond black boot screen and no red lines appears in lower right corner (no OS recognized).
So you have to flash 2 times. Radio flash is shorted for the first attempt and on the second turn you flash your ROM with CustomRUU.
There is a similiar tool like this with the method working with other devices I described above. FlashaholicRUU. Someone give it a try for Diamond. Next week I'll do it and report back.
Cheers,
Cina.
cina said:
It does not work the way I described. It hangs on HTC Diamond black boot screen and no red lines appears in lower right corner (no OS recognized).
So you have to flash 2 times. Radio flash is shorted for the first attempt and on the second turn you flash your ROM with CustomRUU.
There is a similiar tool like this with the method working with other devices I described above. FlashaholicRUU. Someone give it a try for Diamond. Next week I'll do it and report back.
Cheers,
Cina.
Click to expand...
Click to collapse
I remember to see that post on xda developers front page short time ago, but I was not sure if it would work for HTC Diamond.
A universal task29 that would format and flash the device in one single process.
Ironically it was developed a few weeks after I have found an alternative way to mitty that I posted here.
So far I did not hear that it was compatible with Diamond, so I will not risk it.
It's nice to have all these options, because when I searched for something like this a few months ago, I could only find the mitty threat that has more than 80 posts.
For me it was strange as newer devices with very similar hardware and software already had something like this, but Diamond users had to use mitty.
Well I am glad that you like it, and hopefully I helped someone that was not able or willing to do it manually.
I know I've seen a post simular to this but it's buried and what little was there did not help.
I have a Win 7 Home Premium 64-bit system, and tried installing the RUU that leaked Thursday. I installed the latest HTC Sync prior to running the RUU.
Made it as far as the screen on the phone going all black with chrome looking HTC logo, at which point the PC wanted to reboot and I got the error [170]. Per the instructions on the other post, I rebooted the PC and pulled the battery on the DInc.
Afterward, no amount of plugging, unplugging, running the RUU again, booting into hboot, booting into recovery, etc. would ever even get me back tot he black HTC screen. I just keep hitting the error [170] after the "verifying contents" file.
I managed to just power down the phone and turn it back on, despite seeing that scary looking screen with the Dinc under a big red ! icon, and it boots up like nothing ever happened.. all apps and contacts there.. etc.
Can someone PLEASE help me get this stinking RUU to install properly? Or failing that.. is there a way to put the contents into the internal memory of my phone and trick it into thinking it's recieved the OTA and I declined, so that I can install from the settings menu? Is it possible to even do that? If one of us gets the OTA, can we jack the OTA out of our internal storage and post it here to allow that to be done?
TIA..
NinjaRicky, UberNoob Extrordinaire
This sounds like the same stage I am at, but I am terrified to remove the battery for bricking my phone.
Right now I have the chrome htc screen when plugged in and the hboot ruu screen (mostly white with green text) when not.
My hboot ver is .79 and radio is 1.00.03.04.06. I also have the S-OFF.
What is the best way to return to the stock rom?
If you have S-Off, I'm guessing you have rooted your phone a little. I don't think security off is a default the RUU would have done.
I have zero experience with rooting, so I have no idea how to return you to stock. Honestly, unless you changed your radio version.. which it looks like you didn't.. you probably could run Unrevoked and Forever, then use one of the guides here to flash your ROM with the stock kernal. I'm sure I've seen a zip file of it floating around in the guides.
Hope that helps. I'm just going off what I've read. I think my problem is strictly because of the 64 bit Windows, but I'm hoping for a workaround.
Is your sdcard formatted to fat32
Sent from my ADR6300 using XDA App
jdkoreclipse said:
Is your sdcard formatted to fat32
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Not sure if you meant me or Rutledge, but no.. my card is FAT.. not FAT32. I'm about to reformat it now. How does that effect the RUU?
The hboot can only correctly read filed from q fat32 card
Sent from my ADR6300 using XDA App
I know I'm going to come off thick witted and slow for this.. but my question is about running the RUU from Windows 64-bit and getting an error [170] indicating that the computer thinks the USB cable isn't connected. I'm not trying to root my phone or install anything from the SD Card.. I wouldn't know what to do with hboot anyway.. I just put the phone in hboot mode and tried running the RUU again because I was grasping at straws.
What does the SD card have to do with the communication error I keep getting?
Use the extracted PB31IMG.zip from the ruu (tis can be found in the thread) and flash feom hboot....that is easier.,
Sent from my ADR6300 using XDA App
NinjaRicky said:
I know I'm going to come off thick witted and slow for this.. but my question is about running the RUU from Windows 64-bit and getting an error [170] indicating that the computer thinks the USB cable isn't connected. I'm not trying to root my phone or install anything from the SD Card.. I wouldn't know what to do with hboot anyway.. I just put the phone in hboot mode and tried running the RUU again because I was grasping at straws.
What does the SD card have to do with the communication error I keep getting?
Click to expand...
Click to collapse
I'm having the same error and found no way to fix it. I was forced to flash the update via my SD card. I had tried 3 computers with no luck ..
Really want to not root my phone yet.. I have a strong conviction I'd brick it. Just not confident yet.
NinjaRicky said:
Really want to not root my phone yet.. I have a strong conviction I'd brick it. Just not confident yet.
Click to expand...
Click to collapse
Just flashing the file from the RUU via your SD card does not require root since its signed by HTC. You do how ever must rename the file to PB31IMG.zip and make sure the card is formatted as FAT32
I did it with no issues but I wont recommend you to do it. I can recommend in this case just waiting the week or how ever long it takes for Verizon to push to the OTA to your phone then.
If you do want to see what I did just look for my question thread in this section called "[Q][RUU]extracting rom.zip file and flashing not rooted and s-on"
And this can be done with a stock DInc with factory defaults, such as S-On and all in place? No Unrevoked first?
Edit: Ignore the above. I R an idiot. Answered the question in your post. And ... it's updating right now witht he ROM.zip renamed. You are the man today, sir. I appreciate all the advice. boomertwo.. this bud's for you!
you need to have htc sync installed to run the RUU.
also your phone needs to be in HTC sync mode with usb debugging enabled.
i have 7x64.
k.electron said:
you need to have htc sync installed to run the RUU.
also your phone needs to be in HTC sync mode with usb debugging enabled.
i have 7x64.
Click to expand...
Click to collapse
That does work to get the phone into RUU mode but after that then the program lost connection to the phone completely. This was the wall I hit and found no way around it after trying it on 3 different machines. All running windows 7 but only 2 of them were 64 bit.
boomertwo said:
That does work to get the phone into RUU mode but after that then the program lost connection to the phone completely. This was the wall I hit and found no way around it after trying it on 3 different machines. All running windows 7 but only 2 of them were 64 bit.
Click to expand...
Click to collapse
I think someone mentioned that you could just let it do the usb error, the close the RUU and restart it and it should work from there.
hello everyone..
this morning I was intended to revert my kaiser back to WM 6.1,
I followed the instruction to put the ROM to my SD card along with KAISDIAG.nbh.
but maybe I chose a wrong rom, as the process goes, I just realize that the process was deleting my hard SPL..
now the text my 3 color display only says "SPL-1.56.0000"
but the android is still working....
so now my phone run on android without hard SPL...
could anyone help me? is it possible to install a hard SPL from android?
flashing from SD card doesn't works because I don't have any hard SPL installed..
There is no way at present to install hardspl from android, since we cannot run jumpspl, however you should still be able to flash a stock 6.1 rom using usb method.
Sent from my HTC Dream using Tapatalk
I have tried, but the process always failed with connection notification.It says that update utility cannot connect with my pda phone.
Well the problem is, flashing with usb method needs activesync connection with the computer. since microsoft activesync doesn't applicable anymore, I have no idea how to build connection with my phone. Besides, nothing seems happened every time I connect my phone with usb cable. Its just like my pc couldn't detect the device.
Should I install some kind of programs first on my pc? or am I miss some steps to make my phone detected by my computer?
I'm using windows xp by the way..
The CustomRUU still works for me if you boot the phone into SPL first (reset and camera+power buttons) then plug it into the computer and run the RUU (no activesync connection), so you should be able to flash a WM ROM, then you can sort out the HardSPL later
EDIT: Or does that only work for me because I have already got HardSPL?
yes it works..
the process goes, but only for 1 % . my phone reset itself and the notification on my pc says about invalid vender ID "this update utility cannot be used for your PDA phone, please check your update utility."
since the only stock rom that I found is .exe which is extract itself, I couldn't use The CustomRUU. Could this be the problem? or do I choose a wrong rom?
edit : I'm trying to install Factory Shipped ROM form HTC
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship
Do you know where to find stock rom for kaiser? most of the post about stock rom leads me to wiki xda, which is not available anymore.
thanks.
Not sure if these will work, but there are links to original HTC and ATT ROMs here
Also at the bottom of that post is a link to some reconstructed original ROMs
I have no idea if these will work any better than the one you've already tried, but it's probably worth having a go
thanks for the link..
I have visited that thread before, actually the 1st ROM that I tried to flash is also from that page. Both original ROMs for HTCor ATT doesn't works for my phone. But thanks to you I just realize the link about some reconstructed original ROMs.
Well, My phone is KAIS-100 which is made in Taiwan.
I guess I'll try Chinesse HTC 1.56.708.3.
I hope this one will make a progress.
-----------------------------------------
aww... still not working..
with reconstructed ROM, the process stuck at 0%, give me error [262] notification : update error. The manual said that if this kind of error occurred, I just need to do soft reset and run RUU again. I have tried several times even restart my pc first, but still not working.. any suggestion?
Try to flash radio. If you can't do it i think that you have messed up the bootloader
I can't...
the result is same, I'm trying to flash KAIS_Radinly_1701909 or KAIS_RADIO_ONLY_1710901_Custom, I got stuck in 0% with error [262]
The text in my bootloader says
KAIS-100
SPL-1.56.0000
CPLD-8
So, is there nothing else I could do if I have broke my bootloader?
No one can help me anymore? T-T
(running to the middle of the street and shout "why God, why??")
So, the lesson is :
If you are trying to flash back to windows mobile, DO NOT use factory shipped rom. Because it will modify your hard SPL and downgrade your radio version.
If the process failed and your hard SPL gone, you will get stuck in half working android without being able to flash anything, including correct your radio version, or reflash your kernel to fix your panel setting.
correct me if I'm wrong..
well, I hope my experience could be useful for you.
Thanks.
You can extract the exe file with winrar and you'll have all the files including RUU_signed.nbh
Rename it to kaisimg.nbh and copy to sdcard
Don't know if you can install from sdcard but since it's the shipped rom it might let you.
thank you salac..
I also have tried that method, using winrar to extract exe files.
but still, no luck for me..
Flashing via SD card got me stuck at loading screen, and I also tried to use custom RUU to flash the files via usb but my phone reset itself at 1% of the process and gives me error message [294] : invalid vender ID.
SOLVED
Finally
after days of yearning..
I found a suitable WM 6.1 ROM for my kaiser.
My phone is KAIS 100 HTC P4551. Usually, KAIS 100 model is for AT&T but mine is HTC branded, so that's why AT&T stock ROM won't works and my phone was originally shipped for US, that's why most of WWE stock ROMs always give me error 294.
So, basically I have to use HTC WWE ROM for US and this is really gives me hard time since HTC US website only provide ROM for AT&T.
In case you have same problem with me, I have uploaded the ROM at rapidshare
and you could find it here.
Now, I can flash a hardSPL, fix my radio version....
and flash back to android..
ok so heres what happened. forgot my phone was rooted. i tried tmobile ota update. kicked me out into twrp. i messed aroun and bascily now i have no os or anything. i accidentally formatted everything in the phone. its the white 32gb tmobile version if that matters. to make things worse, i use ubuntu 14.04 LTS. no windows. cant even figure out how to get windows on the pc. and no i cant go buy it. noodle budget. i also messed with the fat32 thing and it said unable to make fat32 partition. basicly. its screwed. i need to know what to do about this. i have the lg flash tool, the original .dll and .tot ready to go. but theres the linux thing. everytime i try to connect it to the computer in download mode it said could not mount adroid device or something like that, now it wont even come on for me. i dont know what to do about this. no i couldnt get adb sideload to start, i couldnt mount in download mode, i could get adb to recognise the device but thats about it. i pushed a couple roms to it but nadda. after installing succesfully it just went right back to twrp. i need a video or something that i can slightly understand on how to fix this.
Your best bet is to set up a virtual box and virtualize it. I guess in twrp if you can still get access to it. Is to wipe system and all that fun stuff so it can reformat it to ext4 then try to adb sideload the rom that matches the update as close as possible. The only thing I can think of is that the update messed up partitions so when you flash a rom it can't all fit like it used too.
Sorry if I didnt help I'm just trying my method I had to do when I had my g2
Sent from my HTC One_M8 using XDA Free mobile app
NexusBarry said:
ok so heres what happened. forgot my phone was rooted. i tried tmobile ota update. kicked me out into twrp. i messed aroun and bascily now i have no os or anything. i accidentally formatted everything in the phone. its the white 32gb tmobile version if that matters. to make things worse, i use ubuntu 14.04 LTS. no windows. cant even figure out how to get windows on the pc. and no i cant go buy it. noodle budget. i also messed with the fat32 thing and it said unable to make fat32 partition. basicly. its screwed. i need to know what to do about this. i have the lg flash tool, the original .dll and .tot ready to go. but theres the linux thing. everytime i try to connect it to the computer in download mode it said could not mount adroid device or something like that, now it wont even come on for me. i dont know what to do about this. no i couldnt get adb sideload to start, i couldnt mount in download mode, i could get adb to recognise the device but thats about it. i pushed a couple roms to it but nadda. after installing succesfully it just went right back to twrp. i need a video or something that i can slightly understand on how to fix this.
Click to expand...
Click to collapse
Same situation happen to me, Im praying for someone to give me debrick.img so I can boot this G3 . This SD Card method but we need a working LG G3 that can give us that debrick file
http://forum.xda-developers.com/showthread.php?t=2660566
help fast!
xmagiicsx said:
Same situation happen to me, Im praying for someone to give me debrick.img so I can boot this G3 . This SD Card method but we need a working LG G3 that can give us that debrick file
http://forum.xda-developers.com/showthread.php?t=2660566
Click to expand...
Click to collapse
i dont have any windows keys nor any way to get it. so can u explain have to use virtual box to do that?
Just download a Windows img either that or use wine to emulate Windows apps on Ubuntu is a secondary option
Sent from my HTC One_M8 using XDA Free mobile app
This is my situation as well. No OS. Can't get a ROM to flash successfully via SD card. Bumping this thread for some serious assistance. What do we do?
weekendbiggs said:
This is my situation as well. No OS. Can't get a ROM to flash successfully via SD card. Bumping this thread for some serious assistance. What do we do?
Click to expand...
Click to collapse
Did you read the suggestions that were given in the thread?
doktor buknasty said:
Did you read the suggestions that were given in the thread?
Click to expand...
Click to collapse
you should be able to download a windows 7 and use for 30 days for free. after 30 days, you still can extend it to another 30 days. that should be enough to get you phone back
Wow... reading OP was like a mirror into my own experience except I am on W81 I have tried in every way imaginable to fix this issue with LG Flashtool and it constantly tells me that it can't boot into download mode even though it is already set into it. What other options are there to fix things? I am at wits end..
nekoarashi said:
Wow... reading OP was like a mirror into my own experience except I am on W81 I have tried in every way imaginable to fix this issue with LG Flashtool and it constantly tells me that it can't boot into download mode even though it is already set into it. What other options are there to fix things? I am at wits end..
Click to expand...
Click to collapse
You must have Windows Virtual Box if running Linux, Ubuntu, Solaris, or Mac. Start HERE. It can be tricky for some, you may want to read this whole page before attempting.
sent from my LG G3
joeyhdownsouth said:
You must have Windows Virtual Box if running Linux, Ubuntu, Solaris, or Mac. Start HERE. It can be tricky for some, you may want to read this whole page before attempting.
sent from my LG G3
Click to expand...
Click to collapse
I don't need a VM I have windows 8.1 installed native on my PC.
nekoarashi said:
I don't need a VM I have windows 8.1 installed native on my PC.
Click to expand...
Click to collapse
I misread, sounds like driver issue, have you tried to see if phone is recognized in ADB?
sent from my LG G3