Develop Bugs

Updating JASJAR

Hi all,
I have been trying to check out the forum here, to try and solve my problem, I literally bought my JASJAR today, and it was giving some wierd behaviour. In an attempt to reload the software (I prefere to reload the entire ROM), something went wrong, now all thats on my screen is "USB" and a lil lower down "v1.01".
ActiveSync obviously not connecting now bcos the OS is not on the JASJAR no more, in my device manager is a "Microsoft USB Sync" under my mobile devices.
I downloaded what I am guessing is WM6, 'JASJAR_WWE_20106_20301_11300_wwe_ship' from another thread in this forum, tried to load that but cant communicate with device cos no activesync.
I have tried the different reset options, like the 2 function keys and the reset on the back, I push 0 to clear, and then it jus goes back to the USB v1.01 thing.
I am running windows vista home basic, with the Windows Mobile Device Center, it synced perfectly with this software, communicated properly with the update tool, until my device reset and activsync lost connection, then i was stuffed.
Any help will be appreciated.
Thanks in advance.

Sounds like it is your first time with the upgrade. What you are seeing on the screen is the bootloader, which is what we use for flashing new ROMs.
ActiveSync or Windows Mobile Device Center (how come you have both on Vista?) will therefore not respond. This is fine, because we use a different program to load the new ROMs.
If you look at the folder you downloaded, chances are that there should be a program called "ROMUpgradeUt" or something similar. Provided that you have not changed anything in the folder, you should be able to flash the new ROM by simply following the instructions in the program.
You can also read this link for more information: http://wiki.xda-developers.com/index.php?pagename=HTC_Universal

Here is an instruction guide on ROM upgrading: http://forum.xda-developers.com/showthread.php?t=269118

how come you have both on Vista?
Sorry, I don't mean to sound like I have both, I recently moved to Vista, and am used to calling it activesync and not WMDC.
Thanks, will have a look

Ok, well I have got it up and running again, only problem now is activsync keeps freezing when I try and sync the device...any ideas?
I landed up using my work computer, which has XP on it, and then used MTTY and that connected fine, on Vista it simply didnt wanna work.
I ran the utility for those 'stuck on serial/usb', and that fixed it. Now I would like to load up WM6, but it keeps getting communication failures.

Thanks for the help guys....I got it working...running on WM6 now...whoo!!

Sync Issues on Vista x64 after Dopod 810 WM6 upgrade

hi all,
been searching around for any clues to this but not having any luck.
Prior to doing upgrade I had been using the device successfully on my vista x64 machine.
Successfully performed an upgrade of my device using my XP machine.
Upgraded Windows Mobile Device Center 64 bit edition to 6.1 release on my main PC.
Now, when I connect the phone to the vista pc, i get the customary sound on connection, but device center does not show it as connected. When I check device mgr, I dont see the normal HTC USB Sync item that I did before.
I tried changing the PC to USB setting on the phone and reconnecting, but then PC reports unrecognised device as being connected.
I have tried connecting to different USB ports on the PC with no luck.
Any suggestions appreciated!
Thanks

hey, sorry i don't think i have any solutions for you on this.. but just to make sure, i'm assuming you re-enabled usb connections after you upgraded under vista?
on a side note dutchiesmokah has been having trouble upgrading under vista x64 as posted in this thread, and i'm also very curious how to help him overcome this obstacle. I believe he's stuck at disabling driver signing. Do you think you could have a look over there, and report on what you did etc, to get it working?

hi racerx_
actually, I did my upgrade on a windows xp machine running activesync 4.5 specifically because of that thread. Because of that I never had to go thru the re-enable procedure, as I never disabled it. I merely upgraded the version of Mobile Device Center to 6.1 as I new that was required to support WM6.
I had something similar to my problem happen once before on early version of MDC and WM5, but somehow came good after multiple disconnect/re-connect attempts.
Sent a request to Dopod Asia support a week ago and have not had a response yet.

oooOOOOooohh.. i see what you're saying. Sorry, i didn't read your first post carefully enough. That is weird that it won't sync. I've posted about some weird sync issues as well.. not sure if it's related, but..
under xp my device suddenly stopped syncing and would report an error each time, although it made the connection sound, and activesync turns green so it knew my device was there. It would come and go. I deleted both activesync partnerships on my device (not computer) and magically it's working.. it may not have anything to do with your issue, but just thought i'd share in case it helps out
on a side note, that other thread regarding vista upgrading is moving pretty slow. You think you could be convinced to be a guinea pig and try some of those methods for upgrading under visa and report on what works?

crashed/frozen. wont boot (FInixNOver) - cant reflash!

Hi guys.
I was using the installed the FInixNOver 3.0.1 ROM onto my SPV M700 and it was great. I've had it for about 2 weeks without any problems.
Last night I looked at my phone, only to realise that it was completley dead. This didnt shock me to much because the battery was running low, and i decided to let it die completley before recharging it again.
I charged my phone overnight and switched it on this morning, but the phone would freeze at the 'FInixNOver' splash screen (the numbers at the bottom of the screen would appear overlaying the splash, but the phone wouldnt go pass this point).
The only way to turn off the phone from this state is to eject the battery. I have tried removing the sim card, turning it back on in as many ways as possible but to no avail. I am able to get to the TriColor test screen (im running IPL-0.50 / SPL-1.30.Olipro) but with all the custom roms available, they all use the ROMUpdateUtility which requires the phone to have established an activesync connection initially (but this would mean my phone would have to be 'on completley' - so this is catch 22.)
For the record, my phone/battery died while my wired handsfree was attached (dunno if thats of any interest to anyone or the rom baker).
But it looks like the only way i'll be able to flash my phone is by finding a way to install the .nbh file without using the RUU method. Because I can put my phone into test mode manually.... any help or guidence would be very much appriciated.
Thanks.

Ok can you get it into bootloader? power/camera buttons and reset?
sorry didnt read fully.
right get your device into bootloader first,
then open active sync (are you using xp)
then open connection settings and disable usb connection,
put your device into bootloader mode, then run any rom upgrade, i prefer the WM6.1 pdaviets from HERE (Username: PDAVIET / Password: pdaviet)

Your pda does not need active sync with ruu's, so no catch 22. if you turn off usb connection in active sync, you can still run ruu and it will be recognised, unless you are using vista, where you need to change your HTC SYNC drivers.

Thanks for your quick response...
Yes I can get into boot loader using the power and camera buttons (or holding the power and camera buttons when resetting the phone)...
When the phone is in boot loader mode, active sync doesnt even detect the phone anyway, but nevertheless, I have followed your instructions and disabled the USB Connection. (BTW, yes i am using XP)
The phone is still in boot loader mode, so now i try and execute the ROMUpdateUtility.exe and go through the steps, at the 1st step i tick the tickbox and click next, and the 2nd step i tick the tickbox and click next. (this step says DO NOT enter the bootloader manually? - but i have havent i?) anyway, when i click next, it says... "Verifying the information on your Trinity... Please Wait..." for about 10 seconds, and then i get a message "ERROR [260] : CONNECTION"
What am i doing wrong?

Huumm.. why dont you flash your phone throw the sd card??
Read this link:
http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing

try to flash your phone with some official rom and after that flash it with any other you want!

manos_23 said:
try to flash your phone with some official rom and after that flash it with any other you want!
Click to expand...
Click to collapse
I would recommend this option above, to be safe, i usually get them error messages when the battery is below 50% or sometimes i try it again and it works. it does state do not manually enter bootloader but i always do it this way.

also make sure active sync is not still running in taskmanager under the alais: wcescomm.exe and WCESMGR.exe, end them both.

I've just tried using an official ROM, but the problem still occurs with the 'connecting'. It doesnt seem that the computer picks up a connection to the phone whatsoever.
Should i be concerned that at the bottom of the bootloader screen it says "serial", is this correct?
Im starting to get annoyed now.

Bye,
the bottom of the sreen mast say "usb" not serial.

it seems there is a problem, if it states serial. as it should say usb. try THIS

Seems like the problem was that my USB lead was loose and made a bad connection, hence why the bootloader showed 'serial' and not 'usb'... as soon as i wiggled it and heard the 'connection noise' in windows, i knew i was good to go, and so using the RUU worked fine to reupdate my phones ROM.
Thanks for your help.
My only question is that why did it happen in the first plave?

WIZZKID - I just saw your post here now. I have to tell you that I also saw "SERIAL" at the bottom of the bootloader screen and not "USB". As I said I returned it to get another phone but maybe I will try something else for now instead of a P3600i. I will monitor your thread to see how it turns out for your phone, because it seems that we have the same problem.

if you see "serial" instead "usb" your problem is in the usb cable, usb port from your computer or in the usb connector from your trinity!!!!!
I was having the same problem that you have!! my problem was from my usb from mine trinity!! see if the conector is at good conditions !!!

Well as some of you may know, I got my Trinity replaced for sticking at the WM splash screen after a few days. This second one - I have had it ONE night - and the same thing has happened with incomplete booting. This time I have been trying all night to flash the phone to an official ROM, but I cannot do it (apparently) because I can't establish a connection via ActiveSync. When I stick the data cable in while in bootloader I see SERIAL replaced by USB and when I try the flash I get a "270" error (cannot connect to phone) and the phone re-boots to the sticking plash screen. What should I do now?

ladies and gentlemen...
we've got a lot of mixed messages in this thread.. please make sure you're posting the right thing. no need to disable USB when manually going in to bootloader to flash (at least in xp).. Also, you can ignore the part of the RUU that says 'do not manually enter bootloader' (you should really read the guide on my site)
foxuniform- can you please give some details..
1) are you running xp or vista
2) have you flashed hard-spl? if so what version?
in the mean time, try a couple of things.. first, flash hard-spl (even if you already have it, but from the sound of it i think you don't have it on your device).. if that works, try to flash an official ROM. Can also try to use splxploit, then flash hard-spl, and then flash official ROM (there's a guide on my site if you're unsure)
please post your results
*edit*
here are the steps for SD card upgrade, but i HIGHLY recommend flashing Hard-spl first..
try to do it from SD card. how?
Extract the .NBH file from your prefered ROM upgrade: In windows use winrar (right click) to extract the contents of the exe file. In Linux / MacOS use cabextract (http://www.cabextract.org.uk/) .
Rename the .NBH file to TRINIMG.nbh and copy it to the root folder of your miniSD card.
With miniSD card inserted on the phone, start the bootloader (hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom).
You should see the screen pictured on the left, confirm flashing on screen by pressing the power button.
Flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
When flashing completes soft-reset your device.
Make sure your SD has FAT32 and has no label. There have been reports that if SD has a label the bootloader can not access the TRINIMG.nbh

racerx_ I have carefully read your response and suggestions, and thanks for your expertise input on the matter. I am fairly new to this stuff so read below carefully as you may find errors in the way I tried to go about doing what I was hoping to accomplish.
First let me answer your questions. I am running Windows XP. The phone is in it's completely natural state in that I have not flashed it in any way. The ROM I was TRYING to flash to the phone while it was not starting properly (this is where I manually entered bootloader) is an official ROM from the HTC website (please note everyone that when I registered my P3600i on the HTC website it came up as the Dopod 810). Anyway, that never worked. ActiveSync never detected the phone (and I guess that's the reason I could not do anything as far as flashing goes). I HARD-RESET my P3600i and it booted normally. I re-installed all the stuff I had on it, from memory card to various .cab files, and the phone is working beautifully thus far. I will report if anything funny happens again.
I have to ask you racerx_, if I CAN flash hard-SPL on the P3600i according to the lovely guide on www.trinityguides.info. I have been of the opinion that things don't work for the P3600i as they did for the P3600, and that has been echoed by many P3600i users on this forum who are ready and waiting to try out some cooked ROMs (myself included).
For the sake of record, my phone is running rom version 3.00.707.17 and radio version 1.46.00.11. I patiently await your response.

woaaahhh..
i didn't notice the 'i' in your previous post... yeah, as far as i know, these ROMs are not flashable on your p3600i.. sorry..
**correct me if i'm wrong somebody**

Yeah I kinda thought that would be your response. By the way - do you think that this phenomenon of sticking at the Windows Mobile splash screen (both the P3600 and P3600i models apparently) has anything to do with something users do with the devices, or you figure it's an inherent software glitch of some sort? I am wondering if I should try a different model or hold on to my P3600i? Hope it's not something that'll happen again - I fly for a living and it's not gonna be good to have the thing screw up on me away from base - I really count on it for everything from casual keeping in touch on Messenger to viewing my work schedule. I love the Trinity though - it's one of my all-time favourite HTC phones.

hmm... i don't think its inherent in the Trinity.. (not a hardware issue.. in my opinion)
its been a while since i followed the posts on it, but always seems to be software related.. sometimes ROM-specific problem. Personally, i've probably flashed as many ROMs as anyone and the only time i ever encountered problems was with the official HTC WM6 ha.. go figure.. I think ppl did find that hard resets before and after flashing are helpful as well..
i love my trinity, and there's not much else on the market to make me want to trade it in (is it just me, or have pda's kind of stopped getting cooler).. i'd stick with it..

[Help] A Myriad of Problems

Disclaimer: I am extremely illiterate when it comes to Android terminology, so you will most likely have to talk to me like I'm a child. I will try to explain my problems as best as I can, and will of course answer any questions. I also might over-explain, so I apologize for any length/redundancy issues.
Phone: XPERIA Play R800at, Android 2.3.3, Rooted with su and rom manager
My previous Play's touch screen stopped working, so the warranty granted me this new one. It's only two or three weeks old. The first problem I noticed was that I tried and could not delete anything off of my SD card. I tried formatting it a number of times, both in-phone (In Settings, as well as ES File Manager) and on Windows (both default formatter and a specific SD card formatter), but it would always revert back to what it's previous state would be. After researching a bit, I concluded it's probably faulty or failing, so I've ordered a new one that should get here within the week.
The second problem rose out of the first, I'm sure: My computer now doesn't recognize the sd card anymore. In SMC or MTP mode, it will not pop up on my computer and could not be recognized in PC Companion. On phone, the usual options you get in the notification bar (*dis*connect phone, etc.) do not show up. When connecting, the MTP USB Device driver attempts to install, but never succeeds. This is with USB debugging off and on, and every permutation I could think of.
Now, the most recent problem has been that the Home button doesn't work and there is no lock screen. Using the Terminal Emulator, I've attempted the popular fix (su -> echo -n ON > /efs/imei/keystr -> sync -> reboot) but I get the message /efs/imei/keystr directory nonexistent. I've factory reset my phone a number of times, reset settings, gone into recovery mode and reset things there, as well as caches, but all to no avail.
This could probably easily be remedied by just reflashing Android, or an older version or something, I'm sure, but given that my SD card is currently unreachable, I was wondering if anyone would know of a way I can fix these problems, or at least one of them. Thanks in advance.
If I've left anything out, please tell me and I will expound as best I can.
Other notes that might be of importance:
- It seems my *system* or whatever it would be is read-only, which seems like it could definitely be a problem. How do I fix this or do I even need to?
- I don't have the Setup Guide on my phone; I saw a thread that posited that this was a cause of the no lock screen problem.
Thanks again.

Driver install issue
Hello!
I'm not sure how to fix all of your problems. However, I have the same issue with my MTP drivers not installing when I connect the device. I've tried installing with various tools and the standard sony ericsson software. I believe I have the problem with the driver sorted out. I noticed that the drivers are, for some unknown reason, attempting to install to a TEMP folder. I would assume they are then being dumped from the TEMP folder after only a few seconds because when I install the driver it continues to ask me to install even when I click "finished."
You might try making sure the drivers are installing to the proper location if you haven't already. That might help with some of the issues.
On the same topic, do you know where the drivers are SUPPOSED to go in Windows XP? I'm fairly new to all of this stuff so I'm not sure exactly which folder in C:/WINDOWS the MTP driver for the Experia Play is supposed to go.
I hope this helps!
-Zot-

Asus Zenfone 2 ZE551ML - tried to change firmware from CN to WW, huge problem.

Hi guys, I have a big problem with my Asus Zenfone 2 ze551ml. I bought it from china so I didnt have Google Play and I used to download every app I needed from Aptoide. But yesterday I decided to give it a try and change the firmware. I read every article on "how to", most of them were saying the same steps, so I started by downloading everything I needed, the WW firmware from asus site, the usb drivers, the adb program etc. Everything was going great, and I came to that point that you just have to send via adb the package with the WW firmware and... my laptop(which is an Asus, lol) stopped recognising my phone. Then I started reading tons of threads on how to fix that problem but nothing. I did everything.
Download the intel usb drivers for android- done
Manually install the usb drivers from Asus- done
Uninstall everything and trying one driver at a time- done
Usb debugging-MTP, all these things again and again- done
Tried every single usb cable and port- done
Tried 3 different computers- done
Wipe cache partioning and try all the above steps again- done
Wipe all user data back to default- done
And nothing.. I mean nothing, my phone is invisible to any computer. Is anything else I can do? What's left? To throw my phone away? Now everything in my phone is tiny, the app icons are tiny, the fonts are tiny, even the fb messenger bubble is tiny.. pls help me.. :crying:

my problems and solution for you
Hellooo, not all hope i lost...
Firstly the problem I have similar to you is that my ZF2 runs on CN firmware, which is the biggest struggle ever trying to find the only working APK app files, I was happily trying to install WW firmware (even though it had the playstore, as it was some sort of modded brand new phone front eBay) and I accidely pressed the button which wipes everything :') So I go 3 days figuring out how to make my phone start as another issue had arrised, I fix it with some 3rd party bootloader...and ever since January I've been living this almighty stuggle.
FUNNY THING IS...I KNOW EXACTLY HOW TO FIX IT...but my Acer laptop has an old version of the ADB driver which I cannot get rid of OR UPDATE and I have no access to another pc
As for your issue, by some miracle you read this...
1) make sure you're using a data cable (one that shows you're phone in the Windows library list n all)
2) if you're not seeing or hearing what I said...go in your phones setting punch the fu...I mean tap the "about " option right at the bottom 7 times, and you should now have unlocked the Dev Options...
Now, back to the settings list, press Dev Options which is above the about option, scroll down a little and enable "USB Debugging" press yes/allow...what ever the **** comes up and looks good and wulluh.
3) Now, if actually you've already done step 2 and have tried 3 laptops :0...try step 1 again
4) If you followed step 3s very very complex instructions to a level of hope that binning the phone or suicide are options then by all means set it on fire then throw it at your ex gf...if you have one...concidering you bought an Asus phone lol, mug
5) try this other thing that works but is just as hopeless by finding it on YouTube, searching "Asus ZenFone2 Flash" with the "past month" filter there should be a video with the thumbnail of an Indian man with a blue shirt and glasses, click on it...watch closely n stuff.
Hope it works out and that you found my profecional instructions helpful - Lewis

Make sure your driver's are installed properly.. Check drivers on your pc by going to device manager and check

NiTesh said:
Make sure your driver's are installed properly.. Check drivers on your pc by going to device manager and check
Click to expand...
Click to collapse
That's his issue, same for me, ADB does not show in device manager. Unless you mean installing the driver by right clicking on the phones name?