Okay, Im new to the site as a registered user, but have been looking around in the forums and reading posts and what not, but Im having troubles finding the answers to my questions. There are soo many topics, soo many rreplies, soo many of the same questions and answers in different topics/posts. So these are my questions and Id really like someone to help me out. Im having troubles with my Touch Pro 2 for Verizon. Im currently running windows mobile 6.5.
Question 1: Do I need to downgrade to windows 6.1 to get Android to work?
Question 2: Are there specific installation instructions that I can follow for this device.
Question 3: Does the service provider matter when installing Android?
( I had a few more questions, however, I have a forgetful memory and if they come up, I will write them down and post more questions)
-- right now, it reboots itself when I get online or open an application.
-- Also it is saying that the Facebook for Android app isnt working because it wasnt signed correctly or something to that effect.
-- When it restarts, it will not let me run the dual boot (Gen Y DualBoot) and says "an error occurred on sub_main_androidexistcheck. An error occurred retrieving the registry key"
-- Every once in awhile it will pop up with a message when I try going into an application. Again, I will write down the message and get back to this post.)
-- Oh, and I installed XDAndroid just recently, its the one Im currently having issues with, but Im not sure which Android I was running before, but it was the one that would pop up with different phones and the Android dude when I would start up Android.
Please, can someone help me out with this? I would really appreciate it. Thank you to whoever replies to this post.
I don't believe it should matter between 6.1 and 6.5, haret simply kicks WinMo out of the active memory and runs Android. Install should be the same across the board for all TP2s, format your SD card, get the latest Cab from the sticky at the top of this sub-forum, and install the CAB to your SD. Most errors in Android are repaired with a format of your card.
Related
i have a custom rom with a 3.42 radio and wm 6.1
if i upgrade my phone to windows mobile 6.5 will i still have my custom rom or would it be all new just like when you flash a new rom?
jljohnson919 said:
i have a custom rom with a 3.42 radio and wm 6.1
if i upgrade my phone to windows mobile 6.5 will i still have my custom rom or would it be all new just like when you flash a new rom?
Click to expand...
Click to collapse
The only way you would be able to upgrade to WinMO 6.5 would be to flash the phone just like when you flash a custom ROM now
WinMO 6.5 is not an installable app/upgrade like upgrading an application on your phone its the operating system itself
Right now and there are very few ROMS out there for WinMO 6.5 and none for the Vogue at all (Im assuming you have a Vogue as this is where you posted) soon there will be one as there are people working on it currently but what is there is EXTREMELY buggy and almost non-functional for the fact its on a phone and a phone should be able to be used after all LOL
Keep with the Custom ROMS for now and wait, the desire for it has been spoken and the Chefs are a cookin LOL
Detroit Doug
NFSFan has confirmed that those WM 6.5 ROMS are FAKE. Even if they were real, there would be no point of using them...
The builds are fake indeed. However they do contain a few components of 6.5. None which are worth upgrading for.
NFSFAN said:
The builds are fake indeed. However they do contain a few components of 6.5. None which are worth upgrading for.
Click to expand...
Click to collapse
Really? What components do they have? Anything from a new today screen or Internet Explorer (like rumored)?
Kinetic scroll (give up TouchFLO and Manila2D), new IE build that supports kinetic scroll. The today screens being posted are fake. They are actually from a smartphone, called HTC Juno. Some asian dude took it out of the Juno, resized the images, and re-arranged the tabs to make it look like the new today screen.
flashing on Vouge
I know this may sound tedious but i have no idea on how to flash any ROM onto my Vouge. Can someone please help. I would love to try out several ROMs and see which one would work best for me.
Thanks in advance
Hey, here is one really good one
Detroit_Doug said:
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
Detroit Doug
Click to expand...
Click to collapse
thanks
Everything is working smoothly and better than I thought it would have (i flashed the 6.5 ROM). Thanks to you Detroit Doug or I don't think I would have been able to do it without your instructions. I however do have one more question....i'm having issues syncing the device with my PC now. Any idea on what that could be???
re: Thanks
I've done several resets but to no avail am i able to connect via active sync???
OK maybe i lied about everything working properly and wonderful....so on top of not being able to connect to my PC via activesync I also am not able to connect to the internet on my device, i've downloaded and installed the NFSFAN Sprint GPS Registry but still its a no go... Did i do something wrong completely????? still
I fixed the internet problem!!!!!!!!!!!!!!!!!!!!
....somehow magically i'm now able to connect via activesync. I guess the device just needed time to adjust. Thanks for the help, and i do apologize for the numerous newbie questions.
ehepps said:
....somehow magically i'm now able to connect via activesync. I guess the device just needed time to adjust. Thanks for the help, and i do apologize for the numerous newbie questions.
Click to expand...
Click to collapse
ok so i didnt notice this thread. so whats your secret? howd you get it to work?
mbaseball, I just replied to your thread.
MMS
I flashed the rom perfectly and im lovin every thing bout it but one thing, i cant send or recieve picture mail. Is there a way 2 fix that or sumthin. That takes alot of funny away from the rom. help me please. does there happen to be a 6.5 rom wit picture mail?
Best Windows Mobile 6.5 upgrade for Vogue (Bell)?
hi
I 've been reading this thread, and am just wondering whats' the best download so far for upgrading to Windows Mobile 6.5, for HTC Touch - I think this is the vogue...for Bell Mobility?
If you could please provide a download link.
Thank you all for your help
Thank you
Karim
kchaggani said:
hi
I 've been reading this thread, and am just wondering whats' the best download so far for upgrading to Windows Mobile 6.5, for HTC Touch - I think this is the vogue...for Bell Mobility?
If you could please provide a download link.
Thank you all for your help
Thank you
Karim
Click to expand...
Click to collapse
The best is NFSFAN's Windows Mobile 6.5 ROM. You can find it on another thread in this forum right here:
http://forum.xda-developers.com/showthread.php?t=432487
Don’t even bother with anything else. I am running this. It is fast, stable and very close to the stock WM 6.5 (I have downloaded the device emulator image from Microsoft’s website for software development purposes). The extras that are in there are useful.
The Fish
Help Help, please, I need your help please,
I am really new to this forum. I have been reading a long time the forum, and see evolution of cooked rom. I love the Tomal version 8.2 19960 that was on my Jasjar Imate. When I try to put the Vanillla version 8.2 I think that I mismatch myself, and unfortunately I should get back when I saw the error code 120. What I did, I say yes, and now have a blank screen. Nothing happens. Badly again,again, I have seen before this message USB on top and 2.01 on the bottom, but after I pull out the battery and change for another, I cannot connect anymore the device to the computer. It gives me this message <USB device not recognized> or < Windows cannot recognize a device attaching to you computer>. I kept trying all times, and now that this message, I have on my computer.
I think I did break my device myself, or I have all my stuffs in it, my passwords, my agendas, my contacts and so on.
Howw can anybody help me get out of this mess and recover my device. Please, I need help. Your help please.
Gerard
Universal Imate JasJar broke after error code 120 - Message USB Device not recognize
Thanks to post already done in this forum. I searched and brwosed all <USB not recognized> installed many utilities but without success. Finally, I discover the post < Instructions for those stuck on Boot Screen (UNI_exitbootloader> in wiki.xda-developers.com and I get results, my device has been come to life again, it was RESURRECTED.
I follow exactly, that the solutions, I tried before, but in panic and in a hurry you could miss to steps and to pay attention to the instructions, but I retry again and again and finally it did work. And I put the Tomal 8.2 19960 again on my Imate jasJar and bingo, it works.
For sure, I have not seen the blue screen <clubimate> again, but a black screen, and at the bottom te version 1.15 radio, 8.2 TML and so on, but it doesn't matter, I am so glad to see all the functions come again to life, and put my sbp backup and bingo, I do have all my data and software back, as I take precautions allways to make a backup two days ago with sbp.
MANY THANKS TO XDA-DEVELOPERS; TO XDA DEVOPERS WIKI, AND TO THE PERSONS OR THE TEAM THAT FOCUS ON ANSWERS TO HELP PEOPLE LIKE ME AND OTHERS get out freely and sincerely to theirs problems.
I hope this post will help others to keep visiting and searching xda-developers for solutions of their device needs.
All the best
Hi folks, how is every one?
I have been tinkering with the Polymod Eclair on my Kaiser (running via the SD card).
I have it all running but I have a few questions.
1. If I allow my phone to go in to standby/sleepmode when I press the power button to get the screen up again all I get is a screen full of vertical green lines (with a few other colours here and there) and my phone does not respond. I have to reboot the phone to be able to do anything with it.
Any Ideas as to a solution?
2. When I go into the settings for the mobile networks it doesn't come up with my one (Three (3) or Hutchinson Mobile if you prefer).
is this something to to with it being a 3G service or something?
3. How do I get the screen lock working on Android (if there is one), I cant sem to find it?
4. Should I be able to turn the screen of like you can in Windows CE?
Hope I haven't bombarded and bored you to much with my many questions.
Thank you as always for your hard work.
Steve
You can find the answers to all these questions by searching the polymod thread. Please do not start a new thread for an existing topic.
Don't forget to read the FAQ and Tutorials, I have linked to all of them so you wouldn't have to ask.
Thanks for trying my build!
MODERATORS, you are free to close this thread.
polyrhythmic
I haven't been able to unlock my touch. I am using 2.31 unlocker, I run the RUU.exe and get up to the point where the phone shows the gray screen with the %bar. But it stays at 0% and after a few minutes a get Error 262.
I have already re-flashed to my stock ROM, but same results.
Touch (Sprint)
ROM: 3.03.651.4
Radio: 3.42.30
WinMo 6.1
Update:
I have tried on Windows 7 Pro 32-bit, and on Windows XP Pro 32-bit. Same results....
Try this...
I'm sure the thread will be locked and you'll be told to ask in the FAQ's thread or something, but I hate when that's the only thing you get... not helpful enough! So maybe I can sneak in before the lock.
I had this problem a week ago, and for whatever reason, the only thing that worked for me was: 1st, flashing to the latest stock ROM (which you already have), then turning on the phone and letting it connect to Windows Mobile Device Center (Win7) or ActiveSync (WinXP) (do the whole 'connect without configuring device thing) then run the actual unlocker BAT file (Vogue_unlocker.bat) in the 2.31 unlocker.
Trying to manually run the EXE didn't want to work - letting the BAT file do it's thing through activesync actually worked for me.
Maybe it'll help... I hope so! Good luck!
NuAngel
NuAngel said:
I'm sure the thread will be locked and you'll be told to ask in the FAQ's thread or something, but I hate when that's the only thing you get... not helpful enough! So maybe I can sneak in before the lock.
I had this problem a week ago, and for whatever reason, the only thing that worked for me was: 1st, flashing to the latest stock ROM (which you already have), then turning on the phone and letting it connect to Windows Mobile Device Center (Win7) or ActiveSync (WinXP) (do the whole 'connect without configuring device thing) then run the actual unlocker BAT file (Vogue_unlocker.bat) in the 2.31 unlocker.
Trying to manually run the EXE didn't want to work - letting the BAT file do it's thing through activesync actually worked for me.
Maybe it'll help... I hope so! Good luck!
NuAngel
Click to expand...
Click to collapse
Oh come on Nu!
Unlike most other mods, I don't simply lock the thread. I lock it and/or transfer it to the Q&A thread where I answer the question myself. Please don't say these things. I try to keep the Vogue apart from the usual MO in several other fora.
I do it for 2 reasons:
a. To keep clutter to a minimum
b. To have a nice db with solutions to many issues that people may have with their Vogues. Trust me that the Search Engine of this site works much better when you look through a single thread than when you look for threads.
@caquito07,
I am transferring your question over to the Flashing Guide Sticky thread. Please follow up over there.
@Nu,
One last thing... thanks for stepping in
Thread closed.
Hopefully I got this in the right spot, if not I am sorry:
T-Mobile htc Touch Pro 2 (GSM) RHOD 210
-windows xp pro service pack 3, fully updated .netframework
-DEP disabled
-full security allowed on both phone and pc
-unlocker fails at step 1 with fatal error (only installs enablerapi.cab)
-hardspl fails even with the manual option (1st part installed to phone then run manual from pc side) it just stays at the loading bar
-have tried 6.1 t-mobile stock rom and 6.5 stock rom (at this point can only flash stock roms)
-ran everything with admin privilleges
-firewall disabled
-anti-virus software completely removed from pc
-re-booted phone and pc numerous times
-also tried it on Windows 7
-activesync fast file transfer turned off
Totally out of idea, have seen in the forums other users with the T-Mobile touch pro 2 rhod 210 with same issue's but no-one has posted how to "fix"
or do it, closest post was: NVM got it, well how about telling other what you did to get it to work?????
This is my fourth time unlocking a touch pro 2 and 5th time just flashing the hradspl/custom rom.....so I am not a total noob....
p.s. also tried to manually enter bootloader mode to do it.......and a laundry list of other things (spent almost 2 days reading the forums and help sections)
Has the phone had hSPL done before? Was it a refurbished/insurance replacement device?
If the device has already had hSPL done, you cannot do it again... You can try to contact the developers, but it seems most attempts from others have fallen on deaf ears.
no it is still the stock spl, when I put it into bootloader it is spl-0.87.000 which is the stock one, and cooked roms will not load, another indication it is not hardspl'ed and the unlocker fatal errors after the enablerapi is installed on step one, also tried SOTI and re-wrote my phones security sectors in xml to accept any data input (unsigned or not) I can run and install anything but the hardspl and the unlocker program, have flashed different stock t-mobile roms hoping it was a incompatibility issue with a stock rom but still no happy ending.
But thank you for at least responding and acknowledging my pain
I GOT IT!!!!!!!!!! I GOT IT!!!!!!!!!!!!! I GOT MY HAPPY ENDING!!!!!!!!!! After going thru 2 different os's I got it to work on a reworked windows 7 platform, something in the XP PRO and Windows 7 stock os was not letting me run the unlocker or hardspl!!!!!!! Ended up using Windows 7 shine edition........many thanks to the guy who created it..............AND EVEN MORE THANKS (sorry if I spelled it wrong) OLIPRO !!!!!!!!!!!!! Your patience will not be forgotten!!!!!!!!! Still not sure what was causing the error's on the stock os's but if anyone else is having issue's with T-Mobile Touch Pro 2 I recommend using the windows 7 shine edition.........once again huge thanks to olipro and the team keep up the good work peoples!!!!!!!!!!!!!